Move to pydicom 1.3+

Issue #777 resolved
Ed McDonagh created an issue

pydicom 0.99 and below is legacy. Need to migrate to new pydicom. Required for new pynetdicom (issue ref #530) and for sanity. Also related to issue ref #741 and the structured reports PR they have in the offing.

Comments (11)

  1. Ed McDonagh reporter

    Appears that names read from DICOM are byte strings, so reflecting that in test. Need to investigate more thoroughly with pydicom. Refs #404, #777 [skip ci] docs only.

    → <<cset 2f8c35cd6eda>>

  2. Ed McDonagh reporter

    Disabled pynetdicom testing for now. All other tests pass. Need to work out Python 3 testing rig on bitbucket. Refs #404, #777, #457, #530 [skip ci] Not ready for testing. Next task - move to Django 1.9...

    → <<cset e13fda4c134e>>

  3. Ed McDonagh reporter

    Changed everything from dicom to pydicom. Attempted to remove all byte warnings - elements with VR UN are imported as bytes. Existing db data might be bytes too. Refs #457, #404, #777

    → <<cset 6bd11d6314da>>

  4. Log in to comment