-
-
Notifications
You must be signed in to change notification settings - Fork 259
Seamlessly Read/Write datetime.date
Objects
#18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
""" | ||
Unit tests for Pythonic `datetime.date` object handling. | ||
""" | ||
|
||
import unittest | ||
import datetime | ||
try: | ||
from StringIO import StringIO | ||
except ImportError: | ||
from io import BytesIO as StringIO | ||
|
||
import shapefile | ||
|
||
|
||
class TestDateHandling(unittest.TestCase): | ||
|
||
def testDateReadWrite(self): | ||
"""Round-trip read and write Python `date` as value for 'D' field""" | ||
today = datetime.date.today() | ||
|
||
# Write a one-field, one-record shp to memory; use `date` obj as value | ||
writer = shapefile.Writer() | ||
writer.field('DATEFIELD', 'D', 8) | ||
writer.null() | ||
writer.record(today) | ||
shp, shx, dbf = StringIO(), StringIO(), StringIO() | ||
writer.save(shp=shp, shx=shx, dbf=dbf) | ||
|
||
# Read our in-memory shp to verify that Reader gives us a `date` obj | ||
reader = shapefile.Reader(shp=shp, shx=shx, dbf=dbf) | ||
self.assertEqual(reader.fields[-1][1], 'D') | ||
self.assertEqual(len(reader.records()), 1) | ||
record = reader.record(0) | ||
d = record[0] | ||
self.assertTrue(isinstance(d, datetime.date), | ||
"Expected a `date` object back from Reader (we got a %s)" % type(d)) | ||
self.assertEqual(d, today) | ||
|
||
|
||
if __name__ == '__main__': | ||
unittest.main() |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens when you have a date with size > 8? In my tests it seems to result in corrupt shapefiles. If I save a date with a size bigger than 8, then open the shapefile in arcmap and try to edit it, the data in the dbf file become corrupted.
Might it be better to mandate a size of exactly 8?