pylint #50463 tarball and debian and packaging for python3 [resolved]
generate tarball and debian and packages for python3 (also for lgc and astng) | |
priority | normal |
---|---|
type | task |
done in | 0.22.0 |
load | 5.000 |
load left | 0.000 |
closed by | <not specified> |
generate tarball and debian and packages for python3 (also for lgc and astng) | |
priority | normal |
---|---|
type | task |
done in | 0.22.0 |
load | 5.000 |
load left | 0.000 |
closed by | <not specified> |
Comments
-
2010/11/26 11:43
-
2010/11/26 15:48
-
2010/11/26 16:33
add commentI'm not sure to understand the ticket clearly.. but if you want
both source distribution archives for python2 and python3, I'm pretty
sure we don't need that.
The source tarball should be kept python2 only. Some reasons:
- python2 is the only one based on scm
- python3 flavour is *built* on the fly which guarantee compatibility
and our chosen approach («Maintain a Python 2 base and use 2to3 to
generate Python 3 code» ¹)
- python3 users can still run `python3 setup.py build` (humm, yes in
case of pylint it's not possible right away due to particular test
files but we provide an INSTALL.Python3 file for manual steps)
So, my conclusion:
If we have different source distributions, we have different projects.
If you want different flavours, change the cooking only (aka building steps)
¹ http://wiki.python.org/moin/PortingPythonToPy3k
this raises a question, though. Is it possible to use the source tarball we distribute on a machine with only python3 installed?
Not before a clean python3 rebuild (which is normally done automatically
by install command).
In the general case, this should be enough:
python3 setup.py build
Otherwise, you have to manually run the 2to3 script provided for all
python versions (option taken in the case of pylint for now).
In case of pylint, we could drop the concerned test files for a clean
python3-compatible archive but I hope to declare them in a more
appropriate way (using data_files ?) or with some monkey-patching in
distutils.