The win64 buildbot testing stage hangs. The only thing that I can see
is (I have no time to investigate further) in processexplorer:
'python -E -tt ../lib/test/regrtest.py -uall -rw' has started this process
which hangs:
'cmd /c ""C:\Program Files (x86)\Microsoft Visual Studio 8\VC\vcvarsall.ba
Right. Building Win98 or ME is insanity.
[double-takes]
Hey! Tim! Long time no see. Welcome back Don't be a stranger. :-)
We missed you.
--Guido
On Nov 15, 2007 5:22 PM, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Paul Moore]
> >>From a quick look, rmpyc.py is deleting .pyc and .pyo files in .
[Paul Moore]
>>From a quick look, rmpyc.py is deleting .pyc and .pyo files in ..\Lib.
> This could be done (I believe) using simply
>
>cd ..\Lib
>del /S *.pyc *.pyo
>
> I haven't tested this (no time right now) but certainly on XP, the del
> command accepts a /S flag to delete recursively.
On 15/11/2007, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Ideally, the clean step should not depend on Python existing. On Unix
> it doesn't need it!
>From a quick look, rmpyc.py is deleting .pyc and .pyo files in ..\Lib.
This could be done (I believe) using simply
cd ..\Lib
del /S *.pyc
On Nov 15, 2007 12:14 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> I'll make the change.
Thanks!
> And, btw: after a manual clean, the win64 buildbot compiles again.
Hm, how about running a cleanup step at the *start* of the build
instead of at the end? (Or at both ends if you want to reclaim
On Nov 15, 2007 1:03 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> The *real* problem is that both the build and the clean step require
> Python to work. The former uses it to build _ssl, the latter starts rmpyc.py.
> Since the python30.dll was not built, starting python.exe displays a
> messageb
Guido van Rossum schrieb:
> On Nov 15, 2007 12:14 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
>> I'll make the change.
>
> Thanks!
>
>> And, btw: after a manual clean, the win64 buildbot compiles again.
>
> Hm, how about running a cleanup step at the *start* of the build
> instead of at the end
Guido van Rossum schrieb:
> On Nov 15, 2007 11:35 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
>> Guido van Rossum schrieb:
>> > Perhaps changing the remaining occurrences to PyObject_Str will fix this?
>>
>> If PyObject_Unicode is #defined for backwards compatibility then the
>> occurences
>> sho
Guido van Rossum schrieb:
> On Nov 15, 2007 11:22 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
>> The Win64 buildbot currently fails to link python30.dll and _testcapi.pyd
>> because of an unresolved symbol PyObject_Unicode:
>>
>> http://python.org/dev/buildbot/3.0/amd64%20XP%203.0/builds/242/step-
On Nov 15, 2007 11:35 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Guido van Rossum schrieb:
> > Perhaps changing the remaining occurrences to PyObject_Str will fix this?
>
> If PyObject_Unicode is #defined for backwards compatibility then the
> occurences
> should not be changed, imo.
Even if
On Nov 15, 2007 11:22 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> The Win64 buildbot currently fails to link python30.dll and _testcapi.pyd
> because of an unresolved symbol PyObject_Unicode:
>
> http://python.org/dev/buildbot/3.0/amd64%20XP%203.0/builds/242/step-compile/0
>
> Does anyone have a
The Win64 buildbot currently fails to link python30.dll and _testcapi.pyd
because of an unresolved symbol PyObject_Unicode:
http://python.org/dev/buildbot/3.0/amd64%20XP%203.0/builds/242/step-compile/0
Does anyone have an idea why?
Thomas
___
Python-3
12 matches
Mail list logo
