On Sun, Nov 7, 2010 at 3:53 AM, Giampaolo Rodolà wrote:
> In such cases I would find more easy to be able to connect to the
> machine and test myself rather than create a separate branch, commit,
> schedule a buildbot run, wait for it to complete and see whether
> everything is "green".
>
> On the
On Sat, Nov 6, 2010 at 11:41 PM, "Martin v. Löwis" wrote:
> Instead, I recall that a decision was made (and I'm not sure whether
> with consensus or not) that "make install" would install
> /usr/bin/python3, for the time being. Period.
Indeed, that's my recollection as well. Whether python3 ever
On Saturday 06 November 2010 22:36:44 you wrote:
> I couldn't find the matching failures that you're talking about, but
> then I figured out you mean the FreeBSD7 (7.2) buildbot, not the
> FreeBSD (6.4) buildbot
Search "test_concurrent_futures" in:
http://www.python.org/dev/buildbot/builders/
Giampaolo Rodolà writes:
> In such cases I would find more easy to be able to connect to the
> machine and test myself rather than create a separate branch, commit,
> schedule a buildbot run, wait for it to complete and see whether
> everything is "green".
I agree with both Stephen and Martin's
On Sat, Nov 6, 2010 at 7:19 AM, Victor Stinner
>
> I noticed "OSError: [Errno 23] Too many open files in system" errors on your
> FreeBSD buildbot. I would like to know if you configured a limit on the open
> files or maybe of child processes on this buildbot or not, or if it is a
> failure in Pyt
On 11/6/10 10:53 AM, Giampaolo Rodolà wrote:
> Personally, I would find this particularly useful for OSX since it's
> one of the few OSes I can't manage to virtualize and which often
> causes me problems.
Although I said this on IRC, I'll repeat the offer to the list for those
not present -- I'm o
On 11/6/10 6:43 AM, Eric Smith wrote:
On 11/6/10 1:16 AM, Ezio Melotti wrote:
str.format_map>
I've addressed all of these issues, although if anyone has suggestions
for the docstrings or documentation they'd be appreciated.
Thanks again.
--
Eric.
__
Current status from the tracker...
don't care: 22134
not closed: 2491
not selected: 1
open: 2451
languishing: 25
pending: 39
closed: 19604
That gives us...
2451 open
1 not selected
39 pending
25 languishing
2516 Total open
2451 open
39 languishing
Should be 39 pending here, not la
> sorry in advance if this sounds a little indiscreet, but I think it
> would be great if we'd have SSH access against some of the computers
> used to host buildbots.
The only way this can work is on a bilateral basis. If you need shell
access to one of the build slaves, contact the slave operator
On 11/06/2010 12:01 PM, Terry Reedy wrote:
On 11/6/2010 11:42 AM, R. David Murray wrote:
On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl wrote:
Am 06.11.2010 05:44, schrieb Ezio Melotti:
Hi,
On 05/11/2010 19.08, Python tracker wrote:
ACTIVITY SUMMARY (2010-10-29 - 2010-11-05)
Python track
Hi,
sorry in advance if this sounds a little indiscreet, but I think it
would be great if we'd have SSH access against some of the computers
used to host buildbots.
Personally, I would find this particularly useful for OSX since it's
one of the few OSes I can't manage to virtualize and which often
On 06/11/2010 19.01, Terry Reedy wrote:
On 11/6/2010 11:42 AM, R. David Murray wrote:
On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl
wrote:
Am 06.11.2010 05:44, schrieb Ezio Melotti:
Hi,
On 05/11/2010 19.08, Python tracker wrote:
ACTIVITY SUMMARY (2010-10-29 - 2010-11-05)
Python tracker a
On 11/6/2010 12:33 PM, "Martin v. Löwis" wrote:
This was a private function used on an unsupported platform, this should
do no harm. We’ve been bitten by “should do no harm” before though, so
I am ready to revert this change (and learn from this :)
Do as you like. I won't insist on it being re
On 11/6/2010 11:42 AM, R. David Murray wrote:
On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl wrote:
Am 06.11.2010 05:44, schrieb Ezio Melotti:
Hi,
On 05/11/2010 19.08, Python tracker wrote:
ACTIVITY SUMMARY (2010-10-29 - 2010-11-05)
Python tracker at http://bugs.python.org/
To view or res
On 11/6/2010 8:53 AM, Laurens Van Houtven wrote:
Experience teaches us that people do speak up more than they tend to
keep schtum. We do get feedback on most things, including the "NO
ARCH" rule.
It strikes me as reasonable to warn people that they would be wasting
their time typing out a mul
> This was a private function used on an unsupported platform, this should
> do no harm. We’ve been bitten by “should do no harm” before though, so
> I am ready to revert this change (and learn from this :)
Do as you like. I won't insist on it being reverted.
It's rather a matter of agreeing whe
> I'm skeptical that this change should be carried out, then.
Yes, I asked myself the same question. I had done the svnmerge from
py3k, and when I saw that only one change was left, I wondered whether I
should commit or revert.
> It's easy to argue that this can't possibly hurt (but I can certain
> Remove one trace of Mac OS 9 support (#7908 follow-up)
>
> This was overlooked in r80804. This change is not really a bug fix,
I'm skeptical that this change should be carried out, then.
It's easy to argue that this can't possibly hurt (but I can certainly
come up with code that will break
On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl wrote:
> Am 06.11.2010 05:44, schrieb Ezio Melotti:
> > Hi,
> >
> > On 05/11/2010 19.08, Python tracker wrote:
> >> ACTIVITY SUMMARY (2010-10-29 - 2010-11-05)
> >> Python tracker at http://bugs.python.org/
> >>
> >> To view or respond to any of the
On Sat, 06 Nov 2010 12:31:39 +0100, Martin wrote:
> Am 06.11.2010 12:19, schrieb Victor Stinner:
> > Hi,
> >
> > I noticed "OSError: [Errno 23] Too many open files in system" errors on
> > your
> > FreeBSD buildbot. I would like to know if you configured a limit on the
> > open
> > files or ma
Am 06.11.2010 05:44, schrieb Ezio Melotti:
> Hi,
>
> On 05/11/2010 19.08, Python tracker wrote:
>> ACTIVITY SUMMARY (2010-10-29 - 2010-11-05)
>> Python tracker at http://bugs.python.org/
>>
>> To view or respond to any of the issues listed below, click on the issue.
>> Do NOT respond to this messa
> But the previous consensus (at least, as I, and presumably many other
> people understood it) was that python2 would remain the owner of the
> name "/usr/bin/python" for the indefinite future, and python3 would
> be invoked with /usr/bin/python3.
Can you cite references for that (not that other
I'm sorry you feel that way.
Experience teaches us that people do speak up more than they tend to
keep schtum. We do get feedback on most things, including the "NO
ARCH" rule. At least so far, responses have not been anywhere near
what you'd expect if you'd tell people to "RTFM n00b" (in terms of
Am 06.11.2010 12:19, schrieb Victor Stinner:
> Hi,
>
> I noticed "OSError: [Errno 23] Too many open files in system" errors on your
> FreeBSD buildbot. I would like to know if you configured a limit on the open
> files or maybe of child processes on this buildbot or not, or if it is a
> failure
Hi,
I noticed "OSError: [Errno 23] Too many open files in system" errors on your
FreeBSD buildbot. I would like to know if you configured a limit on the open
files or maybe of child processes on this buildbot or not, or if it is a
failure in Python?
The first error always occurs in the first t
On 11/6/10 1:16 AM, Ezio Melotti wrote:
+.. method:: str.format_map(mapping)
+
+ Similar to ``str.forrmat(**mapping)``, except that ``mapping`` is
+ used directly and not copied to a :class:`dict` . This is useful
+ if for example ``mapping`` is a dict subclass.
Including the "__missing__" exa
26 matches
Mail list logo
