Re: [Python-Dev] Python bug week-end : 20-21 November

Am 26.10.2010 19:53, schrieb Brett Cannon: > Can whomever has edit access to the Python Google Calendar add this? Done. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall

Re: [Python-Dev] r85838 - python/branches/py3k/.gitignore

Am 27.10.2010 09:25, schrieb anatoly techtonik: > On Tue, Oct 26, 2010 at 3:51 PM, Barry Warsaw wrote: >> On Oct 26, 2010, at 09:19 PM, Nick Coghlan wrote: >> >>>On Tue, Oct 26, 2010 at 5:31 PM, Georg Brandl wrote: >>>> This looks more like "Add g

Re: [Python-Dev] Continuing 2.x

Am 28.10.2010 06:13, schrieb Daniel Stutzbach: > 2010/10/27 Kristján Valur Jónsson > > > Firstly, the ease of integrating changes. It would be possible to port > those bugfixes that release-27 gets, and also backport selected things > from > py3k using

Re: [Python-Dev] MemoryError... how much memory?

Am 28.10.2010 15:14, schrieb "Martin v. Löwis": >> Furthermore, our server is fairly complex: we're using quite some >> libraries to do different jobs, and one of the approaches (not the >> only one) that we're taking to deal with this beast is to analyze its >> memory-related behaviour from an ext

Re: [Python-Dev] Continuing 2.x

Am 28.10.2010 18:07, schrieb l...@rmi.net: > Kristj?n Valur J?nsson writes: >> James Y Knight said: >> The python community has already decided many times over that Python2 is >> dead >> and Python3 is the future >> >> But the patient is very much alive and kicking, no matter what the good >>

Re: [Python-Dev] r85960 - python/branches/py3k/Lib/test/test_mailbox.py

Am 30.10.2010 12:12, schrieb Antoine Pitrou: > On Sat, 30 Oct 2010 02:13:01 +0200 (CEST) > brett.cannon wrote: >> Author: brett.cannon >> Date: Sat Oct 30 02:13:00 2010 >> New Revision: 85960 >> >> Log: >> Silence some ResourceWarning in test_mailbox by using file context managers. > > Unfortuna

Re: [Python-Dev] On breaking modules into packages Was: [issue10199] Move Demo/turtle under Lib/

Am 03.11.2010 03:35, schrieb Antoine Pitrou: > On Tue, 2 Nov 2010 19:57:48 -0700 > Brett Cannon wrote: >> > >> > How could we have split the module into a package in a way that matched the >> > API, whilst still retaining backwards compatibility with the old API? We >> > had >> > no choice but to

Re: [Python-Dev] Summary of Python tracker Issues

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

Re: [Python-Dev] Snakebite, buildbot and low hanging fruit -- feedback wanted! (Was Re: SSH access against buildbot boxes)

Am 07.11.2010 12:50, schrieb Nick Coghlan: > On Sun, Nov 7, 2010 at 9:24 PM, Trent Nelson wrote: >> 1. Set up standard build slaves on all the platforms, but put something in >> place that allowed committers to ssh/mstsc in to said slaves when things go >> wrong in order to aid with debugging and

Re: [Python-Dev] Snakebite, buildbot and low hanging fruit -- feedback wanted! (Was Re: SSH access against buildbot boxes)

Am 08.11.2010 01:13, schrieb "Martin v. Löwis": >> I've spent a good bit of time on that, and left all the instructions in >> the buildbot master config. I also adapted buildbot's hg hook to our >> situation (e.g. to send a change to multiple masters, as required for >> the community buildbots), s

Re: [Python-Dev] Backward incompatible API changes in the pydoc module

