Andreas Maier

@thaJeztah This is open for nearly one year now. Can anyone please comment?

I would like to second this issue. The DeprecationWarning is additionally raised when using tagMap. Support for `TAG_MAP` and `TYPE_MAP` has been introduced in pyasn1 version 0.5.0, including backwards compatibility...

After debugging and researching a bit, it turns out that the deprecation warning issue has already been addressed with PR #983. That code has just not been released yet (2.9.1...

We also see the same issue in pytz 2025.1 and 2025.2. Circumvention for us is to exclude the pytz versions that have the issue: 2024.2, 2025.1, 2025.2 Can anyone please...

Is possibly related to issue #133

We have started using Renovate to get dependency recommendations. It currently recommends for one of our projects to upgrade `coverage` to >7.0 which requires using `coveralls`>=4.0. However, `coveralls` versions 4.0.0...

@gowridurgad I can confirm that as well. I have verified that using a login shell on macos with Python 3.11 on GitHub Actions, in PR https://github.com/zhmcclient/python-zhmcclient/actions/runs/11065338978/job/30744588887?pr=1681#step:19:1 Thanks for your help!...

Then in the meantime, could the link to the repo on Pypi be changed to point to the safety repo, and a sentence added that explains it?

@TheKevJames Any chance you can take a look at this PR? The current situation forces everyone (i.e. the world) to stay on the 3.3.1 version of coveralls when using Python...

I am not arguing to fix older versions of pywin32. But future versions simply should follow what most packages on Pypi do: Declare the Python requirements in such a way...