On 07/26/2010 06:36 AM, Edward Diener wrote:
> On 7/25/2010 10:42 PM, David Robinow wrote:
>> On Sun, Jul 25, 2010 at 8:40 PM, Edward Diener
>> wrote:
>>> On 7/25/2010 5:57 PM, Thomas Jollans wrote:
>>> So if a standard library module ( or distributed library ) executes a
>>> call
>>> internally
On 07/26/2010 06:36 AM, Edward Diener wrote:
>
> I start a Python script for version X by going to X's root directory and
> invoking 'python someScript.py' from the command line. Does that not
> sound reasonable ?
Do you have an example of two (not self written) applications requiring
to change t
On 07/25/2010 10:39 PM, MRAB wrote:
> News123 wrote:
>> Thus my idea of having a pystarter with a config file
>> mentioning which directories (tools) should use which python executable
>>
> I think that's the wrong way round. A pystarter should ask the _tool_
> which version of Python it needs.
>>
>> Thus my idea of having a pystarter with a config file
>> mentioning which directories (tools) should use which python executable
>
> Well, good luck ! I don;t know how this is resolved for you when some
> scripts executes 'python xxx yyy' or 'someScript.py yyy'.
both could be resolved with
On Mon, 26 Jul 2010 00:36:47 -0400, Edward Diener wrote:
> On 7/25/2010 10:42 PM, David Robinow wrote:
[...]
>> Edward, I'm having a really hard time understanding your problem. Could
>> you give an example of some real code that is causing you difficulty?
>
> I start a Python script for version
On 7/25/2010 10:42 PM, David Robinow wrote:
On Sun, Jul 25, 2010 at 8:40 PM, Edward Diener
wrote:
On 7/25/2010 5:57 PM, Thomas Jollans wrote:
So if a standard library module ( or distributed library ) executes a call
internally to 'python xxx yyy' or executes a call internally to
'someScript.p
On 7/25/2010 8:41 PM, Steven D'Aprano wrote:
On Sun, 25 Jul 2010 15:19:53 -0400, Edward Diener wrote:
On 7/25/2010 10:03 AM, Thomas Jollans wrote:
On 07/25/2010 02:46 PM, Edward Diener wrote:
The problem with this is that you forget that a script can invoke
Python internally. So whether one u
On Sun, Jul 25, 2010 at 8:40 PM, Edward Diener
wrote:
> On 7/25/2010 5:57 PM, Thomas Jollans wrote:
> So if a standard library module ( or distributed library ) executes a call
> internally to 'python xxx yyy' or executes a call internally to
> 'someScript.py yyy', you're fine with multiple co-exi
On Sun, 25 Jul 2010 15:19:53 -0400, Edward Diener wrote:
> On 7/25/2010 10:03 AM, Thomas Jollans wrote:
>> On 07/25/2010 02:46 PM, Edward Diener wrote:
>>> The problem with this is that you forget that a script can invoke
>>> Python internally. So whether one uses the console or file association
>
On 7/25/2010 5:57 PM, Thomas Jollans wrote:
On 07/25/2010 11:10 PM, Edward Diener wrote:
On 7/25/2010 3:39 PM, Christian Heimes wrote:
Am 25.07.2010 21:32, schrieb Thomas Jollans:
If a script uses sys.executable instead of "python", there is no
problem, at all.
It's true that sys.executable
On 07/25/2010 11:10 PM, Edward Diener wrote:
> On 7/25/2010 3:39 PM, Christian Heimes wrote:
>> Am 25.07.2010 21:32, schrieb Thomas Jollans:
>>> If a script uses sys.executable instead of "python", there is no
>>> problem, at all.
>>
>> It's true that sys.executable is the best way if you have to s
On 7/25/2010 4:26 PM, News123 wrote:
On 07/25/2010 10:18 PM, Thomas Jollans wrote:
On 07/25/2010 10:04 PM, News123 wrote:
sOn 07/25/2010 09:39 PM, Christian Heimes wrote:
Am 25.07.2010 21:32, schrieb Thomas Jollans:
If a script uses sys.executable instead of "python", there is no
problem, at
On 7/25/2010 4:22 PM, News123 wrote:
On 07/25/2010 09:33 PM, Edward Diener wrote:
On 7/25/2010 10:31 AM, News123 wrote:
On 07/25/2010 02:46 PM, Edward Diener wrote:
On 7/25/2010 6:07 AM, Gelonida wrote:
How does a 'pystarter' program know where the file's location is which
is being invoked
On 7/25/2010 3:39 PM, Christian Heimes wrote:
Am 25.07.2010 21:32, schrieb Thomas Jollans:
If a script uses sys.executable instead of "python", there is no
problem, at all.
It's true that sys.executable is the best way if you have to start a new
Python interpreter. However sys.executable may n
On 7/25/2010 3:32 PM, Thomas Jollans wrote:
On 07/25/2010 09:19 PM, Edward Diener wrote:
On 7/25/2010 10:03 AM, Thomas Jollans wrote:
On 07/25/2010 02:46 PM, Edward Diener wrote:
The problem with this is that you forget that a script can invoke Python
internally. So whether one uses the consol
News123 wrote:
On 07/25/2010 09:33 PM, Edward Diener wrote:
On 7/25/2010 10:31 AM, News123 wrote:
On 07/25/2010 02:46 PM, Edward Diener wrote:
On 7/25/2010 6:07 AM, Gelonida wrote:
How does a 'pystarter' program know where the file's location is which
is being invoked ?
the file's locatio
On 07/25/2010 10:18 PM, Thomas Jollans wrote:
> On 07/25/2010 10:04 PM, News123 wrote:
>> sOn 07/25/2010 09:39 PM, Christian Heimes wrote:
>>> Am 25.07.2010 21:32, schrieb Thomas Jollans:
If a script uses sys.executable instead of "python", there is no
problem, at all.
>>
>>
>> sys.execut
On 07/25/2010 09:33 PM, Edward Diener wrote:
> On 7/25/2010 10:31 AM, News123 wrote:
>> On 07/25/2010 02:46 PM, Edward Diener wrote:
>>> On 7/25/2010 6:07 AM, Gelonida wrote:
>
> How does a 'pystarter' program know where the file's location is which
> is being invoked ?
the file's location would
On 07/25/2010 10:04 PM, News123 wrote:
> sOn 07/25/2010 09:39 PM, Christian Heimes wrote:
>> Am 25.07.2010 21:32, schrieb Thomas Jollans:
>>> If a script uses sys.executable instead of "python", there is no
>>> problem, at all.
>
>
> sys.executable will not work with scripts converted with py2e
sOn 07/25/2010 09:39 PM, Christian Heimes wrote:
> Am 25.07.2010 21:32, schrieb Thomas Jollans:
>> If a script uses sys.executable instead of "python", there is no
>> problem, at all.
sys.executable will not work with scripts converted with py2exe,
as sys.executable will not be the executable o
On 07/25/2010 09:39 PM, Christian Heimes wrote:
> Am 25.07.2010 21:32, schrieb Thomas Jollans:
>> If a script uses sys.executable instead of "python", there is no
>> problem, at all.
>
> It's true that sys.executable is the best way if you have to start a new
> Python interpreter. However sys.exec
Am 25.07.2010 21:32, schrieb Thomas Jollans:
> If a script uses sys.executable instead of "python", there is no
> problem, at all.
It's true that sys.executable is the best way if you have to start a new
Python interpreter. However sys.executable may not be set for NT
services. So there may be a p
On 7/25/2010 10:31 AM, News123 wrote:
On 07/25/2010 02:46 PM, Edward Diener wrote:
On 7/25/2010 6:07 AM, Gelonida wrote:
There the windows solution could be something like a small 'pystarter'
program, which would decide depending on the file's location / the
file's first line which python sho
On 07/25/2010 09:19 PM, Edward Diener wrote:
> On 7/25/2010 10:03 AM, Thomas Jollans wrote:
>> On 07/25/2010 02:46 PM, Edward Diener wrote:
>>> The problem with this is that you forget that a script can invoke Python
>>> internally. So whether one uses the console or file association method
>>> of
On 07/25/2010 09:12 PM, Edward Diener wrote:
> On 7/25/2010 1:51 PM, Joel Goldstick wrote:
>> There is this:
>> http://pypi.python.org/pypi/virtualenv
>
> It appears to be only for Linux.
I don't know where you get that impression from. I don't know how well
it works on which platforms, but the f
On 7/25/2010 10:03 AM, Thomas Jollans wrote:
On 07/25/2010 02:46 PM, Edward Diener wrote:
The problem with this is that you forget that a script can invoke Python
internally. So whether one uses the console or file association method
of invoking Python externally, any already written script can
On 7/25/2010 1:51 PM, Joel Goldstick wrote:
Edward Diener wrote:
Are there any documents about multiple versionsof Python coexisting in
the same OS ( Windows in my case ) and what pitfalls to look out for ?
I have already run into a number of them. I installed Python 2.7 and
3.1.2 into completel
Edward Diener wrote:
Are there any documents about multiple versionsof Python coexisting in
the same OS ( Windows in my case ) and what pitfalls to look out for ? I
have already run into a number of them. I installed Python 2.7 and 3.1.2
into completely folders, but immediately ran into serious
On 07/25/2010 02:46 PM, Edward Diener wrote:
> On 7/25/2010 6:07 AM, Gelonida wrote:
>> Hi Edward,
>>
>> There the windows solution could be something like a small 'pystarter'
>> program, which would decide depending on the file's location / the
>> file's first line which python should be started.
On 07/25/2010 02:46 PM, Edward Diener wrote:
> On 7/25/2010 6:07 AM, Gelonida wrote:
>> There the windows solution could be something like a small 'pystarter'
>> program, which would decide depending on the file's location / the
>> file's first line which python should be started.
>
> This does n
On 07/25/2010 02:46 PM, Edward Diener wrote:
> The problem with this is that you forget that a script can invoke Python
> internally. So whether one uses the console or file association method
> of invoking Python externally, any already written script can use either
> internally.
Maybe it's just
On 7/25/2010 2:20 AM, Steven D'Aprano wrote:
On Sat, 24 Jul 2010 22:03:48 -0700, Chris Rebert wrote:
Are the .py and .pyc extensions the only ones which are associated with
Python or are there others, for a normal Python installation in Windows
?
There's also .pyw
Also .pyo
.py = Python so
On 7/25/2010 6:07 AM, Gelonida wrote:
Hi Edward,
On 07/25/2010 04:40 AM, Edward Diener wrote:
I found the solutions too exotic for actual use, and completely
ineffectual for the cases I originally cited. The people in that thread
seem to have completely forgotten that Python can be invoked ext
Hi Edward,
On 07/25/2010 04:40 AM, Edward Diener wrote:
> I found the solutions too exotic for actual use, and completely
> ineffectual for the cases I originally cited. The people in that thread
> seem to have completely forgotten that Python can be invoked externally
> and internally both throu
On Sat, 24 Jul 2010 22:03:48 -0700, Chris Rebert wrote:
>> Are the .py and .pyc extensions the only ones which are associated with
>> Python or are there others, for a normal Python installation in Windows
>> ?
>
> There's also .pyw
Also .pyo
.py = Python source code, usually associated with c
On Sat, Jul 24, 2010 at 7:40 PM, Edward Diener
wrote:
> On 7/24/2010 6:25 AM, Mark Lawrence wrote:
>> On 24/07/2010 04:17, Edward Diener wrote:
>>> Are there any documents about multiple versionsof Python coexisting in
>>> the same OS ( Windows in my case ) and what pitfalls to look out for ? I
>>
On 7/24/2010 6:25 AM, Mark Lawrence wrote:
On 24/07/2010 04:17, Edward Diener wrote:
Are there any documents about multiple versionsof Python coexisting in
the same OS ( Windows in my case ) and what pitfalls to look out for ? I
have already run into a number of them. I installed Python 2.7 and
On 7/24/2010 6:25 AM, Mark Lawrence wrote:
On 24/07/2010 04:17, Edward Diener wrote:
Are there any documents about multiple versionsof Python coexisting in
the same OS ( Windows in my case ) and what pitfalls to look out for ? I
have already run into a number of them. I installed Python 2.7 and
On 24/07/2010 04:17, Edward Diener wrote:
Are there any documents about multiple versionsof Python coexisting in
the same OS ( Windows in my case ) and what pitfalls to look out for ? I
have already run into a number of them. I installed Python 2.7 and 3.1.2
into completely folders, but immediate
Are there any documents about multiple versionsof Python coexisting in
the same OS ( Windows in my case ) and what pitfalls to look out for ? I
have already run into a number of them. I installed Python 2.7 and 3.1.2
into completely folders, but immediately ran into serious problems
executing a
40 matches
Mail list logo
