Open schribl opened 5 months ago
Note that the version specifiers that you linked to are >=
, not <=
, so that they can "float upwards" and accept newer versions of those packages.
How would you suggest changing them? I'd be happy to accept a PR if you have specific suggestions.
I agree we should probably remove Python 2.7 support.
I removed Python 2.7 support in 4e2d3d402d494e2f6dda156e772ff07dbdab5282
Sorry @williballenthin for not seeing your replies. The main point was that the last official release was still having the ==
dependency constraint. So with your new version you addressed this, however the version is not uploaded to PyPI:
https://pypi.org/project/python-evtx/#files
If there is anything I can support, let me know!
@williballenthin sorry to ping you again, but the 0.8.0 version is not yet available on PyPI. Can I somehow support so this can be updated on PyPI?
Sorry for adding this as an issue, but I did not find a better way of asking this question:
Are there any plans for releasing a new version to PyPI with the relaxed version dependencies? The last release still locked the dependencies to specific versions (according to the commit for 2.7 support: https://github.com/williballenthin/python-evtx/blob/v0.7.4/setup.py#L24)
I think it would be good to have a release with relaxed requirements and possibly even revisited depending on the current 2.7 support from this project. As now 2.7 was end of life over 4 years ago. This would avoid potential for unresolvable dependencies in case some other project does require newer versions of this dependencies. As well as some dependency managers might even fall back to version 0.6.1 without this requirements: https://github.com/williballenthin/python-evtx/blob/v0.6.1/setup.py#L24
In case there is anything I can do to support this process I am happy to support this.