Am 08.11.2010 17:02, schrieb Éric Araujo: > Hi Nick, > > If there is no enormous difficulty in maintaining compatibility, I think > the usual deprecation process should be followed. We don’t know who is > using pydoc as a library, so let’s play safe and not risk breaking their > code (especially

Re: [Python-Dev] buildbot master update

Am 13.11.2010 14:00, schrieb Mark Dickinson: > On Fri, Nov 12, 2010 at 9:29 AM, "Martin v. Löwis" wrote: >> As you may have noticed: I updated the buildbot master to release 0.8.2. >> If you notice any problems, please post them here. > > One effect of this change seems to be that bbreport[1] no

Re: [Python-Dev] PEP 385: Formatting of Hg checkin notifications

Am 14.11.2010 13:39, schrieb Nick Coghlan: > On Sun, Nov 14, 2010 at 8:20 PM, "Martin v. Löwis" wrote: >> See >> >> http://hg.python.org/hooks/ >> >> You should have push permissions to that repository. > > I suspect my hg-fu is inadequate to at this point - I get an 'access > to repository "hg.p

Re: [Python-Dev] PEP 385: Formatting of Hg checkin notifications

Am 14.11.2010 19:35, schrieb Antoine Pitrou: > On Sun, 14 Nov 2010 19:27:22 +0100 > "Martin v. Löwis" wrote: >> > I suspect my hg-fu is inadequate to at this point - I get an 'access >> > to repository "hg.python.org/hooks" not permitted' error when I try to >> > push the modified file to "ssh://h

[Python-Dev] [RELEASED] Python 3.2 alpha 4

e found at: http://docs.python.org/3.2/ Please consider trying Python 3.2 with your code and reporting any bugs you may notice to: http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.2's contributors)

Re: [Python-Dev] Breaking undocumented API

Am 16.11.2010 18:06, schrieb Antoine Pitrou: > On Tue, 16 Nov 2010 16:34:54 - > exar...@twistedmatrix.com wrote: >> >> Imagine trying to use a dictionary without knowing about alphabetical >> ordering. > > You mean an ordered dictionary, right? That one's a sorted dictionary, though. Georg

Re: [Python-Dev] Python bug week-end : 20-21 November

Am 16.11.2010 21:15, schrieb Rodrigo Bernardo Pimentel: > On 26 October 2010 18:04, Georg Brandl wrote: >> Am 26.10.2010 19:53, schrieb Brett Cannon: >>> Can whomever has edit access to the Python Google Calendar add this? >> >> Done. > > The Bug Weekend is

Re: [Python-Dev] Mercurial Schedule

Am 16.11.2010 19:38, schrieb Jesus Cea: > Is there any updated mercurial schedule?. > > Any impact related with the new 3.2 schedule (three weeks offset)? I've been trying to contact Dirkjan and ask; generally, I don't see much connection to the 3.2 schedule (with the exception that the final mig

Re: [Python-Dev] Breaking undocumented API

Am 17.11.2010 22:16, schrieb Éric Araujo: >> Excluding a builtin name from __all__ sounds like a perfectly sensible >> idea, so even if it wasn't deliberate, I'd say it qualifies as >> fortuitous :) > > But then, a tool that looks into __all__ to find for example what > objects to document will mi

Re: [Python-Dev] Breaking undocumented API

Am 17.11.2010 22:39, schrieb Fred Drake: > On Wed, Nov 17, 2010 at 4:22 PM, Georg Brandl wrote: >> So it comes down again to what we'd like __all__ to mean foremost: >> public API, or just a list for "import *"? > > It is and has been since its inception

Re: [Python-Dev] Breaking undocumented API

Am 18.11.2010 11:47, schrieb Michael Foord: > On 17/11/2010 21:16, Éric Araujo wrote: >>> Excluding a builtin name from __all__ sounds like a perfectly sensible >>> idea, so even if it wasn't deliberate, I'd say it qualifies as >>> fortuitous :) >> But then, a tool that looks into __all__ to find f

Re: [Python-Dev] Mercurial Schedule

