-
Notifications
You must be signed in to change notification settings - Fork 184
pynetdicom release with pydicom 3 #981
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
Comments
Yes, but there are a number of issues I'd like to get to the bottom of before I do a new release. I think technically you can use pydicom 3, you'll probably have to filter out the various deprecation warnings though. |
I'm curious about the key challenges you’re facing with the v3 release. I imagine the open issues are tough if they're still on the table. Do you think resolving those could lead to breaking changes? If not, why not go ahead and release v3 now and then tackle those issues in fix releases later on? Just a thought. |
I concur, I've discovered a bug with some decompression in v2 of pydicom that's fixed in v3, and not having a compatible pynetdicom is problematic. Pynetdicom 2.x seems to only allow pydicom versions < v3. |
Hi @scaramallion I wanted to follow up about this update, is there any estimated timeline? We want to use the |
I'll probably do something soon, but I'd like to resolve at #912 first |
I would like to utilise some features of pydicom 3 in a new project that primarily relies on pynetdicom. I can see that @medihack has implemented pydicom 3 support in #972
Would it be possible to have a new release of pynetdicom that includes this?
The text was updated successfully, but these errors were encountered: