On 10 Feb, 02:47 pm, ole...@gmail.com wrote:
On Tue, Feb 9, 2010 at 6:15 PM, exar...@twistedmatrix.com wrote:
For what it's worth, we just finished *removing* support for
setUpClass and
tearDownClass from Trial.
Ok ... but why ? Are they considered dangerous for modern societies ?
On 04:18 pm, tsea...@palladion.com wrote:
Just as a point of reference: zope.testing[1] has a layer feature
which is used to support this usecase: a layer is a class namedd as an
attribute of a testcase, e.g.:
class FunctionalLayer:
@classmethod
def setUp(klass):
Do some
On 10:42 pm, fuzzy...@voidspace.org.uk wrote:
On 09/02/2010 21:57, Ben Finney wrote:
Michael Foordfuzzy...@voidspace.org.uk writes:
The next 'big' change to unittest will (may?) be the introduction of
class and module level setUp and tearDown. This was discussed on
Python-ideas and Guido
On 08:21 pm, ba...@python.org wrote:
On Feb 03, 2010, at 01:17 PM, Guido van Rossum wrote:
Can you clarify? In Python 3, __file__ always points to the source.
Clearly that is the way of the future. For 99.99% of uses of __file__,
if it suddenly never pointed to a .pyc file any more (even if one
On 10:29 pm, gu...@python.org wrote:
On Sat, Feb 6, 2010 at 12:49 PM, Ezio Melotti ezio.melo...@gmail.com
wrote:
In #7712 I was trying to change regrtest to always run the tests in a
temporary CWD (e.g. /tmp/@test_1234_cwd/).
The patches attached to the issue add a context manager that changes
On 6 Feb, 11:53 pm, gu...@python.org wrote:
On Sat, Feb 6, 2010 at 3:22 PM, exar...@twistedmatrix.com wrote:
On 10:29 pm, gu...@python.org wrote:
[snip]
I haven't tried to repro this particular example, but the reason is
that we don't want to have to call getpwd() on every import nor do we
On 03:57 pm, gu...@python.org wrote:
On Fri, Feb 5, 2010 at 5:28 AM, Antoine Pitrou solip...@pitrou.net
wrote:
Pascal Chambon pythoniks at gmail.com writes:
By the way, I'm having trouble with the name attribute of raw
files,
which can be string or integer (confusing), ambiguous if
On 04:58 pm, jaeda...@gmail.com wrote:
Jesse Noller jnoller at gmail.com writes:
We already have an implementation that spawns a
subprocess and then pushes the required state to the child. The
fundamental need for things to be pickleable *all the time* kinda
makes it annoying to work with.
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module basis to achieve much the same effect.
In Python 2.6 as well.
Jean-Paul
___
Python-Dev mailing list
On 03:21 pm, m...@egenix.com wrote:
exar...@twistedmatrix.com wrote:
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module basis to achieve much the same effect.
In Python 2.6 as well.
Right, but there are
On 10:47 pm, tjre...@udel.edu wrote:
On 1/29/2010 4:19 PM, Collin Winter wrote:
On Fri, Jan 29, 2010 at 7:22 AM, Nick Coghlanncogh...@gmail.com
wrote:
Agreed. We originally switched Unladen Swallow to wordcode in our
2009Q1 release, and saw a performance improvement from this across the
On 10:55 pm, collinwin...@google.com wrote:
That people are directly munging CPython
bytecode means that CPython should provide a better, more abstract way
to do the same thing that's more resistant to these kinds of changes.
Yes, definitely! Requesting a supported way to do the kind of
On 12 Jan, 10:04 pm, mar...@v.loewis.de wrote:
[...]
I've done a fair bit of 3.x porting, and I'm firmly convinced that
2.x can do nothing:
[...]
Inherently, 2.8 can't improve on that.
I agree that there are limitations like the ones you've listed, but I
disagree with your conclusion.
On 9 Dec, 06:09 pm, fuzzy...@voidspace.org.uk wrote:
On 09/12/2009 18:02, exar...@twistedmatrix.com wrote:
On 05:11 pm, lrege...@jarn.com wrote:
On Wed, Dec 9, 2009 at 17:34, Michael Foord
fuzzy...@voidspace.org.uk wrote:
Can you be more specific?
Only with an insane amount of work. I'll
On 05:11 pm, lrege...@jarn.com wrote:
On Wed, Dec 9, 2009 at 17:34, Michael Foord fuzzy...@voidspace.org.uk
wrote:
Can you be more specific?
Only with an insane amount of work. I'll hold that off for a while.
I don't know if this is related at all (and I guess we won't until
Lennart can be
On 09:44 am, lud...@lericson.se wrote:
Why are there comments on PyPI? Moreso, why are there comments which I
cannot control as a package author on my very own packages? That's
just absurd.
It's *my* package, and so should be *my* choice if I want user input
or not.
And ratings? I thought
On 03:01 pm, dalc...@gmail.com wrote:
On Thu, Nov 12, 2009 at 12:32 PM, Jesse Noller jnol...@gmail.com
wrote:
On Thu, Nov 12, 2009 at 9:25 AM, Barry Warsaw ba...@python.org
wrote:
On Nov 12, 2009, at 8:06 AM, Jesse Noller wrote:
Frankly, I agree with him. As implemented, I *and others* think
On 12:10 pm, s...@pobox.com wrote:
Guido ... it's IMO pretty mysterious if you encounter this and
don't
Guido already happen to know what it means.
If you require parens maybe it parses better:
import (a or b or c) as mod
Given that the or operator shortcuts I think that (a or b or
On 5 Nov, 11:55 pm, bobbyrw...@gmail.com wrote:
What exactly are those better ways? Document as deprecated only?
-Brett
A switch to ENABLE those warnings?
Lord knows I'm sick of filtering them out of logs.
A switch to enable deprecation warnings would give developers a
chance to see them
On 31 Oct, 08:13 pm, solip...@pitrou.net wrote:
Martin v. L�wis martin at v.loewis.de writes:
Not sure whether it's still relevant after the offers of individually
donated hardware.
We'll see, indeed.
However, if you want to look into this, feel free to
set up EC2 slaves.
I only know to
On 12:55 pm, jnol...@gmail.com wrote:
On Fri, Oct 30, 2009 at 4:53 AM, Martin v. Löwis mar...@v.loewis.de
wrote:
I'm confused: first you said they fail, now you say they get skipped.
Which one is it? I agree with R. David's analysis: if they fail, it's
a multiprocessing bug, if they get
On 04:31 pm, c...@msu.edu wrote:
On Fri, Oct 30, 2009 at 04:21:06PM +, Antoine Pitrou wrote:
Hello,
Sorry for the little redundancy, I would like to underline Jean-Paul's
suggestion here:
Le Sun, 25 Oct 2009 14:05:12 +, exarkun a ??crit??:
I think that money can help in two ways
On 04:42 pm, ole...@gmail.com wrote:
On Sun, Oct 25, 2009 at 9:13 AM, exar...@twistedmatrix.com wrote:
On 12:48 pm, c...@msu.edu wrote:
[snip]
The most *exciting* part of pony-build, apart from the always-
riveting
spectacle of titus rediscovering problems that buildbot solved 5
years
On 02:30 pm, solip...@pitrou.net wrote:
Hello,
What do you think of creating a buildbot category in the tracker?
There are
often problems on specific buildbots which would be nice to track, but
there's
nowhere to do so.
Is your idea that this would be for tracking issues with the *bots*
On 29 Oct, 11:41 pm, jnol...@gmail.com wrote:
On Thu, Oct 29, 2009 at 7:04 PM, exar...@twistedmatrix.com wrote:
On 02:30 pm, solip...@pitrou.net wrote:
Hello,
What do you think of creating a buildbot category in the tracker?
There
are
often problems on specific buildbots which would be
On 04:18 pm, dan...@stutzbachenterprises.com wrote:
On Mon, Oct 26, 2009 at 10:58 AM, Antoine Pitrou
solip...@pitrou.netwrote:
Er, I prefer to keep things simple. If you have lots of I/O you should
probably
use an event loop rather than separate threads.
On Windows, sometimes using a
On 12:16 pm, solip...@pitrou.net wrote:
For a), I think we can solve this only by redundancy, i.e. create more
build slaves, hoping that a sufficient number would be up at any point
in time.
We are already doing this, aren't we?
http://www.python.org/dev/buildbot/3.x/
It doesn't seem to
On 09:47 am, mar...@v.loewis.de wrote:
Mark Dickinson wrote:
Would it be worth spending some time discussing the buildbot situation
at the PyCon 2010 language summit? In the past, I've found the
buildbots to be an incredibly valuable resource; especially when
working with aspects of Python or
On 12:48 pm, c...@msu.edu wrote:
[snip]
The most *exciting* part of pony-build, apart from the always-riveting
spectacle of titus rediscovering problems that buildbot solved 5 years
ago,
is the loose coupling of recording server to the build slaves and build
reporters. My plan is to enable
On 05:47 pm, p.f.mo...@gmail.com wrote:
2009/10/25 exar...@twistedmatrix.com:
Perhaps this is a significant portion of the problem. Maintaining a
build
slave is remarkably simple and easy. I maintain about half a dozen
slaves
and spend at most a few minutes a month operating them. Actually
On 06:32 pm, mar...@v.loewis.de wrote:
I've been trying to get some feedback about firing up buildbots on
Cloud
Servers for a while now and haven't had much luck. I'd love to find a
way of having buildbots come to life, report to the mother ship, do
the
build, then go away 'till next time
On 25 Oct, 09:36 pm, db3l@gmail.com wrote:
I think the other issue most likely to cause a perceived downtime
with the Windows build slave that I've had a handful of cases over the
past two years where the build slave appears to be operating properly,
but the master seems to just queue up
On 01:28 am, db3l@gmail.com wrote:
exar...@twistedmatrix.com writes:
This sounds like something that should be reported
upstream. Particularly if you know how to reproduce it. Has it been?
No, largely because I can't reproduce it at all. It's happened maybe
4-5 times in the past 2 years
On 08:24 pm, mar...@v.loewis.de wrote:
Mike Krell wrote:
Is there any possibility of backporting support for the nonlocal
keyword
into a 2.x release?
If so, only into 2.7. Can you please explain why it would be desirable
to do that? 2.7 will likely be the last 2.x release, so only a fairly
On 08:16 pm, n...@arctrix.com wrote:
The current shutdown code in pythonrun.c zaps module globals by
setting them to None (an attempt to break reference cycles). That
causes problems since __del__ methods can try to use the globals
after they have been set to None.
The procedure implemented by
On 5 Oct, 01:04 pm, ziade.ta...@gmail.com wrote:
On Mon, Oct 5, 2009 at 2:50 PM, s...@pobox.com wrote:
Ned Due to a change in distutils released with Python 2.6.3,
packages
Ned that use setuptools (version 0.6c9, as of this writing), or
the
� �Ned easy_install command, to build C
On 03:57 am, mar...@v.loewis.de wrote:
Finally, to Stephen's point about seeing the other side of the
argument, I wrote this offlist a week ago:
I *understand* what you're saying, I *understand* that
192.168.1.1/24 isn't a network,
But you still want to treat it as one.
Could you explain
On 24 Sep, 11:27 pm, mar...@v.loewis.de wrote:
Additionally, I'm very apprehensive about doing any kind of release
without the buildbots running. Does anyone know when they might be
up?
When I (or somebody else) contacts all the slave operators and asks
them
to restart the buildbot slaves.
On 02:35 pm, benja...@python.org wrote:
Hi everyone,
I've started plotting the release of 2.7. I'd like to try for a final
release mid next summer. 3.2 should be released, if not at the same
time as 2.7, within a few weeks to avoid 2.x having features which 3.x
doesn't. If no one has problems
On 06:03 pm, br...@python.org wrote:
On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson benja...@python.org
wrote:
[snip]
Additionally, I'm very apprehensive about doing any kind of release
without the buildbots running. Does anyone know when they might be up?
I don't know the answer, but it
On 11:10 am, ncogh...@gmail.com wrote:
Steven D'Aprano wrote:
I've been skimming emails in this thread, since most of them go over
my
head and I have no current need for an ipaddress module. But one thing
I noticed stands out and needs commenting on:
On Wed, 16 Sep 2009 11:05:26 am Peter
On 12:59 pm, st...@pearwood.info wrote:
On Sun, 30 Aug 2009 06:55:33 pm Martin v. L�wis wrote:
Does it sound worthy enough to create a patch for and integrate
into python itself?
Probably not, given that people think that the algorithm itself is
fairly useless.
I would think that for most
On 12:49 am, benja...@python.org wrote:
I should probably mark that PEP as abandoned or deferred, since for
various reasons, it seems like this is not what Python-dev feels is
needed [1].
Re-reading that thread, I see some good discussion about how to improve
the PEP, a little bit of
On 04:08 pm, ch...@simplistix.co.uk wrote:
Hi All,
Would anyone object if I removed the deletion of of
sys.setdefaultencoding in site.py?
I'm guessing yes! so thought I'd state my reasons now:
This deletion appears to be pretty flimsy; reload(sys) and you have it
back. Which is lucky,
101 - 144 of 144 matches
Mail list logo
