New submission from Ludovic Gasc:
Hi,
To install easily Python 3.4.2 on Linux, I use Pythonz:
http://saghul.github.io/pythonz/
I've discovered that, depends on the packages already installed on Linux, I
don't have the same Python each time after compilation on servers.
Some features could
R. David Murray added the comment:
I don't think it is a good idea for us to try to track which packages are
needed and what they are named by the various downstreams. We could document
the optional modules by project name, though. Note also that the devguide does
point to the umbrella
Ludovic Gasc added the comment:
I'm not agree with you: I've lost a lot of time to find all packages I need for
that, I've merged information from several blog posts.
I imagine that I'm not alone with this problem.
If you move this information in devguide, most persons don't find this.
Andrew Svetlov added the comment:
For Ubuntu/debian you can just run:
$ sudo apt-get build-dep python3
--
nosy: +asvetlov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22882
___
Ludovic Gasc added the comment:
$ sudo apt-get build-dep python3
Good to know, I will test for my next deployment.
The only problem with that, if you use a old Debian with a Python3 that need
less dependencies that actual version.
But you can add a line for that in documentation if we have
R. David Murray added the comment:
The fact that it cost you a lot of time buttresses my point. Any documentation
we write is likely to get stale; it is only the downstream that knows when
these things change and could maintain such a document. And the easy answer is
as Andrew indicated,
Changes by R. David Murray rdmur...@bitdance.com:
--
versions: -Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22882
___
___
