Re: [Python-Dev] PEP 7 updated

Does anyone know of a way to teach vim that C sources in a python checkout should have 4-space indents without changing the defaults for other C files? I use this in my vimrc: "" " indentation: use detectindent plugi

[Python-Dev] Python on Windows with CoApp

Howdy folks, Quick e-mail at 34,000ft (aren't wifi-enabled flights great?) to mention a new initiative that's been started by Microsoft called CoApp (Common Opensource Application Publishing Platform). The aim is simple: make open source software rock on Windows ;-) It's probably easiest to

[Python-Dev] configuring the buildbot to skip some tests?

I've got parc-tiger-1 up and running again. It's failing on test_tk, which makes sense, because it's running as a background twisted process, and thus can't access the window server. I should configure that out. I'm looking for documentation on how to configure the build slave so that it skips t

Re: [Python-Dev] bugs.python.org down?

On Wed, 12 May 2010 13:09:11 -0400, Terry Reedy wrote: > On 5/11/2010 7:16 PM, Antoine Pitrou wrote: > > > > Apparently the tracker has been unresponding for some time now, > > although port 80 still accepts connections. > > As I reported before, there have been on and off problems for days. > Me

Re: [Python-Dev] bugs.python.org down?

On 5/11/2010 7:16 PM, Antoine Pitrou wrote: Apparently the tracker has been unresponding for some time now, although port 80 still accepts connections. As I reported before, there have been on and off problems for days. Messages like (minutes ago) upon trying to login: "Service Temporarily Un

Re: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

On Wed, May 12, 2010 at 6:39 AM, James Y Knight wrote: > I think you'll be a lot happier just modifying Psyco than making everyone > else in the world change their compiler flags. Aye, there's the rub. Nobody's happier modifying Psyco. :) But that just means people will gradually have to stop us

Re: [Python-Dev] Possible patch for functools partial - Interested?

On Fri, May 7, 2010 at 17:02, Antoine Pitrou wrote: > It would be more useful to provide equality, hashing and repr to partial > itself, > rather than a subclass. Feel free to propose a patch :) Hi! I've done that. I've opened a feature request: http://bugs.python.org/issue8699 The patch is als

Re: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

> Short history: new GCC 4.5.0 (released a month ago), when compiling with > -O3, is adding MMX/SSE instructions that requires stack aligned to 16 > byte. This is wrong, since x86 ABI only requires stack aligned to 4 bytes. I think this is debatable. It depends on the operating system also; ultima

Re: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

On May 12, 2010, at 10:01 AM, Jesus Cea wrote: On 12/05/10 15:39, James Y Knight wrote: While assuming the stack is 16byte aligned is undeniably an ABI-violation in GCC, at this point, it's surely simpler to just go along: the new unofficial ABI for x86 is that the stack must always be left

Re: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/05/10 15:39, James Y Knight wrote: > While assuming the stack is 16byte aligned is undeniably an > ABI-violation in GCC, at this point, it's surely simpler to just go > along: the new unofficial ABI for x86 is that the stack must always be > left

Re: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/05/10 15:32, Nick Coghlan wrote: > Jesus Cea wrote: >> Proposal: add "-fno-tree-vectorize" to compilation options for 2.7/3.2. > > Will this actually help? Won't there still be a problem if any extension > module is compiled with GCC 4.5.0 witho

Re: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

On May 12, 2010, at 9:13 AM, Jesus Cea wrote: Short history: new GCC 4.5.0 (released a month ago), when compiling with - -O3, is adding MMX/SSE instructions that requires stack aligned to 16 byte. This is wrong, since x86 ABI only requires stack aligned to 4 bytes. If you compile EVERYTHI

Re: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

Jesus Cea wrote: > Proposal: add "-fno-tree-vectorize" to compilation options for 2.7/3.2. Will this actually help? Won't there still be a problem if any extension module is compiled with GCC 4.5.0 without that option, regardless of the options used to build Python itself? Cheers, Nick. -- Nick

[Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [Zlib-devel] HEADS UP: Apparent bad compilation under (just released) GCC 4.5.0 GCC Bugzilla Bug 40838 gcc shouldn't assume that the stack is aligned http://gcc.gnu.org/bugz

Re: [Python-Dev] Possible patch for functools partial - Interested?

On 5/11/2010 11:54 PM, Cameron Simpson wrote: > I know for functions "==" and "is" currently are equivalent, but we should be > really finicky here about intent, especially since a few messages in the > thread is contemplate testing function for equivalence to one degree or > other. At which point

Re: [Python-Dev] Possible patch for functools partial - Interested?

On Wed, 12 May 2010 06:34:50 pm Stephen J. Turnbull wrote: > Lie Ryan writes: > > it disappoints me this does not compare equal: > > > > add3 = lambda a, b, c: a + b + c > > a = partial(partial(add3, 1), 2) > > b = partial(partial(add3, 2), 1) > > print a == b > > > > :-) > > But it's not e

Re: [Python-Dev] Possible patch for functools partial - Interested?

Lie Ryan writes: > it disappoints me this does not compare equal: > > add3 = lambda a, b, c: a + b + c > a = partial(partial(add3, 1), 2) > b = partial(partial(add3, 2), 1) > print a == b > > :-) But it's not even true for floating point. ___ P

Re: [Python-Dev] Possible patch for functools partial - Interested?

On 05/08/10 03:57, Steve Holden wrote: > Steven D'Aprano wrote: >> >> [...] >>> Similarly, if you wanted p1==p2, why not write >>> >>> p1 = partial(operator.add) >>> p2 = p1 >> >> I thought the OP gave a use-case. He's generating "jobs" (partial >> applied to a callable and arguments), and