Changes for the latest pydicom

[naggie]

Fixes #31 and #26

...aside from the dependent pydicom version number which has not changed yet.

As noted, cancan101@b41cfa1 may be the better fix, however a similar fix is also required for #31 .

Depends on if backwards compatibility is required or not. I would suggest not requiring it so long as pydicom releases a new version number which becomes a dependency.

[naggie]

This is more of a problem than I realised -- old (pip) versions of pynetdicom don't specify pydicom as a dependency. This means deployments with virtualenv+pip fail without installing pydicom first. This is exacerbated if you need to deploy versions before and after the rename.

Perhaps @cancan101 's fix is therefore more appropriate.

[cancan101]

I just filed an issue with pydicom to please release to pypi with new package.

In the meantime you can also try: cancan101@a65b114 (this is my new fork of this project). You will need to pip install with --process-dependency-links.

[naggie]

Excellent, thanks!

[cancan101]

This might also be helpful: pypa/pip#1274

[naggie]

Looks like cancan101's PR has resolved this. Thanks