> Does a modern windows installation actually even *work* if you change
> COMSPEC to command.com instead of cmd.exe? And why would anyone ever
> do that? Hey, I have a good idea: python can just ignore COMSPEC and
> always run cmd.exe. Then you can delete w9xpopen, hooray.
We have a process for th
On Feb 20, 2011, at 4:10 AM, Martin v. Löwis wrote:
> Am 20.02.2011 07:43, schrieb anatoly techtonik:
>> Python definitely needs a development Roadmap to avoid things like
>> w9xpopen.exe slipping off radar from release to release. We don't
>> support Windows 9x since Python 2.6. What this file d
On Sun, Feb 20, 2011 at 15:22, anatoly techtonik wrote:
> On Sun, Feb 20, 2011 at 11:10 AM, "Martin v. Löwis"
> wrote:
> > Am 20.02.2011 07:43, schrieb anatoly techtonik:
> >> Python definitely needs a development Roadmap to avoid things like
> >> w9xpopen.exe slipping off radar from release to r
On Sun, Feb 20, 2011 at 11:10 AM, "Martin v. Löwis" wrote:
> Am 20.02.2011 07:43, schrieb anatoly techtonik:
>> Python definitely needs a development Roadmap to avoid things like
>> w9xpopen.exe slipping off radar from release to release. We don't
>> support Windows 9x since Python 2.6. What this
Am 20.02.2011 07:43, schrieb anatoly techtonik:
> Python definitely needs a development Roadmap to avoid things like
> w9xpopen.exe slipping off radar from release to release. We don't
> support Windows 9x since Python 2.6. What this file does in 3.x
> distributions?
>
> http://bugs.python.org/iss