On 10/03/2014 12:51, Jurko Gospodnetić wrote:
Hi.
On 10.3.2014. 4:16, Mark Lawrence wrote:
It looks as if the upgrade from 3.3.4 to 3.3.5 has stolen my copies of
py.exe and pyw.exe from c:\windows. Before I raise an issue on the bug
tracker could someone please confirm this, as it wouldn't
Hi.
On 10.3.2014. 4:16, Mark Lawrence wrote:
It looks as if the upgrade from 3.3.4 to 3.3.5 has stolen my copies of
py.exe and pyw.exe from c:\windows. Before I raise an issue on the bug
tracker could someone please confirm this, as it wouldn't be the first
time I've managed to screw somethin
On 10/03/2014 08:40, Tim Golden wrote:
On 10/03/2014 03:16, Mark Lawrence wrote:
It looks as if the upgrade from 3.3.4 to 3.3.5 has stolen my copies of
py.exe and pyw.exe from c:\windows. Before I raise an issue on the bug
tracker could someone please confirm this, as it wouldn't be the first
t
Hi.
On 10.3.2014. 4:16, Mark Lawrence wrote:
> It looks as if the upgrade from 3.3.4 to 3.3.5 has stolen my copies of
> py.exe and pyw.exe from c:\windows. Before I raise an issue on the
> bug tracker could someone please confirm this, as it wouldn't be the
> first time I've managed to screw s
On 10/03/2014 03:16, Mark Lawrence wrote:
> It looks as if the upgrade from 3.3.4 to 3.3.5 has stolen my copies of
> py.exe and pyw.exe from c:\windows. Before I raise an issue on the bug
> tracker could someone please confirm this, as it wouldn't be the first
> time I've managed to screw somethin
On 10/03/2014 03:16, Mark Lawrence wrote:
> It looks as if the upgrade from 3.3.4 to 3.3.5 has stolen my copies of
> py.exe and pyw.exe from c:\windows. Before I raise an issue on the bug
> tracker could someone please confirm this, as it wouldn't be the first
> time I've managed to screw somethin
It looks as if the upgrade from 3.3.4 to 3.3.5 has stolen my copies of
py.exe and pyw.exe from c:\windows. Before I raise an issue on the bug
tracker could someone please confirm this, as it wouldn't be the first
time I've managed to screw something up.
--
My fellow Pythonistas, ask not what