Re: [Python-Dev] Problem building Python 2.7.5 with separate sysroot
Quoting Paul Smith p...@mad-scientist.net: My case may be unusual but even in a more formal cross-compilation environment it's not good to add /usr/include/..., or base such a decision on the behavior of the _build_ system. The offical procedure to cover unusual cases is to edit Modules/Setup. If you are not happy with the way in which modules are build, you can override all flags on a per-module basis there. It seems to me (keeping with the theme of this mailing list) that the add_multiarch_paths() function in setup.py is not right. Well, ..., yes. For the last two decades, the build process of Python was *always* wrong, and it always ever will be, in the sense that it doesn't support all cases that people come up with. The only way to deal with this, unfortunately, is to patch the build process for each new use case discovered. As Ned says: if you come up with a patch, don't hesitate to post it to the tracker. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] New FreeBSD 10.0-CURRENT buildbot
Afternoon (UTC+10), I'd like to request a new user/pass for a FreeBSD 10.0-CURRENT VM guest I've just setup as a dedicated buildbot slave to complement my other koobs-freebsd slaves. Also, with this and future additions to the FreeBSD buildslave set in mind, I think it might also be prudent for a rename to take place: koobs-freebsd9-amd64 koobs-freebsd9-amd64-clang (CC=clang) koobs-freebsd10-amd64 (clang is default here) Convention being: koobs-freebsdX[Y]-arch[-config] (Happy for feedback here) If there are any permutations or additions you'd like to specifically see for FreeBSD to increase coverage just let me know (Hint: I have a PandaBoard arm board here i'm getting up and running) I have ZFS DTrace to work with among other things, and the long term plan is to have FreeBSD buildbots running the full gamut of versions, from -RELEASE through -STABLE to HEAD branches. I'm on #python-dev IRC if someone needs to discuss. -- Regards, Koobs ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New FreeBSD 10.0-CURRENT buildbot
Date: Sun, 2 Jun 2013 15:12:43 +1000 From: koobs.free...@gmail.com To: python-dev@python.org Subject: [Python-Dev] New FreeBSD 10.0-CURRENT buildbot [...] koobs-freebsd10-amd64 (clang is default here) Does CPython code compiled with clang runs faster than gcc? Why did you chose clang? Any benchmarks? Any benefits? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] New FreeBSD 10.0-CURRENT buildbot
On Sun, Jun 2, 2013 at 12:51 PM, Carlos Nepomuceno carlosnepomuc...@outlook.com wrote: Date: Sun, 2 Jun 2013 15:12:43 +1000 From: koobs.free...@gmail.com To: python-dev@python.org Subject: [Python-Dev] New FreeBSD 10.0-CURRENT buildbot [...] koobs-freebsd10-amd64 (clang is default here) Does CPython code compiled with clang runs faster than gcc? Why did you chose clang? Any benchmarks? Any benefits? Clang is sometimes favored over gcc for its non-GPL license; I believe the FreeBSD project sees this as an important issue. In general, the more C compilers a piece of C code compiles on, the fewer bugs are left in it, because different C compilers tend to catch different problems - even with cranked up warnings. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 442: Safe object finalization
2013/5/18 Antoine Pitrou solip...@pitrou.net: Calling finalizers only once is fine with me, but it would be a change in behaviour; I don't know if it may break existing code. I agree with Armin that this is better behavior. (Mostly significantly consistent with weakrefs.) (for example, say someone is using __del__ to manage a freelist) Do you know if it breaks any of the projects you tested it with? -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 442: Safe object finalization
2013/5/18 Antoine Pitrou solip...@pitrou.net: Hello, I would like to submit the following PEP for discussion and evaluation. Will the API of the gc module be at all affected? I assume nothing will just be printed for DEBUG_UNCOLLECTABLE. Maybe there should be a way to discover when a cycle is resurrected? -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Validating SSL By Default (aka Including a Cert Bundle in CPython)
As of right now, as far as I can tell, Python does not validate HTTPS certificates by default. As far as I can tell this is because there is no guaranteed certificates available. So I would like to propose that CPython adopt the Mozilla SSL certificate list and include it in core, and switch over the API's so that they verify HTTPS by default. This is what most people are going to expect when using a https url (Especially after learning that Python 2.x doesn't verify TLS, but Python 3.x does). Ideally this would take the shape of attempting to locate the system certificate store if possible, and if that doesn't work falling back to the bundled certificates. That way the various Linux distros can easily have their copies of Python depend soley on their built in certs, but Windows, OSX, Source compiles etc will all still have a fallback value. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Validating SSL By Default (aka Including a Cert Bundle in CPython)
On Jun 2, 2013 10:22 PM, Donald Stufft don...@stufft.io wrote: As of right now, as far as I can tell, Python does not validate HTTPS certificates by default. As far as I can tell this is because there is no guaranteed certificates available. Relevant: http://bugs.python.org/issue13647 So I would like to propose that CPython adopt the Mozilla SSL certificate list and include it in core, and switch over the API's so that they verify HTTPS by default. This is what most people are going to expect when using a https url (Especially after learning that Python 2.x doesn't verify TLS, but Python 3.x does). Ideally this would take the shape of attempting to locate the system certificate store if possible, and if that doesn't work falling back to the bundled certificates. That way the various Linux distros can easily have their copies of Python depend solely on their built in certs, but Windows, OSX, Source compiles etc will all still have a fallback value. There's an existing request for this: http://bugs.python.org/issue13655 Cheers, Chris ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
