On 3/6/07, Ron Adam <[EMAIL PROTECTED]> wrote:
> Neal Norwitz wrote:
>
> I'm looking forward to a new tracker and hope it manages single projects...
> (patches and bugs) better. It would be great if we could search for items
> based on possibly the following conditions.
On 3/6/07, Terry Reedy <[EMAIL PROTECTED]> wrote:
>
> ""Martin v. Löwis"" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> >1. Public identification will not help, because:
> >2. most code isn't in the responsibility of anybody (so publically
> >identifying responsibilities would
On 3/7/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>
> > Me, for example, has an actual question to this list: "How can I know,
> > if I change something in the doc's .tex files, that I'm not broking
> > the TeX document structure?".
>
> You don't have to know. As a general contributor, just s
On 3/7/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>
> We should try to keep the documentation buildable at all times so that it
> will remain visible to everyone at http://docs.python.org/dev/ .
Broken doc doesn't get pushed though. So the worst that will happen
is that the dev doc will be
Sorry for the delay. We really wanted to put out a 2.5.1 release
earlier. Due to busy and conflicting schedules, we had to postpone a
bit. We are on track for the following schedule:
2.5.1c1 - Tuesday, April 3
2.5.1 -Thursday April 12 (assuming a c2 is not necessary)
I don't know of any
On 3/7/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> A.M. Kuchling wrote:
>
> > FWIW, I have a related perception that we aren't getting new core
> > developers. These two problems are probably related: people don't get
> > patches processed and don't become core developers, and we don't have
>
On 3/5/07, Scott Dial <[EMAIL PROTECTED]> wrote:
>
> If nothing else, as an outsider there is no way to know why your patch
> gets ignored while others get swiftly dealt with. Any sort of
> information like this would at least provide more transparency in what
> may appear to be elitest processes.
On 3/10/07, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 09, 2007 at 10:10:48PM -0800, Neal Norwitz wrote:
> > We should probably be a lot more aggressive about closing bugs and
> > patches without response. Unfortunately many fall into this category.
>
> This
On 3/11/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> Jerry Seutter posted patch #1678088 yesterday, which converts
> test_operations over to use unittest and folds the resulting code into
> test_dict. It struck me as a good idea, because a) it gets away from
> output/-based tests, and b) test_ope
Unless someone speaks up to save Python/fmod.c, I'll remove this file
in a few days.
Thanks Paul!
n
--
On 3/10/07, Paul Hankin <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Is there any need for Python/fmod.c any more? I can't see how
> it can be included because there's no test for fmod in the
> ./c
Hi Alan.
Are you running on Windows or Unix? I just tested 2.4 - 2.6 on Linux
and all report:
Server socket: accept would not block
Client socket: write would not block
Which seems to be what you would expect unless I read it wrong.
I vaguely remember some issue about an empty hostname on Wind
There are several failures with both the trunk and 2.5 branch. I have
fixed one problem that allows the tests to run on Windows. That was
fixed by reverting 54407 on the trunk. It still needs to be reverted
on the 2.5 branch. You can go back in the buildbot logs to find out
more about the probl
On 3/21/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> [Raymond]
> >> What are the current thoughts on when Py2.5.1 will go out?
> >> Do we need a bug-day beforehand?
>
> [AMK]
> >A bug day would be a great idea! I have a mailbox bug that'd
> >greatly benefit from discussion about how to fix t
This is a reminder that the 2.5 branch will be frozen early next week.
If there are changes you want to get into 2.5.1, they should be
checked in within a few days. Be conservative! There will be a
2.5.2, it's better to wait than to have to make a new release for one
rushed feature. If you don'
On 3/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Neal> If you don't believe, just wait until Anthony shows up at your
> Neal> doorstep. :-)
>
> And later sends you a bill for the airline tickets. ;-)
No, no. He just pays with the tickets from your bank account or
credit card. D
On 4/11/07, Thomas Heller <[EMAIL PROTECTED]> wrote:
>
> On the 2.5.1 page http://www.python.org/download/releases/2.5.1/
> several things are wrong:
Can someone help fix this? I think Anthony is sleeping right now and
generally pretty busy.
Thanks,
n
I reverted both changes. They can be re-applied after the 2.5 is unfrozen. -- n
On 4/15/07, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> On Saturday 14 April 2007 10:07, Kristján Valur Jónsson wrote:
> > Hello all.
> > I made two checkins to the 25 maintainance branch before Martin
> > kindly poin
On 4/12/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> Ralf, your issue is arising because of revision 53655 which fixes SF 1615701.
I have backed out this change for 2.5.1.
> Am leaving this open for others to discuss and decide. The old behavior was
> surprising to some, but the revised be
There were some SystemErrors on one of the Windows build slaves. Does
anyone have any ideas what might be the cause? I looked through about
5 previous logs on the same slave and didn't see the same problem. I
haven't seen this myself and I don't know if it's WIndows specific. I
don't know if th
On 4/23/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> Fast and simple: I want all stdlib test cases to stop subclassing
> unittest.TestCase and start subclassing test_support.TestCase.
Go for it!
n
___
Python-Dev mailing list
Python-Dev@python.org
http
On 4/23/07, Yaakov Nemoy <[EMAIL PROTECTED]> wrote:
> Hi List,
>
> i want to post a little bit of something I've been working on. Before
> I post it, i want to know if I'm allowed to post it as an attachment.
> Coming up, some work on ASTVisitor in the compiler module.
Hi Yaakov.
If you'd like t
On 4/24/07, Kumar McMillan <[EMAIL PROTECTED]> wrote:
>
> Here is a very small portion of it, with the fix, which was putting a
> ref to the exc_info vars outside the tries and specifically del'ing
> them in the finally block:
Kumar,
Can you create a completely self-contained code example that tr
I just checked in a whitespace normalization change that was way too
big. Should this task be automated?
Assuming the answer is yes, these are the questions should be answered:
1) Which branches should this occur on: trunk, 2.5 (last release), 3k
2) Should there be a special user for these che
No need to worry about it, I fixed the failing test. Although it
would be good to review the comments and make them more accurate.
Take a look at the last change to test_pty.py.
n
--
On 4/29/07, Jerry Seutter <[EMAIL PROTECTED]> wrote:
> I was mucking about in test_pty.py not too long ago. I'll
PEP 11 notes that Mac OS 9 support was unsupported in 2.4. There are
still quite a few places that we check for sys.platform == 'mac'.
There are also (at least) 2 modules (macpath and macurl2path) that
look specific to Mac OS. (OS X has sys.platform == 'darwin'.)
Shall I add a deprecation warnin
This is the third time I've seen a crash on 2 different machines.
This is the first time I noticed this unexplained crash:
http://python.org/dev/buildbot/all/amd64%20gentoo%20trunk/builds/1983/step-test/0
That was at r54982.
I tried to reproduce this: with a non-debug build, with a debug build,
ecodec', 'test_weakref',
'test_ftplib', 'test_posixpath', 'test_xmlrpc', 'test_urllibnet',
'test_old_mailbox', 'test_distutils', 'test_site', 'test_runpy',
'test_fork1', 'test_traceback'])
On 5/6/07, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> I lost the key I originally gave for commiting my summaries. Who do I
> talk to about fixing that?
Send your new key to pydotorg. -- n
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.p
Part of the problem might be that we are using an old version of svn
(1.1) AFAIK. IIRC these operations were sped up in later versions.
n
--
On 5/8/07, Kristján Valur Jónsson <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hello there.
>
> Does anyone know why getting the SVN logs for a project is so excru
Which is correct?
$ egrep '(False|True)' Doc/lib/*.tex | grep -c \\constant{
74
$ egrep '(False|True)' Doc/lib/*.tex | grep -c \\code{
204
$ egrep 'None' Doc/lib/*.tex | grep -c \\code{
512
$ egrep 'None' Doc/lib/*.tex | grep -c \\constant{
83
n
___
Pyt
Martin,
I'm looking at Python/marshal.c and there are a lot of places that
don't support sequences that are larger than would fit into size(int).
I looked for marshal referenced in the PEP and didn't find anything.
Was this an oversight or intentional?
To give you some examples of what I mean fr
On 5/15/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > I'm looking at Python/marshal.c and there are a lot of places that
> > don't support sequences that are larger than would fit into size(int).
> > I looked for marshal referenced in the PEP and didn't find anything.
> > Was this an oversig
I had a little argument with the marshal module on Windows last night,
I eventually won. :-)
A patch was checked in which would prevent blowing out the stack and
segfaulting with this code:
marshal.loads( 'c' + ('X' * 4*4) + '{' * 2**20)
Originally, I didn't change the recursion limit which
Are the following accepted PEPs implemented and should be marked final:
SA 358 The "bytes" Object Schemenauer, GvR
SA 3106 Revamping dict.keys(), .values() & .items() GvR
SA 3109 Raising Exceptions in Python 3000Winter
SA 3110 Catching Exceptions in
On 5/18/07, Collin Winter <[EMAIL PROTECTED]> wrote:
>
> > SA 3110 Catching Exceptions in Python 3000 Winter
>
> This is implemented (I'll update the PEP to reflect this). Has a
> decision been made as to whether 2.6 will support both "," and "as" in
> except statements?
I think 'excep
On 5/18/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 5/18/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > On 5/18/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> > >
> > > > SA 3110 Catching Exceptions in Python 3000 Winter
> &g
On 5/22/07, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote:
>
> As you see, cStringIO's code also needs a good cleanup to make it,
> at least, conforms to PEP-7.
Alexandre,
It would be great if you could break up unrelated changes into
separate patches. Some of these can go in sooner rather than
On 5/23/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Trent Mick schrieb:
> > http://www.python.org/dev/buildbot/all/x86%20W2k%20trunk
> >
> > Is my buildbot the only reliable Windows buildbot machine?
>
> Tim Peter's machine comes and goes, depending on whether he starts
> the buildbot. Alan
On 5/25/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> In my bcannon-objcap branch I am trying to check in a change that involves a
> soft symlink from Lib/controlled_importlib.py to
> ../importlib/controlled_importlib.py through ``ln -s
> ../controlled_importlib.py controlled_importlib.py`` while i
On 5/26/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
>
> On 5/25/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> > Neal Norwitz schrieb:
> > > On 5/25/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > >> In my bcannon-objcap branch I am try
On 5/26/07, Peter Åstrand <[EMAIL PROTECTED]> wrote:
>
> I'm unable to commit tonight:
>
> SendingDoc/lib/libsubprocess.tex
> SendingLib/subprocess.py
> SendingLib/test/test_subprocess.py
> Transmitting file data ...svn: Commit failed (details follow):
> svn: 'pre-commit' ho
On 5/26/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> >
> > I tried to fix it so you can check in links, but that didn't work. I
> > commented out the change, so you should be able to commit again.
>
> Odd... the call worked here (SVN 1.4.3). Which version is the server using?
I don't know. Aft
One other thing to check is to ensure that sqlite was compiled with
-fno-strict-aliasing. I know there was a strange problem on one of
the buildbots due to this flag not being present. I have no idea if
that could be your problem here though.
n
--
On 5/28/07, "Martin v. Löwis" <[EMAIL PROTECTED
On 6/13/07, ocean <[EMAIL PROTECTED]> wrote:
> > Meanwhile I tried to replace the parsing I did with Plex by re.Scanner.
> And
> > again there is a remarkable speed difference. Again python2.5 is slower:
> >
> > try:
> > from re import Scanner
> > except:
> > from sre import Scanner
> >
> >
On 7/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> ... there is a heavy Google bias in the existing survey sample ...
Not just this survey...
There are many python developers at Google and that is not likely to
change anytime soon. This means that it's even more important to hear
diffe
On 7/12/07, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote:
>
> Phillip Eby:
> > Testing your package before you zip it, would be one. :) My
> > personal main interest was in being able to add an item to sys.path
> > without having to set $PYTHONPATH on Windows. That's why I'd like it
> > to b
It's about that time of year again. We are starting to organize
Python sprints again this year hosted at Google (ie, there was a 5
minute conversation and a couple of emails). Nothing has solidified
yet, but here are our ideas:
* Hosted at Google's headquarters in Mountain View, CA USA
* From
Martin,
Do you know why T_PYSSIZET is inside a #ifdef HAVE_LONG_LONG? That
seems like a mistake. Here's the code:
#ifdef HAVE_LONG_LONG
#define T_LONGLONG 17
#define T_ULONGLONG 18
#define T_PYSSIZET 19 /* Py_ssize_t */
#endif /* HAVE_LONG_LONG */
ISTM, that T_PYSSIZET should be
On 8/15/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > Sounds like a good plan. I'm not a great coach though since I didn't
> > write _ssl.c and I've never used openssl directly. But I can help you
> > with the Python stuff of course!
>
> Thanks (though I think I can handle the Python end of it, t
On 8/15/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Georg Brandl schrieb:
> >
> > Neal will change his build scripts, so that the 2.6 and 3.0 devel
> > documentation pages at docs.python.org will be built from these new
> > trees soon.
>
> Okay, I made the switch. I tagged the state of both Pyth
On 8/17/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Neal added it in rev 43214, when it was still PEP 3000. I'm sure he
> didn't read PEP 11 and beyond that I doubt he remembers from where he
> pulled this info. :-)
When I added it in 43214, it was in an outstanding questions section.
It was
On 8/21/07, Hrvoje Nikšić <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-08-20 at 20:27 +0200, Maciej Fijalkowski wrote:
> > import thread
> >
> > while 1:
> > f = open("/tmp/dupa", "w")
> > thread.start_new_thread(f.close, ())
> > f.close()
>
> file_close inadvertently allows fclose to be c
On 8/22/07, Hrvoje Nikšić <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-08-21 at 09:14 -0700, Neal Norwitz wrote:
> > The patch is insufficient to prevent all types of crashes that occur
> > when accessing a file from 2 threads (closing in one and doing
> > whatever in anot
On 8/23/07, Hrvoje Nikšić <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-08-22 at 21:32 -0700, Neal Norwitz wrote:
> > Py_BEGIN_ALLOW_THREADS
> > errno = 0;
> > - ret = _portable_fseek(f->f_fp, offset, whence);
> > + if (f-&g
On 8/24/07, Hrvoje Nikšić <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-08-23 at 11:57 -0700, Neal Norwitz wrote:
> > > "allow threads" section that runs with the GIL released, file_close
> > > might acquire the GIL and be running in parallel to this code. If
>
It looks like you found the meta tracker rather than the python one.
To reset your password for the main python tracker:
http://bugs.python.org/[EMAIL PROTECTED]
To report bugs, go here:
http://bugs.python.org/
To register a new account, go here:
http://bugs.python.org/[EMAIL PROTECTED]
N
Bill,
Could you also look into this problem:
Traceback (most recent call last):
File "/home/pybot/buildarea/trunk.klose-debian-ia64/build/Lib/threading.py",
line 486, in __bootstrap_inner
self.run()
File
"/home/pybot/buildarea/trunk.klose-debian-ia64/build/Lib/test/test_ssl.py",
line 144
On 8/26/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > This occurs on at least 3 of the buildbots (ubuntu and debian on ia64,
> > ppc, and hppa). Here's one example:
> >
> > http://python.org/dev/buildbot/all/ia64%20Ubuntu%20trunk%20trunk/builds/832/step-test/0
>
> If I'm reading this right, it's
Thanks. I applied it. -- n
On 8/26/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> Well, as long as you have your ears on, here's another patch to test_ssl.
>
> 1) Fixes the bug that two class names are initial-lower-case.
>
> 2) Replaces the poll waiting for the server to become ready with
>
Bill,
Please mail your ssh key as an attachment to [EMAIL PROTECTED]
n
--
On 8/28/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Hi Bill,
>
> I think it's time you get to do your own checkins. There's a protocol
> but I forget how to do it -- I think you mail your ssh key to Martin.
>
> --Gui
We are planning the release of 2.5.2 for next week. Unless there are
serious bugs, please hold off making big changes to the 2.5 branch
until after 2.5.2 final is released. Anthony gets cranky when things
break and he scares me...a lot. :-) Doc/test fixes as always are
still fine.
The plan is c
On Oct 11, 2007 11:36 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
>
> Neal, I have one patch for ctypes still sitting in some of my sandboxes.
> ctypes doesn't work when configured with --with-system-ffi on machines
> where 'sizeof(long long) != sizeof(long)', in other words on 32-bit boxes.
>
> I
On Oct 24, 2007 7:22 AM, Facundo Batista <[EMAIL PROTECTED]> wrote:
> 2007/10/12, Neal Norwitz <[EMAIL PROTECTED]>:
>
> > The plan is cut the release candidate around Tuesday/Wednesday next
> > week (Oct 16/17). If all goes well, 2.5.2 final will follow a week
>
There are many warnings from the trunk (and 2.5) builds on Win64. I
suspect quite a few of these are real problems. Win64 is the most
unusual platform wrt 64-bits due to long being 32-bit. If we need
64-bits, we need to use Py_ssize_t.
IIRC, we've had some bug reports for Win64. I know I've fi
Mike, thanks for reviewing the bugs and for creating a patch. Good work!
On Nov 2, 2007 2:23 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Mike Klaas wrote:
> > http://bugs.python.org/issue1705170: reproduced. Conjecture as to
> > why it is occurring, but I don't know the guts well enough to pr
On Nov 13, 2007 1:05 PM, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
>
> I can also help on win32 specific development. As an example, I find
> that the distutils module don't work very well with the new compilers.
> I won't be of much help on Unix, though.
We need more help on Windows! Most
On Nov 30, 2007 7:16 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Nov 30, 2007 12:02 PM, Neil Toronto <[EMAIL PROTECTED]> wrote:
> > On both of my systems, using -O2 reduces execution time in pystone by 9%
> > and in pybench by 8%. It's function inlining: "-O3
> > -fno-inline-functions" works j
On Dec 2, 2007 11:29 AM, Chad Austin <[EMAIL PROTECTED]> wrote:
> Hi Antoine,
>
> Antoine Pitrou wrote:
> > Hi,
> >
> > (I was asked to forward this from the bug tracker)
> >
> >> We have also run into problems where a task tries to "return" (yield
> >> Return())
> >> from within a try: except Exc
Hi Titus. Great work on GHOP!
On Dec 21, 2007 3:05 AM, Titus Brown <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> a bit of grep'ping and personal examination discovered the following
> tests in trunk/ that could be converted to unittest or doctests. Any
> thoughts, pro or con?
Yes, it would be great
On Jan 9, 2008 1:12 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Thomas Heller wrote:
> > Seems they are referring to the results of the rung 1 run (what ever 'rung'
> > means ;-).
> > With the account Neal made me some months ago, I can login on this page:
> >
> >http://scan.coverity.com
On Jan 9, 2008 9:08 AM, <[EMAIL PROTECTED]> wrote:
>
> Christian> I read the announcement of the Python Users list and figured
> Christian> out that some of the other core developers might be
> Christian> interested in the news, too.
>
> Christian> Among other projects Python was u
On Jan 9, 2008 9:08 AM, <[EMAIL PROTECTED]> wrote:
>
> I went to the run2 page:
>
> http://scan.coverity.com/rung2.html
>
> I shows 6 uninspected defects for Python. How do we see what they are?
> What is an uninspected defect? Any idea how the Coverity folks compute
> Defects/KLOC? For exa
to be added.
n
--
>
>
> On Jan 10, 2008 10:57 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> > Neal Norwitz wrote:
> > > I think only Coverity can add people. You can send them a message if
> > > you would like to be added: [EMAIL PROTECTED] Or you can
We need to fix the Windows buildbots. 2 tests are currently failing
for 2.5.2: test_mailbox test_winreg
From:
http://www.python.org/dev/buildbot/all/x86%20XP-4%202.5/builds/107/step-test/0
The errors are:
File
"E:\cygwin\home\db3l\buildarea\2.5.bolen-windows\build\lib\test\test_mailbox.py
Around Jan 13, the refleak hunting test that is reported on
python-checkins started to report refleaks on virtually every run. I
suspect this is due to r59944 (at 2008-01-13 16:29:41) which was from
patch #1700288 to cache methods. With this patch it makes it much
harder to spot refleaks. Does a
On Jan 27, 2008 3:37 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Phillip J. Eby wrote:
> > Expose an API to clear the cache, and clear it at shutdown? It
> > should probably be part of interpreter shutdown anyway.
>
> Good point. I've implemented PyType_ClearCache and exposed it via
> sys._c
On Jan 31, 2008 1:42 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Martin v. Löwis wrote:
> |> As current bsddb module maintainer, I was wondering if 2.5.2 will
> |> support BerkeleyDB 4.6 :-?.
> |
> | Maybe I'm misunderstanding the question - whom a
On Feb 1, 2008 2:52 PM, Mark Dickinson <[EMAIL PROTECTED]> wrote:
> The IBM format is particularly troublesome because
> it's base 16 instead of base 2 (so e.g. multiplying a float by 2 can lose
> bits), but it appears that recent IBM machines do both IBM format and IEEE
> format floating-point.
On Feb 7, 2008 5:09 AM, Andrew MacIntyre <[EMAIL PROTECTED]> wrote:
>
> So I've been testing with the freelists ripped out and ints and floats
> reverted to fairly standard PyObject_New allocation (retaining the small
> int interning) and thus relying on PyMalloc to do any compaction.
>
> The resul
On Feb 8, 2008 10:54 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Andrew MacIntyre wrote:
> > However, my tests do show that something is funny with the current
> > freelist implementation for floats on at least 2 platforms, and that
> > doing without that sort of optimisation for float object
On Thu, Feb 21, 2008 at 2:26 PM, Eric Smith
<[EMAIL PROTECTED]> wrote:
> I'm going to work on backporting PEP 3127, specifically the hex, oct(),
> and bin() builtins. I have bin() completed, and I'll check it in
> shortly. oct() will require a future import. Does anyone have any
> pointers fo
On Thu, Feb 21, 2008 at 7:43 AM, Giampaolo Rodola' <[EMAIL PROTECTED]> wrote:
>
> I have usually seen a lot of tests implemented like this:
>
> from test.test_support import TESTFN, unlink
> import unittest
>
> class TestCase(unittest.TestCase):
>
> def setUp(self):
> self.file = No
On Fri, Feb 22, 2008 at 11:15 AM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] schrieb:
>
> > This message has been popping up in the buildbot mails for several days:
> >
> > > Conflict detected in commontex/boilerplate.tex. Doc build skipped.
> >
> > I have no idea what it
+1 to everything -- n
On Fri, Feb 22, 2008 at 3:45 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> I've volunteered to be the release manager for Python 2.6 and 3.0.
> It's been several years since I've RM'd a Python release, a
On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> I do think map() and filter() should issue a warning under -3 when the
> first arg is None. (Or does 2to3 detect this now?)
What's wrong with filter(None, seq)? That currently works in 3k:
>>> filter(None, range(5
Short description (see http://bugs.python.org/issue2181 for the patch
and more details):
Optimize code like:
x = any_expression
return x
to:
return any_expression
The local variable x is no longer set before returning. Is this
appropriate for .pyc generation or should it only be done f
On Sun, Feb 24, 2008 at 6:57 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Sat, Feb 23, 2008 at 5:59 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > On Sat, Feb 23, 2008 at 8:06 AM, Guido van Rossum <[EMAIL PROTECTED]>
> wrote:
> > >
> > &g
On Sun, Feb 24, 2008 at 6:52 PM, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> Yesterday's bug day was another success, closing 48 issues. Several
> committers were there: Facundo Bastista, Georg Brandl, and Christian
> Heimes. Facundo organized a local group of participants, and we
> committed a
On Mon, Feb 25, 2008 at 2:20 PM, Bugbee, Larry <[EMAIL PROTECTED]> wrote:
> Hi Barry,
>
> A question Do you know if OpenSSL's applink.c will be included in
> the Windows builds? If so, and I hope it is, great!
>
> If not, I'd like to encourage its inclusion.
The best way to encourage its
On Mon, Feb 25, 2008 at 12:53 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>
> That's a really good idea. At least for the alpha's I would like to
> have a policy that the monthly release goes out unless
>
> 1) There are critical bugs open for 2.6 and/or 3.0
> 2) The important buildbots are red
On Mon, Feb 25, 2008 at 10:35 PM, Jeroen Ruigrok van der Werven
<[EMAIL PROTECTED]> wrote:
> -On [20080226 06:05], Neal Norwitz ([EMAIL PROTECTED]) wrote:
> > sparc solaris10
> > amd64 gentoo (this is really an ubuntu 6.10 box)
> > x86 gentoo (*)
> > g4 os
On Tue, Feb 26, 2008 at 12:07 AM, Jeroen Ruigrok van der Werven
<[EMAIL PROTECTED]> wrote:
> -On [20080226 08:09], Neal Norwitz ([EMAIL PROTECTED]) wrote:
> >I agree with the theory. However, we have only a single BSD box
> >currently working and it has been flaky. Prima
On Tue, Feb 26, 2008 at 11:47 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> Well, in my opinion "batteries included" is great, but not when one of
> the batteries consistently acts up and requires a good shake to get
> working again. The bsddb module has consistent reliability issues when
> i
Trent, thanks for working on the buildbot. I fixed the first case you
mentioned in r61233 wrt removing the directory before closing the
file. It would be great if you could submit a patch when you are able
to fix the remaining problems.
Cheers,
n
On Tue, Mar 4, 2008 at 6:58 AM, Trent Nelson <[E
On Tue, Mar 4, 2008 at 3:46 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
>
> That said, it is my aim to keep bsddb in stdlib, providing a stable and
> featureful module. I think keeping bsddb development inside python svn
> is not appropiate. Currently (I could change idea), my approach will be
> k
On Wed, Mar 5, 2008 at 2:18 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Nick Coghlan wrote:
> > While the patches are appreciated, please submit them to the tracker at
> > bugs.python.org rather than mailing them directly to this list.
>
> This comment doesn't apply to your recent posts - look
This inconsistency goes back to 2.3 at least and probably to the
initial unicode implementation.
>>> set(dir(u'')) - set(dir(''))
['isnumeric', 'isdecimal']
UserString contains these two methods even though 8-bit strings do
not. I'm not sure what we should do for 2.6 or 3.0. My preference
would
On Sun, Mar 16, 2008 at 12:07 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> >>> New sprint idea: getting all (inc. trunk) the buildbots green by
> >> Thursday. Anyone interested?
> >>
> >> I think the chance to achieve that is close to zero.
> >
> > Sounds like a challenge if ever I've h
On Sun, Mar 16, 2008 at 5:13 PM, Mark Dickinson <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 16, 2008 at 1:32 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> >
>
> > I think this is possible, though considerable work. Probably the
> > biggest win will be creat
On Mon, Mar 17, 2008 at 9:10 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> Barry, Neal, and myself had a conversation and changed the priority
> fields in the tracker. You can click on 'priority' to see an
> explanation, but the new fields are:
>
> - release blocker
> - critical
> - high
> -
101 - 200 of 523 matches
Mail list logo