Changes by Patrick Welche :
--
nosy: +prlw1
___
Python tracker
<http://bugs.python.org/issue14873>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Patrick Welche :
--
nosy: +prlw1
___
Python tracker
<http://bugs.python.org/issue13789>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Patrick Welche :
--
nosy: +prlw1
___
Python tracker
<http://bugs.python.org/issue13210>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Patrick Welche :
--
nosy: +prlw1
___
Python tracker
<http://bugs.python.org/issue13461>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Patrick Welche:
I currently have python 2.7 and 3.2 installed concurrently. I just tried to
install 3.3 as well, but a file conflicts between 3.2 and 3.3. It is
libpython3.so.
Given that we go out of our way e.g. with
$(INSTALL_DATA) Misc/python.pc $(DESTDIR)$(LIBPC
Patrick Welche added the comment:
I see that this was introduced in
http://www.python.org/dev/peps/pep-0384/
Would a configure option to make it easy not to install the conflicting file be
acceptable?
--
___
Python tracker
<http://bugs.python.
Patrick Welche added the comment:
No, I don't think you should close this, as you haven't explained what it is
that you won't do.
I think that a sensible plan is to introduce a configure flag whose effect is
to not install the files which cause the conflict. You set the def
Patrick Welche added the comment:
To quote the README:
Installing multiple versions
...
For example, if you want to install Python 2.6, 2.7 and 3.4 with 2.7 being the
primary version, you would execute "make install" in your 2.7 build directory
and "
