On 8 August 2012 18:56, Antoine Pitrou wrote:
> Le 08/08/2012 15:25, "Martin v. Löwis" a écrit :
>
>>
>> Of course, when somebody has access to SPARC hardware, *and* they
>> have some interest that Python 3.3 works on it, they should test it.
>> But testing it as a favor to the community is IMO ir
Does Python 3.3 support cross-compilation? There are two new option
for configure: --host and --build, but it's not mentioned in What's
New in Python 3.3.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/py
Le 08/08/2012 15:25, "Martin v. Löwis" a écrit :
Of course, when somebody has access to SPARC hardware, *and* they
have some interest that Python 3.3 works on it, they should test it.
But testing it as a favor to the community is IMO irrelevant now;
that particular community is shrinking rapidly
On Wed, Aug 8, 2012 at 12:54 AM, Raymond Hettinger
wrote:
> Hello all,
>
> I'll soon be starting the edits of Whatsnew for 3.3.
>
> When I did this for 3.2, it took over 150 hours of work to research all the
> changes. This time there are many more changes, so my previous process won't
> work (
Could someone with access to a SPARC machine (perhaps with a modern version
of Debian-sparc) grab a clone from http://hg.python.org/cpython/ and run
the test suite?
I'd invoke the "scratch your own itch" principle here. SPARC, these
days, is a "minority platform"; I wouldn't mind deleting all S
Nick Coghlan wrote:
> It does place a constraint on consumers that they can't assume those
> fields will be NULL just because they didn't ask for them, but I'm
> struggling to think of any reason why a client would actually *check*
> that instead of just assuming it.
Can we continue this discussi
Hello,
currently the only cheap way for developers to test on SPARC that I'm
aware of is using this old Debian qemu image:
http://people.debian.org/~aurel32/qemu/sparc/
That image still uses linuxthreads and may contain any number of platform
bugs. It is currently impossible to run the test sui
Hello all,
I'll soon be starting the edits of Whatsnew for 3.3.
When I did this for 3.2, it took over 150 hours of work to research all the
changes. This time there are many more changes, so my previous process won't
work (reviewing every "new in 3.3" entry in the docs, every entry in the
vol
