Open alexander-bauer opened 6 months ago
Interesting, we don't support / test Python 3.9 to start with. We may have used more recent python syntax. I would have expected you would have had to hack things to get it to install in 3.9? If not, that's a bug too.
That aside, I would have expected our CI to catch this on the PR that updated to 0.5.0. Happy to revert for now.
I even more welcome a PR to upgrade to latest APIs + plugging the missing testing. I started locally on https://github.com/pypa/bandersnatch/pull/1672 but just haven't had the time to finish it and test it ... all help welcome.
I didn't have any trouble installing on 3.9, funnily enough. I was able to get my environment to work by pinning the s3path
version: the extra requirement listed in the setup.cfg
looks like it's just set to >= 0.4.0
, so pip install bandersnatch[s3] s3path<0.5.0
is resolvable.
I haven't got the cycles to contribute today, unfortunately, but I'm back up and working with just that install tweak.
Hello, I'm using a fresh install of
bandersnatch[s3]
in attempt to establish a private S3-backed mirror. I discovered this issue in Python 3.9, but was able to reproduce it on Python 3.11. Here is an example configuration, and the following stack trace.It appears the commit in the upstream
s3path
package is https://github.com/liormizr/s3path/commit/5ea0bd23db60c6efd34da732534442ffb8894abf. It looks like this change first appeared in version0.5.0
, and that the latest tag without it is0.4.2
.A proper fix should probably update the Bandersnatch codebase to use the new public API, but a minimal fix in the meantime would be to adjust
requirements_s3.txt
to uses3path==0.4.2
rather than its currents3path==0.5.0
.