Éric Araujo added the comment:
setuptools is recommended over distutils, and doesn’t have the issue (per
previous messages).
--
assignee: eric.araujo ->
resolution: -> wont fix
stage: needs patch -> resolved
status: open -> closed
___
Python
Changes by Éric Araujo mer...@netwok.org:
--
components: +Distutils -Distutils2
stage: - needs patch
title: distutils2: build should use a version-specific build directory -
distutils: build should use a version-specific build directory
versions: +Python 3.5 -3rd party, Python 3.4
Ronald Oussoren added the comment:
I don't think this is a bugfix, but a new feature and as such the behavior
should only be changed for 3.4.
The easiest workaround for this issue is to use setuptools or distribute when
installing, as those tools do set the various build directories to
Arfrever Frehtes Taifersar Arahesis added the comment:
Changing of name of subdirectory would break e.g. shell scripts, which set
PYTHONPATH=build/lib when calling Python scripts, so this change rather should
not be made in micro releases.
--
___
Ronald Oussoren added the comment:
I'd change the name of the subdirectories of build instead of the name of the
build directory itself. That way distutils will still create one build
directory regardless of how many python versions you use, and the name of that
directory is easily
Éric Araujo added the comment:
I'd change the name of the subdirectories of build instead of the name of the
build directory itself.
Yep that’s what I was thinking about (or if I wasn’t, I should have been :)
IIRC distutils is more or less closed for development w.r.t. new features.
Not
Éric Araujo added the comment:
It seems to me this is just a special case of the more general issue of
building multiple versions of the
same distribution, say with multiple versions of Python 2. In general,
anytime you change your build
environment, you should start with no existing
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15419
___
Arfrever Frehtes Taifersar Arahesis added the comment:
Currently users can run e.g.:
$ python2.7 setup.py build -b build-2.7 install
$ python3.2 setup.py build -b build-3.2 install
If default name of build directory had to be changed, then it would be useful
to also include name of Python
