Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: GeospatialPython/pyshp
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: GeospatialPython/pyshp
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.2.x
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 4 files changed
  • 2 contributors

Commits on Aug 18, 2017

  1. More lenient reading and writing for ints and floats

    Previously, int fields only accepted ints, and float fields only accepted floats. 
    Now, these can be specified as strings, and will try to force convert to the correct type. 
    Force conversion is done only when needed, to avoid large ints getting corrupted by converting to float and back to int. 
    
    Fixes #99 and #108
    karimbahgat authored Aug 18, 2017
    Configuration menu
    Copy the full SHA
    386f704 View commit details
    Browse the repository at this point in the history

Commits on Aug 24, 2017

  1. Configuration menu
    Copy the full SHA
    10c6176 View commit details
    Browse the repository at this point in the history

Commits on Aug 28, 2018

  1. Configuration menu
    Copy the full SHA
    a53f022 View commit details
    Browse the repository at this point in the history

Commits on Sep 8, 2018

  1. Fix text character truncation in py3 + bump to next version

    - Fixes issue in Py3 when converting text characters to byte strings, but in Py3 converts to unicode instead, because uses the Py2 specific str() function, instead of the version neutral b(). When the text contains non-ascii 2-byte unicode values this results in truncating the unicode length instead of the byte length, and thus results in incorrectly padded byte lengths and data values ending up in the wrong field/column. See #157, and also #148. 
    - Also bump to next version.
    karimbahgat authored Sep 8, 2018
    Configuration menu
    Copy the full SHA
    fc630bb View commit details
    Browse the repository at this point in the history
Loading