On 17/06/2014 04:08, Zachary Ware wrote:
On Mon, Jun 16, 2014 at 4:12 PM, Victor Stinner
wrote:
Hi,
I would like to know if Python 3.5 will still support Windows XP or
not. Almost all flavors of Windows XP reached the end-of-life in
April, 2014 except "Windows XP Embedded". There is even an ha
On Mon, Jun 16, 2014 at 4:12 PM, Victor Stinner
wrote:
> Hi,
>
> I would like to know if Python 3.5 will still support Windows XP or
> not. Almost all flavors of Windows XP reached the end-of-life in
> April, 2014 except "Windows XP Embedded". There is even an hack to use
> Windows upgrades on the
On 17 Jun 2014 03:42, "Chris Barker" wrote:
>
> On Sat, Jun 14, 2014 at 1:11 PM, Paul Sokolovsky
wrote:
>
>>
>> > > 1. It hampers interactive mode - instead of short and easy to type
>> > > execfile("file.py") one needs to use exec(open("file.py").read()).
>>
>> >
>> > If the amount of typing is
Hi,
I would like to know if Python 3.5 will still support Windows XP or
not. Almost all flavors of Windows XP reached the end-of-life in
April, 2014 except "Windows XP Embedded". There is even an hack to use
Windows upgrades on the desktop flavor using the embedded flavor (by
changing a key in the
On 06/16/2014 10:40 AM, Chris Barker wrote:
My conclusions:
1) runfile() is not really very usefull, it's fine to hve removed it.
s/runfile/execfile
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listin
On Sat, Jun 14, 2014 at 1:11 PM, Paul Sokolovsky wrote:
> > > 1. It hampers interactive mode - instead of short and easy to type
> > > execfile("file.py") one needs to use exec(open("file.py").read()).
>
> > If the amount of typing is the problem, that's easy to solve:
> >
> > # do this once
>
