I ran 2.6, 3.0, and 3.1 manually. 2.7 should get picked up on the
next run. The problem is that regrtest.py -R hangs from time to time
which caused the machine to run out of memory. Does anyone else have
regrtest.py -R hang for them? Some tests were disabled to try to
prevent the problem, but i
On Wed, Feb 11, 2009 at 6:24 AM, A.M. Kuchling wrote:
> On Tue, Feb 10, 2009 at 09:16:48PM -0800, Neal Norwitz wrote:
>> I ran 2.6, 3.0, and 3.1 manually. 2.7 should get picked up on the
>> next run. The problem is that regrtest.py -R hangs from time to time
>> which caus
On Tue, Feb 24, 2009 at 2:18 PM, Heracles
wrote:
>
> Hello,
>
> I am working on a patch to add to the _cursesmodule.c file of the Python
> core libraries. I figured I would take on one of the implemented functions
> to try to get my feet wet contributing to the project. At any rate, I have
> the
Has anyone run valgrind/purify and pychecker/pylint on the 3.1 code
recently? Both sets of tools should be used before the final release
so we can fix any obvious problems.
n
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailm
On Wed, Oct 21, 2009 at 6:56 PM, Mike Krell wrote:
> Is there any possibility of backporting support for the nonlocal keyword
> into a 2.x release? I see it's not in 2.6, but I don't know if that was an
> intentional design choice or due to a lack of demand / round tuits. I'm
> also not sure if
On Mon, Nov 2, 2009 at 2:18 AM, Mark Dickinson wrote:
> On Sat, Oct 31, 2009 at 9:47 PM, Brett Cannon wrote:
>> Just wanted to publicly thank everyone who has been causing all the
>> checkins to fix and stabilize the test suite (I think it's mostly
>> Antoine and Mark, but I could be missing some
On Fri, Nov 6, 2009 at 12:27 AM, Mark Dickinson wrote:
> On Fri, Nov 6, 2009 at 3:53 AM, R. David Murray wrote:
>
>> (2) issue 4970: consistent signal 32 error on the norwitz-x86 Gentoo
>> buildslave in 3.1 and 3.x. This may be due to the box
>> running an old threading library,
On Mon, Jan 25, 2010 at 2:34 PM, Victor Stinner
wrote:
>
> Interaction with the Python developers
> ==
>
> I open an issue for each bug found in CPython. I describe how to reproduce it
> and try to write a patch. I have learn to always write an unit test, useful
On Wed, Jan 27, 2010 at 11:58 AM, Ben Finney wrote:
> Chris Bergstresser writes:
>
>> On Wed, Jan 27, 2010 at 2:54 AM, Ben Finney
>> wrote:
>> > Neal Norwitz writes:
>> >> Who knows, someone might even write a book about Fusil someday
>> >
Do we care about this (after your checkin and with my fix to make
32-63 bit values ints rather than longs):
# 64 bit box
>>> minint = str(-sys.maxint - 1)
>>> minint
'-9223372036854775808'
>>> eval(minint)
-9223372036854775808
>>> eval('-(%s)' % minint[1:])
-9223372036854775808L
n
--
On 7/9/06, N
On 7/9/06, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 09, 2006 at 03:02:06PM -0700, Neal Norwitz wrote:
> > Do we care about this (after your checkin and with my fix to make
> > 32-63 bit values ints rather than longs):
> >
> > # 64 bit box
&g
On 7/9/06, Tim Peters <[EMAIL PROTECTED]> wrote:
> Just to make life harder ;-), I should note that code, docs and tests
> for sys._current_frames() are done, on the tim-current_frames branch.
> All tests pass, and there are no leaks in the new code. It's just a
> NEWS blurb away from being just a
http://python.org/sf/1513611
xml.sax.ParseException weirdness in python 2.5b1. The following code
doesn't work:
from xml.sax import make_parser, SAXParseException
parser = make_parser()
try:
parser.parse(StringIO('invalid'))
except SAXParseException:
print 'caught it!'
Any comments?
n
On 7/10/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Jeremy Hylton wrote:
>
> > To express this email in the positive form:
> > 1. Reserved words should be real words.
> > 2. The meaning of the word should be clear.
> > 3. "Put statements in positive form." (Strunk & White)
> > 4. The word shoul
On 7/12/06, Armin Rigo <[EMAIL PROTECTED]> wrote:
>
> Only two breakages is certainly nice, and I know that we all try quite
> hard to minimize that; that's probably still two breakages too much.
I agree, but some of this responsibility has to fall to users.
Sometimes these breakages are bugs, pur
On 7/12/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
> On 7/5/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > For example, we heard grumblings about the releases coming too often.
> > Once we went to an 18 month release schedule, there was minimal
>
On 7/13/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
>
> > If it's pure python, why don't people just copy everything under
> > site-packages after installing? They could/should run compileall
> > after that to recompile the .pyc files. With 2.5 on 64-bit machines,
> > C extension
On 7/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Fred> It feels like the release cycle from alpha1 to final has gotten
> Fred> increasingly rushed.
I think that's just because you are getting older and time goes by
faster the less time you've got left. :-) It seems to be going
On 7/13/06, Christopher Armstrong <[EMAIL PROTECTED]> wrote:
> On 7/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > On Thu, 13 Jul 2006 11:29:16 -0700, Aahz <[EMAIL PROTECTED]> wrote:
> >
> > >There's been some recent discussion in the PSF wondering where it would
> > >make sense to throw s
On 7/13/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Neal Norwitz wrote:
>
> > Given that several people here think we should lengthen the schedule
> > in some way, I suspect we will do something. I'm not really against
> > it, but I don't think it will
On 7/15/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Terry Reedy wrote:
> > That is the goal, but when I watched the buildbot results last spring, the
> > degree of stability (greenness) appeared to vary. Is it possible to tag
> > particular versions as a 'green' version, or the 'most recent
I have a server up and running. I still need to polish some stuff
off. I will mail more info when I get a chance.
n
--
On 7/21/06, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
> On Fri, 21 Jul 2006 10:04:38 -0700, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
> >Hi,
> >
> >Apart from the goals st
There are still a bunch of outstanding bugs. rc1 is about a week away
and it would be great to fix these. Many of these are also present in
2.4, but it would be nice to squash them in 2.5. Here's the list from
PEP 356:
http://python.org/sf/1526585 - SystemError concat long strings (2.4)
I've fixed most of the problems (or determined they weren't problems)
from all the warnings issued by Klocwork's static analysis tool. The
following are outstanding issues.
This first group looks like real problems to me:
# 74 Object/funcobject.c:143Suspicious deref of ptr before NULL check
If you want I can send you the build master cfg I setup on python.org
and some simple instructions for how to connect to it. I don't have
time to focus on this at the moment and probably won't until 2.5 is
out.
n
--
On 7/20/06, Grig Gheorghiu <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This message is
On 7/25/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz wrote:
> > # 74 Object/funcobject.c:143Suspicious deref of ptr before NULL check
>
> Not quite sure what it is complaining about, but
>
> else if (PyTuple_Check(closure)) {
On 7/25/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis wrote:
> > Neal Norwitz wrote:
> >> # 74 Object/funcobject.c:143Suspicious deref of ptr before NULL check
> >
> > Not quite sure what it is complaining about, but
> >
On 7/25/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> >
> > Yes, I definitely think dropping the X would make the warning go away.
> > Do we want to check for a NULL pointer and raise an exception? The
> > docs don't address the issue, so I think if we added a check, ie: if
> > (closure && P
On 7/25/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz wrote:
> > We never really did address this issue did? A while back we talked
> > about whether to assert vs check and do PyErr_BadInternalCall(). I
> > don't remember a clear
On 7/26/06, Tim Peters <[EMAIL PROTECTED]> wrote:
>
> Today I noticed this happened when the buildbot started to run tests,
> and I'm 100% sure it's due to this code in
> Tools/buildbot/kill_python.c (the buildbot log files showed that
> kill_python.c killed /some/ Python process, and the Python ru
What is the behaviour that was added which broke compliance? What is
the benefit of the behaviour?
>From your description of fixing the problem, it seems there's some
risk invovled as it's modiyfing import.c, plus adding new features.
What is your recommendation?
n
--
On 7/26/06, Phillip J. Eby
On 7/27/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
>
> Personally, I would prefer to see it properly fixed in 2.5 rather than
> having to rip it out. It's more work for me to create the proper fix than
> it is to just work around it in my code, but it seems a more righteous
> labor, if you know
On 7/27/06, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 27, 2006 at 05:40:57PM +0200, Georg Brandl wrote:
> > The UUID test suite, which wasn't run by regrtest.py until now, is
> > now failing on some buildbots (and my machine). This should be fixed
> > before releasing something.
>
> Lo
It checks for ifconfig, /sbin/ifconfig, and /usr/sbin/ifconfig (same
for arp). The problem is the os.pipe command doesn't hide these
issues. It doesn't cause the test to fail, but is still broken. The
test is presumably failing for the other reason I mentioned
(unixdll_getnode). Let me know if
On 7/28/06, Michael Hudson <[EMAIL PROTECTED]> wrote:
> Anthony Baxter <[EMAIL PROTECTED]> writes:
>
> > Does anyone disagree with making the next release beta3?
>
> It seems like a good idea to me. I guess this will mean the final
> release will be pushed back a bit?
Anthony and I talked about s
Ping,
I just checked in a change to disable testing 2 uuid functions
(_ifconfig_get_node and unixdll_getnode) that fail on many platforms.
Here's the message:
"""
Disable these tests until they are reliable across platforms. These
problems may mask more important, real problems.
One or both meth
I'm wondering if the following change should be made to Include/weakrefobject.h:
-PyAPI_FUNC(long) _PyWeakref_GetWeakrefCount(PyWeakReference *head);
+PyAPI_FUNC(Py_ssize_t) _PyWeakref_GetWeakrefCount(PyWeakReference *head);
And the 2 other files which use this (weakref obj and module). Should
t
This looks like it needs to be fixed as it's a regression. As Skip
said, bug fixes are allowed. There will still be at least one release
candidate. It's looking like c1 will be around Aug 18 and final
around Sept 12. I'll update the PEP when I get a chance and confirm
all the dates.
n
--
On 8
Things are getting better, but we still have some really important
outstanding issues. PLEASE CONTINUE TESTING AS MUCH AS POSSIBLE.
Also, it would be great to use as many tools as possible to find bugs
and improve quality. It would be especially nice to run Purify on
Windows.
I've updated PEP 35
There is at least one outstanding bug report for test_mmap failing on
AIX IIRC. Possibly another for test_resource. Please review bug
reports and file new ones/update old ones with the current status.
Unless if you provide patches, they probably won't be fixed though.
No one has access to AIX AFA
On 8/9/06, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> 2.4 performed these imports silently, while 2.5 complains "SystemError:
> Parent module 'x' not loaded", which is actually a useful message, and
> helped me fix it.
Can you make a small, self-contained test case? The SystemError
should be a n
I checked in this fix for the __index__ clipping issue that's been
discussed. This patch is an improvement, but still needs some work.
Please pull out any parts you have an issue with and suggest a patch
to address your concern.
n
-- Forwarded message --
From: neal.norwitz <[EMAI
I'm not sure if this is a race condition in the test, the test using
SocketServer inappropriately, or if the failure is exposing a problem
in SocketServer.
The issue is that when the second (UDP) server is setup, there is
still a child process from the first (TCP) server. So when the UDP
server c
I just updated the PEP to remove all references to issues blocking
release of 2.5.
I don't know of any. I haven't heard of any issues with the fixes
that have been checked in.
If you have issues, respond ASAP! The release candidate is planned to
be cut this Thursday/Friday. There are only a few
On 8/15/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
That penalty is already paid today. Much code dealing with
ints has a type test whether it's an int or a long. If
int and long become subtypes of each other or of some abstract
type, performance will decrease even more because a subtype
te
On 8/15/06, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
>
> It would be nice if someone could bytecompile Lib using
> Tools/compiler/compile.py and then run the test suite. I'd do it
> myself but can't spare the time at the moment (I started but ran
> into what seems to be a gcc bug along the way)
Thanks Dino.
The attached patch should fix the problem. Once RC1 is cut, I'll
check this in unless someone beats me to it. Since the compiler
changed, I can't backport this. If someone wants to make a similar
fix for 2.4 go for it.
n
--
On 8/16/06, Dino Viehland <[EMAIL PROTECTED]> wrote:
W
On 8/16/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
>
> It seems to me that you could drop the FAST_SUBCLASS bit, since none of the
> other bits will be set if it is not a subclass of a builtin. That would
> free up one flag bit -- perhaps usable for that BaseException flag Guido
> wants. :)
:
On 8/17/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> I'd like to fix the two build failures that the Windows buildbots
> show for the 2.5 trunk. I'm not quite sure what the OpenSSL failure
> is, yet, but the sqlite error should be fixable with the patch
> below. Ok to work on this?
Please do
This is a reminder (I don't think anyone else sent one, I sure hope not).
We are holding 4 days of sprints next week at Google offices in NY
city and Mt View, CA. These are open if you'd like to attend. It
would be very helpful to pre-register on the wiki as we can notify
security and generally
I did something similar to what Andrew suggested.
http://python.org/sf/1542451
Could everyone interested take a look and offer more test cases?
n
--
On 8/17/06, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 18, 2006 at 12:26:33AM +0200, Armin Rigo wrote:
> > Without more inspection, I'd
VC8 is not a supported compiler at this point. However, patches are
greatly accepted.
The _types module was added late and probably VC6 and VC8 project
files did not get updated. You can search for the necessary mods to
the VC7 proj file(s) on python-checkins.
n
--
On 8/18/06, christopher baus
I've been working on enhancing xrange and there are a bunch of issues
to consider. I've got pretty much complete implementations in both C
and Python. Currently xrange is 2 objects: range and the iter.
These only work on C longs. Here's what I propose:
2.6:
* Add deprecation warning if a floa
I don't want to make any more changes to 2.5 unless we absolutely have
to. I also don't want to lose fixes. How about for anything that
should be resolved in 2.5, but wait for 2.5.1 we set the tracker item
to: Group 2.5, Resolution: Later, Priority 7.
Then it should be easy to find these things
On 8/18/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
>
> I'd like to commit this. It fixes bug 1542051.
>
> Index: Objects/exceptions.c
...
Georg,
Did you still want to fix this? I don't remember anything happening
with it. I don't see where _PyObject_GC_TRACK is called, so I'm not
sure why _Py
Gustavo,
Did you still want this addressed? Anthony and I made some comments
on the bug/patch, but nothing has been updated.
n
--
On 8/15/06, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote:
> > If you have issues, respond ASAP! The release candidate is planned to
> > be cut this Thursday/Friday.
There are 3 bugs currently listed in PEP 356 as blocking:
http://python.org/sf/1551432 - __unicode__ breaks on exception classes
http://python.org/sf/1550938 - improper exception w/relative import
http://python.org/sf/1541697 - sgmllib regexp bug causes hang
Does anyone wan
On 9/5/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> > [MAL]
> > The proper fix would be to introduce a tp_unicode slot and let
> > this decide what to do, ie. call .__unicode__() methods on instances
> > and use the .__name__ on classes.
>
> That was my bug reaction and what I said on the bug r
Doc patches are fine, please fix.
n
--
On 9/7/06, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
> On 5-sep-2006, at 6:24, Neal Norwitz wrote:
>
> > There are 3 bugs currently listed in PEP 356 as blocking:
> > http://python.org/sf/1551432 - __unicode__ brea
PEP 356
http://www.python.org/dev/peps/pep-0356/
has 2.5c2 scheduled for Sept 12. I checked in a fix for the last
blocking 2.5 issue (revert sgml infinite loop bug). There are no
blocking issues that I know of (the PEP is up to date).
I expect Anthony will call for a freeze real soon now. I
Michael,
In Python/pystate.c, you made this checkin:
"""
r39044 | mwh | 2005-06-20 12:52:57 -0400 (Mon, 20 Jun 2005) | 8 lines
Fix bug: [ 1163563 ] Sub threads execute in restricted mode
basically by fixing bug 1010677 in a non-broken way.
"""
_PyGILState_NoteThreadState is declared as static
On everyones favorite platform (HP-UX), the following code consistently fails:
###
from thread import start_new_thread, allocate_lock
from time import sleep
def bootstrap():
from os import fork ; fork()
allocate_lock().acquire()
start_new_thread(bootstrap, ())
sleep(.1)
###
The error is
On 9/14/06, Aahz <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 14, 2006, Neal Norwitz wrote:
> >
> > On everyones favorite platform (HP-UX), the following code
> > consistently fails:
>
> Which exact HP-UX? I remember from my ancient days that each HP-UX
> version
I also tested the fix (see patch below) for the abs() issue and it
seemed to work for 4.1.1 on 64-bit. I'll apply the patch to head and
2.5 and a test after 2.5 is out.
I have no idea how to search for these problems. I know that xrange
can't display -sys.maxint-1 properly, but I think it works
On 9/17/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz schrieb:
> > I also tested the fix (see patch below) for the abs() issue and it
> > seemed to work for 4.1.1 on 64-bit. I'll apply the patch to head and
> > 2.5 and a test after 2.5 i
On 9/18/06, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Neal Norwitz]
> >> I'm getting a crash when running test_builtin and test_calendar (at
> >> least) with gcc 4.1.1 on amd64. It's happening in pymalloc, though I
> >> don't know what th
On 9/21/06, Armin Rigo <[EMAIL PROTECTED]> wrote:
> Hi Anthony,
>
> On Thu, Sep 21, 2006 at 09:12:03PM +1000, Anthony Baxter wrote:
> > Thanks to everyone for helping make 2.5 happen. It's been a long slog there,
> > but I think we can all be proud of the result.
>
> Thanks for the hassle! I've go
On 9/21/06, Jack Diederich <[EMAIL PROTECTED]> wrote:
>
> I should leave the tounge-in-cheek bombast to Tim and Frederik, especially
> when dealing with what might be an OS & machine specific bug. The next
> checkin and re-test will or won't highlight a failure and certainly someone
> with a g4 wi
On 9/21/06, Tim Peters <[EMAIL PROTECTED]> wrote:
>
> Well, to be strictly anal, while the result of
>
> (size_t)-123
>
> is defined, the result of casting /that/ back to a signed type of the
> same width is not defined. Maybe your compiler was "doing you a
> favor" ;-)
I also tried with a ca
On 9/22/06, Johnny Lee <[EMAIL PROTECTED]> wrote:
>
> Hello,
> My name is Johnny Lee. I have developed a *ahem* perl script which scans
> C/C++ source files for typos.
Hi Johnny.
Thanks for running your script, even if it is written in Perl and ran
on Windows. :-)
> The Python 2.5 typos can be c
On 10/3/06, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote:
> On Tuesday 03 October 2006 14:08, A.M. Kuchling wrote:
> > That doesn't explain it, though; the contents of whatsnew26.html
> > contain references to pep-308.html. It's not simply a matter of new
> > files being untarred on top of old.
On 10/2/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> This is why I asked for input from people on which would take less time.
> Almost all the answers I got was that the the C code was delicate but that
> it was workable. Several people said they wished for a Python
> implementation, but hardly
On 9/12/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>
> If you wonder how this all happened: Neal added sgml_input.html after
> c1, but didn't edit msi.py to make it included on Windows. I found out
> after running the test suite on the installed version, edited msi.py,
> and rebuilt the insta
On 10/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Georg> [ Bug http://python.org/sf/1541585 ]
>
> Georg> This seems to be handled like a security issue by linux
> Georg> distributors, it's also a news item on security related pages.
>
> Georg> Should a security advisory b
On 10/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I recently began running a Pybots buildslave for SQLAlchemy. I am still
> struggling to get that working correctly. Today, Python's test_codecs test
> began failing:
I checked in a fix for this that hasn't quite completed yet. (Only
fi
On 11/6/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Herman Geza schrieb:
> > Here python reads from an already-freed memory area, right?
>
> It looks like it, yes. Of course, it could be a flaw in valgrind, too.
> To find out, one would have to understand what the memory block is,
> and what
On 11/7/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz schrieb:
> > at 0x44FA06: Py_ADDRESS_IN_RANGE (obmalloc.c:1741)
> >
> > Note that the free is inside qsort. The memory freed under qsort
> > should definitely not be the base
You probably need to contact the authors for more info:
https://svn.sourceforge.net/svnroot/ziparchive/ziparchive/trunk/
http://wiki.python.org/moin/SummerOfCode
n
--
On 11/12/06, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> Hello,
>
> wasn't there a project about the zipfile module in the Summer o
What, if any, impact do you think the LSB should have wrt maintaining 2.4?
n
On 12/4/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> At the LSB meeting, there was a brief discussion of what Python
> version should be incorporated into LSB. This is more an issue
> if ABI compatibility for the C
On 12/4/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> At the LSB meeting, Jeff Licquia asked whether Python could provide
> binary compatibility with previous versions by use of ELF symbol
> versioning. In ELF symbol versioning, you can have multiple
> definitions for the same symbol; clients
On 12/5/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
>
> > So I think a public statement that we will support 2.4 with
> > security patches for a while longer (and perhaps with security
> > patches *only*) would be a good thing - independent of the LSB,
> > actually.
>
> Well, I don't know what so
Hi Lars.
Thanks for all your work on tarfile!
Please send your ssh2 key to pydotorg at python.org as an attachment.
One of us will add your key. Hopefully I can remember how to do it.
Here's some other info: http://www.python.org/dev/faq/#subversion-svn
I can't add you to SF to be assigned bug
I don't have a schedule in mind for 2.5.1 yet, however we should start
preparing for it. The release will probably happen sometime in
January if everyone is available. The branch has been pretty quiet,
so I'm not expecting too many problems.
Once we figure out a date for release I'll follow up h
On 1/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I came across a complaint that PEP 0042 had become a graveyard of
> neglected ideas, and decided to have a look through and implement
> something. Creating a smarter temporary file object seemed simple
> enough.
>
> Oddly, even after GvR re
problems with existing software as object.h
> > > > shouldn't be included directly, anyway.
> > >
> > > +1
> >
> > Maybe this should be done in a more systematic fashion? E.g. by giving
> > all "internal" header files a "py_" p
r to me if this should be fixed, but it's got a high priority::
http://python.org/sf/1467929 %-formatting and dicts
n
--
On 12/25/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> I don't have a schedule in mind for 2.5.1 yet, however we should start
> preparing for it.
On 1/3/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz schrieb:
> > Wow, I didn't realize I was that much of a broken record. :-)
> > I don't even remember talking to Thomas about it, only Guido. I
> > definitely would like to see
On 1/3/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz schrieb:
> > By private, I mean internal only to python and don't need to prefix
> > their identifiers with Py and are subject to change without backwards
> > compatibility. Includ
On 1/4/07, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 04, 2007 at 10:22:54AM -0800, Mike Klaas wrote:
> > > [ 1598181 ] subprocess.py: O(N**2) bottleneck
> > >
> > >I submitted the trivial fix almost two months ago, but apparently nobody
> > >feels responsible...
>
> Is Peter Astrand s
I fixed the crash that was due to raising a warning on shutdown. I
have heard about crashes at shutdown and wonder if this was the cause.
There might be similar bugs lurking that assume PyModule_GetDict()
always returns a valid pointer. It doesn't, it can return NULL.
I'm not sure if the origin
I've noticed a bunch of changes recently without corresponding items
added to Misc/NEWS. Can everyone update NEWS especially when fixing
bugs or adding new features?If you have made recent checkins, it
would be great if you could go back and update Misc/NEWS if you missed
it the first time.
T
SVN rev 52305 resolved Bug #1545497: when given an explicit base,
int() did ignore NULs embedded in the string to convert.
However, the same fix wasn't applied for long().
n
On 1/13/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> What's wrong with this session? :-)
>
> Python 2.6a0 (trunk:5341
http://python.org/sf/1637022 points out a problem caused by the lack
of a _Py prefix on Ellipsis. Most (all?) of the new AST names are not
prefixed. These are all meant to be internal names. Are there any
issues with changing this? If we do so, it means that any module
built with 2.5 that is us
On 1/17/07, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Why don't the Python 2.5 buildbots build anymore?
It looks like there were no checkins that caused a build. Changing
doc or Misc/NEWS is excluded. I'm guessing that there is a bug in
buildbot that causes it to miss any changes from svnmerge.
Short of using a memory debugger such as Valgrind or Purify, have you
considered looking for reference leaks? These may be the cause and
can be checked with pure python code. See how Lib/test/regrtest.py
handles the -R option.
n
--
On 1/24/07, Kristján V. Jónsson <[EMAIL PROTECTED]> wrote:
> Th
As you may have noticed we missed the schedule for getting 2.5.1 out.
Unfortunately several of us are having scheduling problems with making
this release. Since there don't seem to be major problems with the current
2.5 release, our current plan is to defer release until April when
everyone should
On 2/25/07, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
> It's about how we get Python 2.x to 3.0, and howmuch of 3.0 we put into 2.6
> and later.
I've also talked to a bunch of people at PyCon, including Thomas.
There seems to be much concern (rightfully so!) about the upgrade path
from 2.x to 3
On 2/25/07, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > The time schedules in PEP 361 (2.6 release schedule) and what Guido
> > has said for 3k (from what I remember) are roughly:
> >
> > April 2007 - 3.0 PEPs
On 2/25/07, Jeremy Hylton <[EMAIL PROTECTED]> wrote:
> On 1/3/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > In #1626545, Anton Tropashko requests that object.h should be
> > renamed, because it causes conflicts with other software.
> >
> > I would like to comply with this requests for 2.6, a
On 3/6/07, Phil Thompson <[EMAIL PROTECTED]> wrote:
> On Tuesday 06 March 2007 5:49 am, Martin v. Löwis wrote:
> > Phil Thompson schrieb:
> > > I'm not sure what your point is. My point is that, if you want to
> > > encourage people to become core developers, they have to have a method of
> > > gra
1 - 100 of 523 matches
Mail list logo