Am 18.11.2010 17:25, schrieb "Martin v. Löwis": > Am 17.11.2010 08:18, schrieb Georg Brandl: >> Am 16.11.2010 19:38, schrieb Jesus Cea: >>> Is there any updated mercurial schedule?. >>> >>> Any impact related with the new 3.2 schedule (three wee

Re: [Python-Dev] Mercurial Schedule

Am 18.11.2010 18:32, schrieb "Martin v. Löwis": >>> Alternatively, b1 should be postponed until after the Mercurial >>> migration is done. >> >> I think this "new feature" is not so shocking that it can be used as >> an argument to hold up the migration. If you have another reason to >> stop the m

Re: [Python-Dev] Mercurial Schedule

Am 19.11.2010 03:23, schrieb Benjamin Peterson: > 2010/11/18 Jesus Cea : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 18/11/10 18:32, "Martin v. Löwis" wrote: >>> In general, I'm *also* concerned about the lack of volunteers that >>> are interested in working on the infrastructure.

Re: [Python-Dev] Mercurial Schedule

Am 19.11.2010 08:58, schrieb "Martin v. Löwis": > Am 19.11.2010 03:23, schrieb Benjamin Peterson: >> 2010/11/18 Jesus Cea : >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> On 18/11/10 18:32, "Martin v. Löwis" wrote: In general, I'm *also* concerned about the lack of volunteers th

Re: [Python-Dev] Mercurial Schedule

Am 19.11.2010 16:00, schrieb Dirkjan Ochtman: > On Fri, Nov 19, 2010 at 15:56, Nick Coghlan wrote: >> That's enough to make folks like me somewhat nervous as to whether or >> not we're actually going to have a usable source control system come >> December 12. > > Yes, I've been negligent about up

Re: [Python-Dev] Mercurial Schedule

Am 19.11.2010 15:36, schrieb "Martin v. Löwis": >> - date Hg will be available for write access (it should be frozen for >> a while, to give the folks doing the conversion a chance to make sure >> buildbot is back up and run, commit emails are working properly, etc) > > I would target the build sl

Re: [Python-Dev] Mercurial Schedule

Am 19.11.2010 15:46, schrieb Barry Warsaw: > On Nov 19, 2010, at 11:50 PM, Nick Coghlan wrote: > >>- date SVN will go read only > > Please note that svn cannot be made completely read-only. We've already > decided that versions already in maintenance or security-only mode (2.5, 2.6, > 2.7, 3.1)

Re: [Python-Dev] Mercurial Schedule

Am 19.11.2010 22:35, schrieb "Martin v. Löwis": >> I don't understand all the worry about sys.subversion. > > Really? For a security release, there should be *zero* chance that it > breaks existing applications, unless the application relies on the > security bug that has been fixed. By "zero chan

Re: [Python-Dev] Mercurial Schedule

Am 21.11.2010 18:27, schrieb Jesus Cea: > What is the impact in the buildbot architecture?. Slaves must do > anything?. At least they need to have mercurial installed, I guess. > > What, as a buildslave manager, must I do to ready my server for the > migration?. Apart from having Mercurial instal

Re: [Python-Dev] [Python-checkins] r86702 - python/branches/py3k/Lib/idlelib/IOBinding.py

Am 23.11.2010 07:13, schrieb Terry Reedy: > > > On 11/23/2010 1:01 AM, terry.reedy wrote: >> Author: terry.reedy >> Date: Tue Nov 23 07:01:31 2010 >> New Revision: 86702 >> >> Log: > Issue 9222 Fix filetypes for open dialog > > Sorry, forgot to add this before clicking [go] or whatever the butto

Re: [Python-Dev] [Python-checkins] r86703 - python/branches/release31-maint/Lib/idlelib/IOBinding.py

Am 23.11.2010 07:49, schrieb Terry Reedy: > > > On 11/23/2010 1:16 AM, Senthil Kumaran wrote: >> Hi Terry, >> >> On Tue, Nov 23, 2010 at 2:07 PM, terry.reedy >> wrote: >>> Author: terry.reedy >>> Date: Tue Nov 23 07:07:04 2010 >>> New Revision: 86703 >>> >>> Log: >>> Issue 9222 Fix filetypes fo

Re: [Python-Dev] [Python-checkins] r86720 - python/branches/py3k/Misc/ACKS

Am 24.11.2010 20:25, schrieb Terry Reedy: > On 11/24/2010 2:04 PM, Brett Cannon wrote: >> On Tue, Nov 23, 2010 at 15:07, Terry Reedy wrote: > >>> I used Notepad to edit the file, TortoiseSvn to commit, the same as I did >>> for #9222, rev86702, Lib\idlelib\IOBinding.py, yesterday. >>> If the latt

[Python-Dev] [Preview] Comments and change proposals on documentation

Hi, at , you can look at a version of the 3.2 docs that has the upcoming commenting feature. JavaScript is mandatory. I've switched on anonymous comments for testing, but usually at least comments from anonymous users can be moderated. Be sure to test the "propose

Re: [Python-Dev] [Python-checkins] r86748 - in python/branches/py3k-urllib/Lib: http/client.py urllib/request.py

Am 25.11.2010 12:47, schrieb Éric Araujo: >> Author: senthil.kumaran >> New Revision: 86748 >> >> Log: >> Experimental - Transparent gzip Encoding in urllib2. There should be a good >> way to deal with Content-Length. > Cool feature! But... > >> Modified: >>python/branches/py3k-urllib/Lib/h

Re: [Python-Dev] [Preview] Comments and change proposals on documentation

Am 27.11.2010 23:11, schrieb Steven D'Aprano: > Nick Coghlan wrote: >> On Thu, Nov 25, 2010 at 6:24 AM, Georg Brandl wrote: >>> Hi, >>> >>> at <http://dpo.gbrandl.de/contents>, you can look at a version of the 3.2 >>> docs that has t

Re: [Python-Dev] PEP 384 final review

Am 29.11.2010 09:09, schrieb "Martin v. Löwis": >> I have now completed >> >> http://www.python.org/dev/peps/pep-0384/ >> >> >> was structseq.h considered? > > No, it wasn't - unfortunately, it still doesn't get included when > including Python.h. I'll add it. Would 3.2 be a good time

Re: [Python-Dev] [Preview] Comments and change proposals on documentation

Am 28.11.2010 00:58, schrieb Steven D'Aprano: > Georg Brandl wrote: >> Am 27.11.2010 23:11, schrieb Steven D'Aprano: > >>> I wasn't able to find a comment bubble that contained anything, so I >>> don't know what sort of information you expect

Re: [Python-Dev] Python and the Unicode Character Database

Am 01.12.2010 23:39, schrieb "Martin v. Löwis": >> As of today, "What’s New In Python 3.2" [1] does not even mention the >> unicodedata upgrade to 6.0.0. > > One reason was that I was instructed not to change "What's New" a few > years ago. Maybe all past, present and future whatsnew maintainers

Re: [Python-Dev] Python and the Unicode Character Database

Am 02.12.2010 20:40, schrieb "Martin v. Löwis": >> Maybe all past, present and future whatsnew maintainers can agree on these >> rules, which I copied directly from whatsnew/3.2.rst? > > I don't think all past maintainers can Yes, and the same goes for the future ones, since they may not even kno

Re: [Python-Dev] Porting Ideas

Am 02.12.2010 20:06, schrieb Barry Warsaw: > On Dec 02, 2010, at 12:59 PM, Terry Reedy wrote: > >>On 12/2/2010 8:36 AM, Lennart Regebro wrote: >>> On Wed, Dec 1, 2010 at 20:17, Antoine Pitrou wrote: And I'm not sure what this package called "Python" is (“a high-level object-oriented pro

Re: [Python-Dev] Minor: Unix icons for 2.5?

Anthony Baxter wrote: > There's an open PEP-356 issue for "update the icons to the newer > shinier ones" for Unix. As far as I can see, there's the 14x15 GIF > images used for Idle and the documentation. Note that for me at least, > idle comes up without an icon _anyway_. > > Are there any oth

Re: [Python-Dev] get for lists and tuples?

Russell E. Owen wrote: > I'd like to have the get method available for lists and tuples. (I > figured this must have been discussed before but can't recall it and > didn't turn anything up on google). > > It's obviously not a use-all-the-time method (or it'd already be there), > but I find myse

Re: [Python-Dev] Minor: Unix icons for 2.5?

e at least, > > idle comes up without an icon _anyway_. > > A pyfav.(gif|png) replacement would be quite welcome! > > On Tuesday 11 July 2006 13:25, Georg Brandl wrote: > > In case we add a Python .desktop file (as proposed in patch #1353344), > > we'll need

Re: [Python-Dev] get for lists and tuples?

Anthony Baxter wrote: > On Wednesday 12 July 2006 03:39, Georg Brandl wrote: >> > Anyway, I'm just testing the waters. If it's not heresy then I'd >> > like to do what I can to make it happen. >> >> IMO there's almost no chance this can go int

Re: [Python-Dev] Minor: Unix icons for 2.5?

Martin v. Löwis wrote: > Georg Brandl wrote: >> In case we add a Python .desktop file (as proposed in patch #1353344), >> we'll need some PNGs in /usr/share/icons. A patch for Makefile.pre.in >> is attached. > > Independent of whether this should be done at all,

Re: [Python-Dev] Long options support

Fredrik Lundh wrote: > Georg Brandl wrote: > >> I've just closed a bug report wishing for long option support, >> pointing to a patch sitting in the patch tracker implementing >> this. >> >> Should we accept at least the very common options "

Re: [Python-Dev] Pronouncement on SF #1520294 sought

Barry Warsaw wrote: > Just as 2.5b2 was being release, I updated SF patch #1520294: > > https://sourceforge.net/tracker/index.php? > func=detail&aid=1520294&group_id=5470&atid=305470 > > This fixes the pydoc, inspect, and types modules for built-in types > like getset and member descriptors. I'm

Re: [Python-Dev] Strategy for converting the decimal module to C

Raymond Hettinger wrote: > Aahz wrote: >> On Tue, Jul 18, 2006, Raymond Hettinger wrote: >> >>> P.S. The dictionary approach to context objects should likely be >>> abandoned for the C version. If the API has to change a bit, then so >>> be it. >>> >> >> Why do you say that? The rest I a

Re: [Python-Dev] Strategy for converting the decimal module to C

Raymond Hettinger wrote: > >>> I think it was tripping-up the folks working on the C implementation. >>> Georg can speak to it more directly. IIRC, the issue was that the >>> context object exposed a dictionary which a user could update directly >>> and there was no notification back to the surr

Re: [Python-Dev] Support for PyGetSetDefs in pydoc

Barry Warsaw wrote: > Why did I do this instead of trying to hunt down some existing getset > or member descriptor? For one thing, there really aren't very good > candidates for such objects in the built-in modules. You can't use > objects like datetime.timedelta.days in types.py because d

Re: [Python-Dev] FW: Bug? Certainly a new *behavior* from subprocess in 2.5 on Win32

Kevin Jacobs <[EMAIL PROTECTED]> wrote: > On 7/21/06, *Nick Coghlan* <[EMAIL PROTECTED] > > wrote: > > Delaney, Timothy (Tim) wrote: > > Looks like there's a bug in Popen.__del__ in 2.5. I'm not in a > position > > to have a look right now. > > For

Re: [Python-Dev] remaining issues from Klocwork static analysis

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 > > else if (PyTuple_Check(closure)) { > Py_XINCREF(closure); > } > > looks indeed suspic

Re: [Python-Dev] remaining issues from Klocwork static analysis

Neal Norwitz wrote: > 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)) { >>

Re: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix

Neal Norwitz wrote: > What is the behaviour that was added which broke compliance? What is > the benefit of the behaviour? sys.path_importer_cache is now used to cache if a real directory exists on the filesystem. Previously, a value of None for a given sys.path entry told find_module that no imp

Re: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix

Armin Rigo wrote: > Hi Phillip, > > On Wed, Jul 26, 2006 at 02:40:27PM -0400, Phillip J. Eby wrote: >> If we don't revert it, there are two ways to fix it. One is to just change >> PEP 302 so that the behavior is unbroken by definition. :) The other is >> to actually go ahead and fix it by ad

[Python-Dev] uuid test suite failing

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. Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/li

Re: [Python-Dev] uuid test suite failing

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. Okay, after fixing the test on my machine (locale issue) it looks like some ifconfigs do

Re: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix

Phillip J. Eby wrote: >>sys.path_importer_cache is quite an internal thing > > Whose behavior is documented in a PEP. Correct. >> and >>most code, even import hooks, shouldn't have to deal with it. > > That doesn't make it unimportant. It's a visible change in specified > behavior between P

Re: [Python-Dev] Release manager pronouncement needed: PEP 302 Fix

Bob Ippolito wrote: > Just because it's obscure doesn't mean we should go change how things > work in a way that's not consistent with the documentation. The > documentation should change to match the code or vice versa, though I > really don't have any strong feelings one way or the other.

[Python-Dev] Using Python docs

Regarding bug 469773, I think it would be great to have such a document "Using Python", containing the manual page and platform- specific hints on how to invoke the interpreter and scripts (e.g. explaining the shebang for Unices). I'd be willing to help write up such a document. Another thing th

Re: [Python-Dev] Py2.5 release schedule

Barry Warsaw wrote: > if isinstance(obj, ClassType) > > which fails in Python 2.5. I actually rewrote it like so: > > if isinstance(obj, ClassType) or isinstance(obj, type(type)) The second "type" seems to be superfluous. ;) Georg ___ Python-Dev ma

Re: [Python-Dev] segmentation fault in Python 2.5b3 (trunk:51066)

Martin v. Löwis wrote: > Ralf Schmitt schrieb: >> I've been trying to port our software to python 2.5. >> unfortunately I'm getting constantly hit by segfaults. > > I understand it's unfortunate for you, but it is fortunate > for us that you have been trying to port your application > before 2.5 w

Re: [Python-Dev] 2.5 status

Neal Norwitz wrote: > 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 >

Re: [Python-Dev] 2.5 status

Tim Peters wrote: > [Georg Brandl, on > http://python.org/sf/1523610 - PyArg_ParseTupleAndKeywords > potential core dump > ] >> This one's almost fixed if we can decide what to do with "levels". >> I wrote some time ago: >> >> ""

[Python-Dev] Is this a bug?

Is this considered a bug? Sure, deleting modules from sys.modules isn't quite common, but it happened to me on one occasion. Python 2.4.3 (#1, Jul 29 2006, 10:52:20) >>> import logging >>> import sys >>> del logging >>> del sys.modules['logging'] >>> ^D Error in atexit._run_exitfuncs: Traceba

Re: [Python-Dev] SyntaxError: can't assign to function call

Terry Reedy wrote: > "Neal Becker" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] >> class X (object): >>pass >> >> X() += 2 >> >>> SyntaxError: can't assign to function call >> >> Suppose I actually had defined __iadd__ for class X. Python says this >> syntax is invalid. I wi

Re: [Python-Dev] SyntaxError: can't assign to function call

Guido van Rossum wrote: >> This is similar to >> >> x = ([1], 2) >> x[0] += [2] >> >> which doesn't currently work either, though it could. > > No it couldn't. You can't assign to x[0]. L += R is defined as L = > L.__iadd__(R) so L must be a valid assignment target. > Thanks for making that cle

Re: [Python-Dev] Is this a bug?

Georg Brandl wrote: > Is this considered a bug? Sure, deleting modules from sys.modules > isn't quite common, but it happened to me on one occasion. > > Python 2.4.3 (#1, Jul 29 2006, 10:52:20) > >>> import logging > >>> import sys > >>> de

Re: [Python-Dev] Recent logging spew

Tim Peters wrote: > We're getting an awful lot of these turds at the ends of test runs now: > > Error in atexit._run_exitfuncs: > Not sure what caused it, but suspect this: > > """ > Author: georg.brandl > Date: Fri Aug 11 09:26:10 2006 > New Revision: 51206 > > Modified: > python/trunk/Lib/

Re: [Python-Dev] dict containment annoyance

tomer filiba wrote: > [Aahz] >> -1 >> >> This is seriously no different from an attempt to do >> >> >>> a = {} >> >>> a[ [] ] = 1 > > how so? i'm not trying to modify/store anything in a dict. > i'm only testing if a certain object is contained in the dict. > that's totally different. > imagine th

Re: [Python-Dev] Arlington VA sprint on Sept. 23

A.M. Kuchling wrote: > The CanDo group continues to have sprints in Arlington, so we may as > well continue to piggyback on their space. The next one will be > Saturday Sept. 23; sign up at > . > > If the PEP 356 plan holds, Python 2.5 will have been r

Re: [Python-Dev] Arlington VA sprint on Sept. 23

Martin v. Löwis wrote: > Fred L. Drake, Jr. wrote: >> I can guess at Martin's thinking, but I'd rather let him speak for himself, >> since I'm not a trained channeller. ;-) > > Essentially, I want to give patches more attention, since they are > larger contributions. I don't care if bug reports

Re: [Python-Dev] Making 'python -t' the default.

Thomas Wouters wrote: > > Can I suggest making 'python -t' the default, in 2.6? It makes python > warn about mixing tabs and spaces in indentation. +1. > In Py3k, '-tt' (the > error-raising version) will be the default, instead. Or disallow tabs altogether. > I see too many > newsbies with

Re: [Python-Dev] Type of range object members

Neal Norwitz wrote: > 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 decre

Re: [Python-Dev] 2.4 & 2.5 beta 3 crash

Josiah Carlson wrote: > Dino Viehland <[EMAIL PROTECTED]> wrote: >> >> We've been working on fixing some exception handling bugs in >> IronPython where we differ from CPython. Along the way we ran into >> this issue which causes CPython to crash when the code below is run. >> It crashes on both 2

Re: [Python-Dev] uuid tests failing on Windows

Martin v. Löwis wrote: > test_uuid1 and test_uuid4 fail consistently on Windows; apparently, > the generated universally-unique identifiers aren't even unique within > a set of 1000 identifiers. > > Can somebody please fix that? If not, should we remove the uuid module > as being immature? Patch

Re: [Python-Dev] TRUNK IS UNFROZEN, available for 2.6 work if you are so inclined

Fredrik Lundh wrote: > Georg Brandl wrote: > >>> The example code causes segfaults and probably always has (at last to 2.2) >> >> Interesting! From a naive POV, the docs' example is quite right. > > except that it doesn't work? I wanted to say:

Re: [Python-Dev] 2.4 & 2.5 beta 3 crash

Neal Norwitz wrote: > I did something similar to what Andrew suggested. > > http://python.org/sf/1542451 > > Could everyone interested take a look and offer more test cases? > Note that this needs to be fixed in the compiler package too. Georg ___ P

Re: [Python-Dev] One-line fix for urllib2 regression

John J Lee wrote: > Revision 50842 made a change to an undocumented interface of urllib2 that > I'm sure will break real code. > > Patch 1542948 reverts the part of that commit that applied to urllib2, and > adds a one-line fix in its place that addresses the problem that 50842 > fixed. > > De

Re: [Python-Dev] What should the focus for 2.6 be?

Talin wrote: > Guido van Rossum wrote: >> I've been thinking a bit about a focus for the 2.6 release. >> >> We are now officially starting parallel development of 2.6 and 3.0. I >> really don't expect that we'll be able to merge the easily into the >> 3.0 branch much longer, so effectively 3.0 wil

Re: [Python-Dev] PEP 362 open issues

Brett Cannon wrote: > I have been spending my Google sprint time on writing and implementing > PEP 362 (http://www.python.org/dev/peps/pep-0362/), which finally > defines Signature objects for functions. With the implementation at a > place I am happy with, I wanted to ask about the open issues

Re: [Python-Dev] Interest in a Python 2.3.6?

Barry Warsaw wrote: > I am considering producing a Python 2.3.6 release, which would of > course only be a bug fix maintenance release. The primary reason is > that not all OS distributions have upgraded to Python 2.4 and I think > it's worthwhile for us to bless a release that fixes known cr

Re: [Python-Dev] 2.5 status

Brett Cannon wrote: > > > On 9/4/06, *Neal Norwitz* <[EMAIL PROTECTED] > > wrote: > > There are 3 bugs currently listed in PEP 356 as blocking: > http://python.org/sf/1551432 - __unicode__ breaks on > exception classes > > > I replied on the bug re

Re: [Python-Dev] Fwd: Problem withthe API for str.rpartition()

Steve Holden wrote: >> * I acknowledge that Python *code* is almost certainly going to be edited in >> a >> left-to-right text editor, because it's an English-based programming >> language. >> But the strings that string methods like partition() and rpartition() are >> used >> with are quite

[Python-Dev] Exception message for invalid with statement usage

Current trunk: >>> with 1: ... print "1" ... Traceback (most recent call last): File "", line 1, in AttributeError: 'int' object has no attribute '__exit__' Isn't that a bit crude? For "for i in 1" there's a better error message, so why shouldn't the above give a TypeError: 'int' object is no

[Python-Dev] GCC 4.x incompatibility

Is it noted somewhere that building Python with GCC 4.x results in problems such as abs(-sys.maxint-1) being negative? I think this is something users may want to know. Perhaps the "Known Bugs" page at http://www.python.org/download/releases/2.5/bugs/ is the right place to put this info. Georg

Re: [Python-Dev] Python 2.5 bug? Changes in behavior of traceback module

Michael Glassford wrote: > In Python 2.4, traceback.print_exc() and traceback.format_exc() silently > do nothing if there is no active exception; in Python 2.5, they raise an > exception. Not too difficult to handle, but unexpected (and a pain if > you use it in a lot of places). I assume it was

Re: [Python-Dev] PEP 355 status

Shouldn't that paragraph be added to the PEP (e.g. under a "Status" subheading)? enjoying-top-posting-ly, Georg Guido van Rossum wrote: > I would recommend not using it. IMO it's an amalgam of unrelated > functionality (much like the Java equivalent BTW) and the existing os > and os.path modules

[Python-Dev] Security Advisory for unicode repr() bug?

[ Bug http://python.org/sf/1541585 ] This seems to be handled like a security issue by linux distributors, it's also a news item on security related pages. Should a security advisory be written and official patches be provided? Georg ___ Python-Dev ma

Re: [Python-Dev] Security Advisory for unicode repr() bug?

[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 be written and official patches b

Re: [Python-Dev] Can't check in on release25-maint branch

[EMAIL PROTECTED] wrote: > (I sent a note to pydotorg yesterday but got no response. Trying here.) > > I checked in a change to Doc/lib/libcsv.tex on the trunk yesterday, then > tried backporting it to the release25-maint branch but failed due to > permission problems. Thinking it might be lock

Re: [Python-Dev] what's really new in python 2.5 ?

Gerrit Holl wrote: > On 2006-10-03 20:10:14 +0200, A.M. Kuchling wrote: >> I've added a robots.txt to keep crawlers out of /dev/. > > Isn't there a lot of useful, search-engine worthy stuff in /dev? > I search for peps with google, and I suppose the 'explanation' section, > as well as the develope

Re: [Python-Dev] Security Advisory for unicode repr() bug?

Georg Brandl wrote: > [ Bug http://python.org/sf/1541585 ] > > This seems to be handled like a security issue by linux distributors, > it's also a news item on security related pages. > > Should a security advisory be written and official patches be > provided? May I

Re: [Python-Dev] 2.3.6 for the unicode buffer overrun

Barry Warsaw wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Oct 12, 2006, at 4:08 AM, Anthony Baxter wrote: > >> I've had a couple of queries about whether PSF-2006-001 merits a >> 2.3.6. >> Personally, I lean towards "no" - 2.4 was nearly two years ago now. >> But I'm >> ope

[Python-Dev] build bots, log output

Hi, I wonder if it's possible that the build bot notification mails that go to python-checkins include the last 10-15 lines from the log. This would make it much easier to decide whether a buildbot failure is an old, esoteric one (e.g. test_wait4 sem_post: Success make: *** [buildbottest] Killed

Re: [Python-Dev] build bots, log output

Martin v. Löwis wrote: > Georg Brandl schrieb: >> I wonder if it's possible that the build bot notification mails that go >> to python-checkins include the last 10-15 lines from the log. This would >> make it much easier to decide whether a buildbot failure is an old, >

Re: [Python-Dev] Path object design

Fredrik Lundh wrote: > Talin wrote: > >> I'm right in the middle of typing up a largish post to go on the >> Python-3000 mailing list about this issue. Maybe we should move it over >> there, since its likely that any path reform will have to be targeted at >> Py3K...? > > I'd say that any prop

Re: [Python-Dev] Path object design

[EMAIL PROTECTED] wrote: > On 03:14 am, [EMAIL PROTECTED] wrote: > > >One thing is sure -- we urgently need something better than os.path. > >It functions well but it makes hard-to-read and unpythonic code. > > I'm not so sure. The need is not any more "urgent" today than it was 5 > years ago

Re: [Python-Dev] Path object design

[EMAIL PROTECTED] wrote: > On 10:06 am, [EMAIL PROTECTED] wrote: > >What a successor to os.path needs is not security, it's a better (more > pythonic, > >if you like) interface to the old functionality. > > Why? > > I assert that it needs a better[1] interface because the current > interface

<    1   2   3   4   5   6   7   8   9   10   >