You are not logged in.
Hi,
There is a package in AUR that goes through quite a bit of effort to port a program from python 2 to python 3, because "python 3 is the default version in Arch".
This involves patches to "upgrade" the program to python 3, since it was not written for python 3 in the first place.
As I understand, python 3 really is the default version on Arch, but there's also a policy of sending patches upstream, if possible.
Should the desire to make everything run on python 3 weigh heavier than the desire to keep packages free of patches, or not?
Here is the package in question:
deheader: http://aur.archlinux.org/packages.php?ID=44074
Thanks.
Offline
chicken or egg?
imho, if the package can be made to run on python3, that should be the default. having it being able to run on python2 as an added extra is a plus for a smooth transition for other distributions.
Offline
But what if the port to python3 is bugprone? Same answer?
Offline
python3 patches should be pushed upstream. And the 'minimal patches' guideline applies to official Arch packages, most AUR packages (AFAICT) are created to apply some patch or other.
In the case of the package you describe, it'd be easier to just make it depend on python2 while the python3 patches are sent upstream. A few sed lines.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline