> SciTE doesn't do that, in the default configuration it just uses
> whatever is called "pythonw" on the path, for running files having a .py
> or .pyw suffix.
I see. By default, Python does not put itself onto PATH. Does that mean
that SciTE cannot run Python scripts in the default installation?
Glenn Linderman wrote:
On approximately 12/1/2008 11:29 PM, came the following characters from
the keyboard of Martin v. Löwis:
It would be nice if the ftypes were version specific as created by the
installer; IIRC, I created the above three from the ftype Python.File as
I installed each version
Glenn Linderman wrote:
> I'm unaware of it needing to handle multiple extensions
> from the command line or via double clicking in Explorer, so was
> exploiting the extra level of indirection to save typing, and make the
> command simpler to remember.
Python *does* provide multiple useful extensio
On approximately 12/4/2008 5:29 AM, came the following characters from
the keyboard of Colin J. Williams:
Glenn Linderman wrote:
The equivalent of those commands is available via Windows Explorer,
Tools / Folder Options, File Types, scroll-scroll-scroll your way to
.py, Click Advanced, fidd
Glenn Linderman wrote:
The equivalent of those commands is available via Windows Explorer,
Tools / Folder Options, File Types, scroll-scroll-scroll your way to
.py, Click Advanced, fiddle, copy paste apply, and other twaddle.
Yes, but what's needed is a further level of indirection. Curre
On approximately 12/3/2008 8:51 AM, came the following characters from
the keyboard of Colin J. Williams:
Martin v. Löwis wrote:
What changes are made to the registry?
For a complete list, see Tools/msi/msi.py in the source tree.
I have scanned the file:
http://svn.python.org/projects/python/
Martin v. Löwis wrote:
What changes are made to the registry?
For a complete list, see Tools/msi/msi.py in the source tree.
I have scanned the file:
http://svn.python.org/projects/python/branches/py3k/Tools/msi/msi.py
I don't find anything that addresses this issue.
Read the add_registry fu
On Dec 1, 4:49 pm, "Colin J. Williams" <[EMAIL PROTECTED]> wrote:
> Could anyone please point me to
> documentation on the way the msi
> installer handles multiple versions eg.
> Python 2.5, 2.6 and 3.0?
>
> What changes are made to the registry?
>
> Is there some way to specify a default
> version
Hi!
Multiple versions of Python is possible (example: Python standard +
Python by OOo).
But, multiple versions of Python+PyWin32 is not possible.
Suggestion: use VirtualBox or Virtual-PC.
@-salutations
--
Michel Claveau
--
http://mail.python.org/mailman/listinfo/python-list
> Using a right click, one can open any .py file with say SciTe. Within
> SciTe, one can Run the current file.
>
> It would be good to have the appropriate version (my use of "default")
> preselected.
I don't know how SciTe choses the version of Python to run. In the
sense in why you use the wor
Martin v. Löwis wrote:
What changes are made to the registry?
For a complete list, see Tools/msi/msi.py in the source tree.
I have scanned the file:
http://svn.python.org/projects/python/branches/py3k/Tools/msi/msi.py
I don't find anything that addresses this issue.
Read the add_registry fun
>>> What changes are made to the registry?
>>
>> For a complete list, see Tools/msi/msi.py in the source tree.
>
> I have scanned the file:
> http://svn.python.org/projects/python/branches/py3k/Tools/msi/msi.py
>
> I don't find anything that addresses this issue.
Read the add_registry function.
Martin v. Löwis wrote:
Could anyone please point me to documentation on the way the msi
installer handles multiple versions eg. Python 2.5, 2.6 and 3.0?
I don't think that is documented anywhere.
What changes are made to the registry?
For a complete list, see Tools/msi/msi.py in the source
> OK, Issue 4485 created. My first one, so let me know if I goofed. I
> elaborated a bit from the original email, upon reflection. Seemed
> useful, but also seemed complex by the time I got done.
Looks about right to me.
> I don't really have a clue what the uninstaller should do with these;
>
On approximately 12/1/2008 11:29 PM, came the following characters from
the keyboard of Martin v. Löwis:
It would be nice if the ftypes were version specific as created by the
installer; IIRC, I created the above three from the ftype Python.File as
I installed each version.
That's a good i
> It would be nice if the ftypes were version specific as created by the
> installer; IIRC, I created the above three from the ftype Python.File as
> I installed each version.
That's a good idea; please submit a wish list item to bugs.python.org.
There may be issues (such as people relying on this
On approximately 12/1/2008 11:05 PM, came the following characters from
the keyboard of Martin v. Löwis:
Is there some way to specify a default version in such a way that it can
be changed as necessary?
What do you mean by "default version"?
There is the version that is associated with th
> Could anyone please point me to documentation on the way the msi
> installer handles multiple versions eg. Python 2.5, 2.6 and 3.0?
I don't think that is documented anywhere.
> What changes are made to the registry?
For a complete list, see Tools/msi/msi.py in the source tree.
> Is there some
Could anyone please point me to
documentation on the way the msi
installer handles multiple versions eg.
Python 2.5, 2.6 and 3.0?
What changes are made to the registry?
Is there some way to specify a default
version in such a way that it can be
changed as necessary?
PyScripter uses an opt
19 matches
Mail list logo
