scaramallion
scaramallion
How would ASGI work with the DICOM TCP protocol? As I understand it, ASGI only applies to HTTP or websockets, not TCP.
Hmm, OK, thanks for the explanation. It does look like it'd be a nice extra though.
I have no real experience with either so no idea. I'm only just starting to experiment by attempting to write a cut-down association client and server using the various options.
What's the plan for 2.x and 3.0? I.e, at what release are we expecting to end the 2.x series?
I'm not fussed, just wanted to know if I should create a new release issue or not
I'd like to change the config option setting to use a single entry point, probably backed by a dict or class as you suggested: ```python from pydicom import config config.set_option("opt...
I've also never really been happy with the current way we handle pixel data decoding (too much boilerplate, hard to customise). I'd like to replace it wholesale with a system...
* `Sequence` `append`, `extend`, `__iadd__`, `insert` and maybe `__setitem__`. Basically anything that has the narrower parameter type `Dataset` compared to `MultiValue` * `Dataset` `__contains__` because of the narrower type
> the latter should be Sequence[pydicom.dataelem.DataElement] Shouldn't it be `MutableSequence[T]`? A VM > 1 `DataElement`'s value is a `MultiValue` instance. > We ran into an issue in highdicom where we...
This seems like a good idea, perhaps in `_version.py`?