Alf P. Steinbach wrote:
* Ethan Furman:
Mark Hammond wrote:
On 29/10/2009 11:06 AM, Alf P. Steinbach wrote:
So I suggest switching to some other more light-weight installer
technology.
Thanks for the suggestion, but I expect we will stick with MSI even
with its shortcomings. Using MSI
Mark Hammond wrote:
On 29/10/2009 11:06 AM, Alf P. Steinbach wrote:
So I suggest switching to some other more light-weight installer
technology.
Thanks for the suggestion, but I expect we will stick with MSI even with
its shortcomings. Using MSI files has significant other advantages,
par
* Gabriel Genellina:
En Wed, 28 Oct 2009 21:06:03 -0300, Alf P. Steinbach
escribió:
The installer did manage to do the rest of that part correctly: file
associations and PATHEXT variable.
The Python installer from python.org does NOT add .py and .pyw to
PATHEXT; the ActivePython one does.
En Wed, 28 Oct 2009 21:06:03 -0300, Alf P. Steinbach
escribió:
The installer did manage to do the rest of that part correctly: file
associations and PATHEXT variable.
The Python installer from python.org does NOT add .py and .pyw to PATHEXT;
the ActivePython one does.
(3) Tkinter not
* John Machin:
On Oct 29, 11:06 am, "Alf P. Steinbach" wrote:
(3) Tkinter not bundled, misleading & incomplete documentation.
With the file associations in place (the installer managed to do that) running
console programs works fine.
However, running Tkinter based programs does *not* work:
On Oct 29, 11:06 am, "Alf P. Steinbach" wrote:
> (3) Tkinter not bundled, misleading & incomplete documentation.
>
> With the file associations in place (the installer managed to do that) running
> console programs works fine.
>
> However, running Tkinter based programs does *not* work:
>
>
> imp
On Oct 29, 11:56 am, "Alf P. Steinbach" wrote:
> Summarizing the main differences 2.6 -> 3.1.1 that I know of so far: print is
> now a function (nice), "/" now always produces float result (unsure about
> that,
> it must surely break a lot or even most of existing code?), xrange() has been
> remo
* David Robinow:
On Wed, Oct 28, 2009 at 8:06 PM, Alf P. Steinbach wrote:
PS: This was not unexpected. It was exactly why I earlier didn't even look
at CPython (umpteen bad experiences with *nix ports) but used ActivePython.
It's not a *nix port. It's multiplatform and it works fine.
Your "
On Wed, Oct 28, 2009 at 8:06 PM, Alf P. Steinbach wrote:
> PS: This was not unexpected. It was exactly why I earlier didn't even look
> at CPython (umpteen bad experiences with *nix ports) but used ActivePython.
It's not a *nix port. It's multiplatform and it works fine. As you've
been told befor
* Mark Hammond:
On 29/10/2009 11:06 AM, Alf P. Steinbach wrote:
So I suggest switching to some other more light-weight installer
technology.
Thanks for the suggestion, but I expect we will stick with MSI even with
its shortcomings. Using MSI files has significant other advantages,
particul
On 29/10/2009 11:06 AM, Alf P. Steinbach wrote:
So I suggest switching to some other more light-weight installer
technology.
Thanks for the suggestion, but I expect we will stick with MSI even with
its shortcomings. Using MSI files has significant other advantages,
particularly in "managed"
* Gabriel Genellina:
En Wed, 28 Oct 2009 19:18:48 -0300, Alf P. Steinbach
escribió:
I thought it would be prudent to install 3.1.1 for Windows from
scratch, so I uninstalled everything (CPython, ActivePython), and then
installed Python 3.1.1.
In the "Advanced" option I told the installer to
* Gabriel Genellina:
En Wed, 28 Oct 2009 19:30:13 -0300, Alf P. Steinbach
escribió:
Hm, the installer forgot to clean up, leaving lots of files, so
contrary to the dialog's final message the system had been modified.
If those files are third-party libraries, this confirms my previous
post.
* Alf P. Steinbach:
* Alf P. Steinbach:
Hi.
Or, to whomever this concerns... ;-)
I thought it would be prudent to install 3.1.1 for Windows from
scratch, so I uninstalled everything (CPython, ActivePython), and then
installed Python 3.1.1.
In the "Advanced" option I told the installer to
En Wed, 28 Oct 2009 19:30:13 -0300, Alf P. Steinbach
escribió:
Hm, the installer forgot to clean up, leaving lots of files, so contrary
to the dialog's final message the system had been modified.
If those files are third-party libraries, this confirms my previous post.
It's not the 3.1.1
En Wed, 28 Oct 2009 19:18:48 -0300, Alf P. Steinbach
escribió:
I thought it would be prudent to install 3.1.1 for Windows from scratch,
so I uninstalled everything (CPython, ActivePython), and then installed
Python 3.1.1.
In the "Advanced" option I told the installer to compile packages.
* Alf P. Steinbach:
Hi.
Or, to whomever this concerns... ;-)
I thought it would be prudent to install 3.1.1 for Windows from scratch,
so I uninstalled everything (CPython, ActivePython), and then installed
Python 3.1.1.
In the "Advanced" option I told the installer to compile packages.
Th
Hi.
Or, to whomever this concerns... ;-)
I thought it would be prudent to install 3.1.1 for Windows from scratch, so I
uninstalled everything (CPython, ActivePython), and then installed Python 3.1.1.
In the "Advanced" option I told the installer to compile packages.
The compiler then found
18 matches
Mail list logo
