Releases: ImagingDataCommons/dicomweb-client
Releases · ImagingDataCommons/dicomweb-client
0.52.0
New features
- New module
dicomweb_client.uri
for creating and parsing DICOMweb URIs (#48)
0.51.0
Improvements
- Allow single-part response message from origin server for the Retrieve Instance transaction. It is debatable whether this behaviour is compliant with the standard. Part 18 originally specified that an instance should be retrieved using content type
multipart/related; type="application/dicom"
, but Supplement 183 changed the wording of the standard and explicitly stated that application/dicom
shall be used. This change in behavior was unintentional and Correction Proposal 2040 aims to correct this. However, since this behavior is allowed according to the current version of standard, we decided to support it.
0.50.4
Improvements
- Log additional information during decoding of multipart messages
- Apply stricter flake8 rules for improved PEP8 compliance
0.50.3
Bug fixes
- Fix extraction of parts from multipart message
0.50.2
Bug fixes
- Correctly specify required Python version
Improvements
0.50.0
New features
- Add
iter_*()
methods for retrieving parts of multipart resources from the origin server in chunks using chunked transfer encoding
- Automatically retrieve series and studies in chunks via command line interface
0.41.2
Bug fixes
- Fix issue of duplicated Host header field when using chunked transfer encoding
0.41.0
Enhancement
Improved logging
- Ensure that all request messages are logged (for all retry iterations)
- Configure the root logger to write urllib3 messages
0.40.1
Bugfix
- Fix content type of STOW-RS StoreInstances POST request messages
0.40.0
New features
- Configurable retrying of GET and POST requests for given HTTP status codes
Enhancements
- Check type hints using mypy
Changes
- Drop support for Python 3.5 to enable more advanced type definitions, f-string formatting, etc.