Comments (10)
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.
Related Issues (20)
- compile fails on docker python:2.7 HOT 3
- Correct And Simplify Memory Handling in xattr_get HOT 4
- Broken signature for 0.6.1 HOT 3
- support Path objects HOT 2
- pyxattr-0.5.x installation error HOT 2
- pyxattr fails to install on Windows 10 with cl : Command line error D8021 : invalid numeric argument '/Werror' HOT 4
- Better error message when trying to write EAs too big for file system HOT 4
- Build Fail HOT 3
- 0.7.2: sphinx warnings HOT 8
- Consider adding incremental read and seek interface for large attribute values HOT 6
- Ability to read and write MacOS extended attributes on CIFS volume HOT 5
- pip install requires Python.h and gcc HOT 3
- Tests should only look at the user namespace HOT 10
- BUG: Memory leak bugs due to returned new reference is not decreased on failure (static analyzer reports) HOT 5
- Is there batch operations? HOT 1
- Fix example and maybe add typing HOT 2
- PyPy3.10: `xattr.getxattr()` does not accept `pathlib.Path` whereas it works on CPython HOT 12
- 0.8.1: documentation uses `recommonmark` which is now deprecated HOT 5
- library name collision: xattr and pyxattr = `import xattr`?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pyxattr.