Hopefully by now you have heard of the Summer of PyPy, our program
for funding the expenses of attending a sprint for students. If not,
you've just read the essence of the idea :-)
However, the PyPy EU funding period is drawing to an end and there is
now only one sprint left where we can sponsor
On 11/7/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Grig Gheorghiu schrieb:
One of the Pybots buildslaves running x86 Ubuntu Edgy has been failing
the unit test step for the trunk, specifically the test_ucn test.
Something is wrong with the machine. I forced a clean rebuild, and
now it
Martin v. Löwis wrote:
a) the directory cache is out of date, and you should
re-read the directory
b) the module still isn't there, but is available in
a later directory on sys.path (which hasn't yet
been visited)
c) the module isn't there at all, and the import will
eventually
Greg Ewing schrieb:
Martin v. Löwis wrote:
a) the directory cache is out of date, and you should
re-read the directory
b) the module still isn't there, but is available in
a later directory on sys.path (which hasn't yet
been visited)
c) the module isn't there at all, and the
Patch #841454 takes a stab at cross-compilation
(for MingW32 on a Linux system, in this case),
and proposes to use SCons instead of setup.py
to compile extension modules. Usage of SCons
would be restricted to cross-compilation (for
the moment).
What do you think?
Regards,
Martin
On Thursday 09 November 2006 16:30, Martin v. Löwis wrote:
Patch #841454 takes a stab at cross-compilation
(for MingW32 on a Linux system, in this case),
and proposes to use SCons instead of setup.py
to compile extension modules. Usage of SCons
would be restricted to cross-compilation (for
