Steven D'Aprano writes:
> The usual technique people tend to come up with is:
>
> x = s.pop()
> s.add(x)
>
> Which strikes many people (including myself) as inelegant. Surely "get
> an element" is a more fundamental operation than "get an element and
> remove it"?
Not in a literal urn
On Fri, Oct 30, 2009 at 8:29 PM, Steven D'Aprano wrote:
>> > Iterating over an iterable is
>> > what iterators are for.
>
> set.get(), or set.pick() as Wikipedia calls it, isn't for iterating over
> sets. It is for getting an arbitrary element from the set.
>
> If the requirement that get/pick() c
2009/10/30 Steven D'Aprano :
> On Sat, 31 Oct 2009 07:27:22 am A.M. Kuchling wrote:
>> On Fri, Oct 30, 2009 at 09:37:36PM +0100, Georg Brandl wrote:
>> > I don't like this. It gives a set object a hidden state, something
>> > that AFAICS no other builtin has.
>
> All objects have a reference count
On Sat, 31 Oct 2009 07:27:22 am A.M. Kuchling wrote:
> On Fri, Oct 30, 2009 at 09:37:36PM +0100, Georg Brandl wrote:
> > I don't like this. It gives a set object a hidden state, something
> > that AFAICS no other builtin has.
All objects have a reference count field which is hidden from Python
c
> Since I've never used any such service ("cloud"-based VMs), I'm not sure
> what the downsides would be. But it seems to be that it would be at least
> worth trying.
Not sure whether it's still relevant after the offers of individually
donated hardware. However, if you want to look into this, f
> Well the general situation would be slightly easier to appreciate if there
> was a
> public medium where buildbot info was exchanged, announcements done, and
> problems tracked. Some kind of tracker, tracker keyword, mailing-list, or
> anything else.
As for the tracker keyword - I created one (
twistedmatrix.com> writes:
>
> Is your idea that this would be for tracking issues with the *bots*
> themselves? That is, not just for tracking cases where some test method
> fails on a particular bot, but for tracking cases where, say, a bot's
> host has run out of disk space and cannot run
On Fri, Oct 30, 2009 at 09:37:36PM +0100, Georg Brandl wrote:
> I don't like this. It gives a set object a hidden state, something that
> AFAICS no other builtin has. Iterating over an iterable is what iterators
> are for.
It also makes the object thread-unsafe; there's no way for two threads
to
On Fri, 30 Oct 2009 at 19:46, Paul Moore wrote:
2009/10/30 C. Titus Brown :
Once things are up and running, I'll be prepared to do basic care and
feeding of the buildslave, but as my time is limited, it would be nice
if others would pitch in to help.
I would be somewhat unhappy about giving mo
On Fri, 30 Oct 2009 at 09:57, "Martin v. L?wis" wrote:
But the real reason for having a buildbot category (or at least a keyword)
would be to be able to tag all bugs that are currently making buildbots
fail that are _not_ the result of a recent checkin. This would make
the task of finding the bu
2009/10/30 C. Titus Brown :
>> As a counter-offer: Given remote access to however many Windows VMs
>> you want to provide, I'll get them up and running with buildslaves on
>> them. If that requires software such as Visual Studio, I have copies
>> via the MSDN licenses that I am happy to provide.
>
On Fri, Oct 30, 2009 at 04:58:29PM -, exar...@twistedmatrix.com wrote:
> 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:
>>>
>>>
Steven D'Aprano schrieb:
> On Wed, 28 Oct 2009 04:47:59 am Raymond Hettinger wrote:
>
>> A dict.get() can be meaningfully used in a loop (because the key can
>> vary). A set.get() returns the same value over and over again
>> (because there is no key).
>
> I don't believe anyone has requested tho
On Fri, Oct 30, 2009 at 11:45 AM, C. Titus Brown wrote:
> On Fri, Oct 30, 2009 at 11:42:30AM -0500, Olemis Lang wrote:
>> On Sun, Oct 25, 2009 at 9:13 AM, wrote:
>> > On 12:48 pm, c...@msu.edu wrote:
>> >>
>> >> [snip]
>> >>
>> >> The most *exciting* part of pony-build, apart from the always-riv
ACTIVITY SUMMARY (10/23/09 - 10/30/09)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
2483 open (+31) / 16582 closed (+19) / 19065 total (+50)
Open issues with patches: 989
Average
On 04:42 pm, ole...@gmail.com wrote:
On Sun, Oct 25, 2009 at 9:13 AM, 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
ago",
is the loose coupling
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 in
On Fri, Oct 30, 2009 at 04:49:51PM +, Paul Moore wrote:
> 2009/10/30 C. Titus Brown :
> > 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
2009/10/30 C. Titus Brown :
> 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
On Fri, Oct 30, 2009 at 11:42:30AM -0500, Olemis Lang wrote:
> On Sun, Oct 25, 2009 at 9:13 AM, 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 buildb
On Fri, Oct 30, 2009 at 05:41:39PM +0100, Antoine Pitrou wrote:
> Le vendredi 30 octobre 2009 ?? 09:31 -0700, C. Titus Brown a ??crit :
> > [ ... ]
> >
> > I'm happy to provide VMs or shell access for Windows (XP, Vista, 7); Linux
> > ia64; Linux x86; and Mac OS X. Others have made similar offers
On Sun, Oct 25, 2009 at 9:13 AM, 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
>> ago",
>> is the loose coupling of recording server to
Le vendredi 30 octobre 2009 à 09:31 -0700, C. Titus Brown a écrit :
> [ ... ]
>
> I'm happy to provide VMs or shell access for Windows (XP, Vista, 7); Linux
> ia64; Linux x86; and Mac OS X. Others have made similar offers. The
> architectures supported by the cloud services don't really add anyt
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 in this case.
> >
> >
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 in this case.
>
> First, there are now a multitude of cloud hosting providers which will
> operate a sl
Steven D'Aprano wrote:
>> So you want to introduce additional, hidden state to sets? (to make
>> sure that successive invocations return different values)
>
> If you can think of any other way to efficiently cycle over the elements
> in a set, I'm all for it :)
for x in itertools.cycle(s):
# t
Steven D'Aprano pearwood.info> writes:
>
> If you can think of any other way to efficiently cycle over the elements
> in a set, I'm all for it :)
How about "for x in s"?
Or if you want to cycle:
>>> s = set('abc')
>>> it = itertools.cycle(s)
>>> next(it)
'a'
>>> next(it)
'c'
>>> next(it)
'b'
On Fri, 30 Oct 2009 03:00:27 pm Raymond Hettinger wrote:
[skipping to the last paragraph]
> Sorry for so many questions
Don't be sorry. These are good questions, and I'll try to answer them.
But keep in mind that this isn't my proposal -- I vary between +0 and
+1 on the proposal depending on t
On Fri, Oct 30, 2009 at 10:15 AM, wrote:
> On 12:55 pm, jnol...@gmail.com wrote:
>>
>> On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. Löwis"
>> 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, i
On Fri, 30 Oct 2009 at 08:55, Jesse Noller wrote:
On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. L?wis" 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 skipped, it'
On 12:55 pm, jnol...@gmail.com wrote:
On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. Löwis"
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 skipped, it's a flaw in
On Fri, Oct 30, 2009 at 4:53 AM, "Martin v. Löwis" 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 skipped, it's a flaw in the build
> slave configuration (b
> Any thoughts/comments/ideas, anything?:)
Announce it to comp.lang.python.announce if you haven't done so, yet.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://ma
> Is there a place where the status of the ssl module is summarized
The documentation of the ssl module should describe its features
correctly and precisely.
> or a better place to discuss this? I could try to provide contributions or
> further details if appropriate.
For contributions, this is
> But the real reason for having a buildbot category (or at least a keyword)
> would be to be able to tag all bugs that are currently making buildbots
> fail that are _not_ the result of a recent checkin. This would make
> the task of finding the bugs that need to be cleaned up to stabilize
> the
Jesse Noller wrote:
> On Thu, Oct 29, 2009 at 8:31 PM, R. David Murray
> wrote:
>
>> I'd say that particular one is a bug in the tests. If /dev/shm is
>> not available and is required, then the tests should be skipped with
>> an appropriate message. It would also secondarily be an issue with
>
Am Freitag, 30. Oktober 2009 03:58:16 schrieb Steven D'Aprano:
> To clarify point 3, given:
>
> x = set.get()
> y = set.get()
>
> then x and y will only be the same element if set has length one.
> However, given:
>
> x = set.get()
> set.add(el)
> set.remove(el)
> y = set.get()
>
> there are n
Hi there,
yappi(Yet Another Python Profiler) is a multithreaded profiler for 2.x
series(do not know if it will work on 3k, not tested yet). I have done my
best to make it efficient as possible.(details are under the technical
bullet in the website). It is aimed for long-running programs, to
attach
38 matches
Mail list logo
