Build failure with 0.7.1 about pyxattr HOT 10 CLOSED

This is on an up-to-date Arch Linux machine with Python 3.8.0.

from pyxattr.

The error message is when building for Python 2.7, but Python 2 is no longer supported in the last version.

What command did you run that triggered a Python 2 build? The makefile doesn't list Python 2 anymore.

from pyxattr.

Or at least should not, maybe I left it by mistake. Hence good to understand what triggered the Py 2.7 build.

from pyxattr.

We explicitly build both Python 2 and Python 3 versions of the package. I did not realize that Python 2 support was dropped. My mistake. The timing is a little bit unfortunate, though, since there are some quite popular applications that depend on pyxattr and still do not support Python 3 in any stable release. This essentially prevents us from upgrading pyxattr to the most recent release at Arch Linux. I guess other distributions will be affected too, unless there are new stable releases of bup and rdiff-backup with Python 3 support soon.

from pyxattr.

Also, it is quite surprising to see this breaking change happening in a minor release. A bigger version jump would have been justified, I guess.

from pyxattr.

I guess this can be closed, though. Thank you for your help!

from pyxattr.

We explicitly build both Python 2 and Python 3 versions of the package. I did not realize that Python 2 support was dropped. My mistake.

I see, no problem.

The timing is a little bit unfortunate, though, since there are some quite popular applications that depend on pyxattr and still do not support Python 3 in any stable release.

I would hope that in the next 3-5, at most 6 months, any that are still actually maintained will get one. After all, Python 2 is EOL in 2 weeks upstream.

This essentially prevents us from upgrading pyxattr to the most recent release at Arch Linux.

Note that there are no significant changes besides moving to cleaner code thanks to the Py3-only code; there is a very small fix in case memory allocation fails when creating a list.

I guess other distributions will be affected too, unless there are new stable releases of bup and rdiff-backup with Python 3 support soon.

Yes, I'm not uploading the new version to Debian either for now.

Also, it is quite surprising to see this breaking change happening in a minor release. A bigger version jump would have been justified, I guess.

Yes, you are right, I should have moved to 1.0.0, but the ship has now sailed. Do you think it would be worth re-releasing the Py2 version as 0.8, and a 1.0 with Python 3 only?

from pyxattr.

Personally, I don't see much benefit in rereleasing things but it might help prevent more confusion.

from pyxattr.

I'll just release 0.8 as bigger version bump, and call this "done".

from pyxattr.

Actually, "0.7" was the one that introduced py3-only, not 0.7.1. Sigh, I think I'll just leave things as they are right now…

from pyxattr.