Hello!
The condensed version of the question would probably be: How does one
deal with multiple interpreters and one package where you want to try
some changes?
The background:
I made a trivial change to some package (docutils) to scratch a
personal itch, and I want to offer this back to the
Are you using arch linux.
I deal with multiple interpreters putting fake executables in
/usr/local/bin for everything: (python, sphinx, virtualenv, pydoc,
idle, python-config...) selecting 2 or 3. You can do the same for
selecting 2.3, 2.5, 2.7. What the scripts do is to detect whether it
is
Joep van Delft joepvande...@xs4all.nl wrote:
Hello!
The condensed version of the question would probably be: How does one
deal with multiple interpreters and one package where you want to try
some changes?
You could use tox to test a package using different Python versions.
--
Akira
--
On 7/17/14 11:32 AM, Joep van Delft wrote:
Hello!
The condensed version of the question would probably be: How does one
deal with multiple interpreters and one package where you want to try
some changes?
The background:
I made a trivial change to some package (docutils) to scratch a
personal
Hello Javier!
Thanks, those links are helping a bit. And: yes, I am using Archlinux.
But still those links assume that there are totally separate
site-packages* directories installed for both. I am not sure how I
would surpass this distinction between py-X.P and py-Y.Q.
Should I really create
On Thu, 17 Jul 2014 15:41:44 -0400
Ned Batchelder n...@nedbatchelder.com wrote:
For testing one project on multiple versions of Python, use tox.
Its entire reason for being is to test Python code against multiple
environments, generally for different Python versions, but possibly
for other
I can work with this (have not tried though), but there must be a
more elegant solution than symlinking my way forward...
I don't really understand what you are trying to do, but I would advise
to use environment variables to control the behaviour of the fake scripts
in /usr/local/bin
In
In article mailman.11957.1405626121.18130.python-l...@python.org,
Ned Batchelder n...@nedbatchelder.com wrote:
On 7/17/14 11:32 AM, Joep van Delft wrote:
Hello!
The condensed version of the question would probably be: How does one
deal with multiple interpreters and one package where
On 18/07/2014 9:44 AM, Roy Smith wrote:
In article mailman.11957.1405626121.18130.python-l...@python.org,
Ned Batchelder n...@nedbatchelder.com wrote:
Virtualenv is definitely the right way to isolate different Python
environments from each other.
Absolutely. Don't even consider any other
In article lq9sf2$p9r$1...@dont-email.me, alex23 wuwe...@gmail.com
wrote:
On 18/07/2014 9:44 AM, Roy Smith wrote:
In article mailman.11957.1405626121.18130.python-l...@python.org,
Ned Batchelder n...@nedbatchelder.com wrote:
Virtualenv is definitely the right way to isolate different
On Fri, Jul 18, 2014 at 11:29 AM, Roy Smith r...@panix.com wrote:
In article lq9sf2$p9r$1...@dont-email.me, alex23 wuwe...@gmail.com
wrote:
On 18/07/2014 9:44 AM, Roy Smith wrote:
In article mailman.11957.1405626121.18130.python-l...@python.org,
Ned Batchelder n...@nedbatchelder.com
11 matches
Mail list logo
