Re: [Python-Dev] The bytes type

On Fri, Jan 12, 2007 at 10:49:13AM -0800, Raymond Hettinger wrote: > I think we should draw a line in the sand and resolve not to garbage-up > Py2.6. > The whole Py3.0 project is about eliminating cruft and being free of the > bonds of backwards compatibility. Adding non-essential cruft to Py2.6

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On Mon, Jan 15, 2007 at 11:40:22PM +0100, "Martin v. L??wis" wrote: > > Do I just suffer from having an overactive imagination? Are all of > > these implementation strategies impossible for some reason, and there > > are no others? > > Yes, and yes. What about turning all references to obj.items

[Python-Dev] Testers wanted: mailbox.py bugfix

http://www.python.org/sf/1599254 is a bug in the mailbox.py module that affects single-file mailbox formats (mbox, Babyl, MMDF) and can cause data loss. A proposed fix, mailbox-unified-patch, is attached to the bug. If you use mailbox.py for modifying mailboxes in the above formats, can you pleas

Re: [Python-Dev] Testers wanted: mailbox.py bugfix

On Wed, Jan 17, 2007 at 03:36:58PM -0600, Charles Cazabon wrote: > I can't speak for MMDF or Babyl, but it's a well-known requirement that all > programs on a system must use the same type of locking when mbox files are > used; the administrator picks his favourite (fcntl, dotlocking, whatever) and

Re: [Python-Dev] Twisted Isn't Specific (was Re: Trial balloon: microthreads library in stdlib)

On Thu, Feb 15, 2007 at 09:19:30AM -0500, Jean-Paul Calderone wrote: > >That feels like 6 layers too many, given that > > _logrun(selectable, _drdw, selectable, method, dict) > > return context.call({ILogContext: newCtx}, func, *args, **kw) > > return self.currentContext().callWithContext(ctx, func

Re: [Python-Dev] Py2.6 ideas

On Thu, Feb 15, 2007 at 05:41:51PM -0600, [EMAIL PROTECTED] wrote: > Tim> Hmm - possibilities. "record" definitely has greater connotations > Tim> of heterogeneous elements than "tuple", which would put paid to the > Tim> constant arguments that "a tuple is really just an immutable list

[Python-Dev] Encouraging developers

>From : 4. The patch mafia. I like everyone on python-dev that I meet, but somehow it is annoyingly difficult to get a patch into Python. Like threading, and the stdlib, this is a mixed blessing: yo

Re: [Python-Dev] Encouraging developers

On Mon, Mar 05, 2007 at 12:58:13PM -0600, [EMAIL PROTECTED] wrote: > I'm not much of a version control wonk. How would these help? Can't the > folks who need such stuff do some sort of anonymous svn checkout? The external developers can commit changes, revert them, etc. to their local repository

Re: [Python-Dev] Encouraging developers

On Mon, Mar 05, 2007 at 11:30:06PM +, Neil Schemenauer wrote: > I guess Andrew was looking for specific instructions. ... I'm happy to let the ball sit in Thomas's court until the Bazaar developers come out with 0.15 and run their conversion on the SVN repository. There's no burning hurry ab

Re: [Python-Dev] Encouraging developers

On Mon, Mar 05, 2007 at 08:50:46PM -, [EMAIL PROTECTED] wrote: > is indicative of a failure of the community. A good deal of the > discussion here in recent months has either been highly speculative, or > only tangentially related to Python's development, which is ostensibly > its topic. W

Re: [Python-Dev] Encouraging developers

On Tue, Mar 06, 2007 at 09:06:22AM +, Phil Thompson wrote: > My point is simply that the effort required to review patches seems to be a > problem. Perhaps the reasons for that need to be looked at and the process > changed so that it is more effective. At the moment people just seem be > sa

Re: [Python-Dev] SVK (was: Encouraging developers)

On Tue, Mar 06, 2007 at 07:59:53AM +0100, Ronald Oussoren wrote: > development easier for them. They can already do this using SVK, > which is a distributed version control system as well but uses SVN > repositories to store its data. I'm happy to write up a wiki page describing how to use SV

Re: [Python-Dev] SVK

On Tue, Mar 06, 2007 at 09:53:35AM -0500, A.M. Kuchling wrote: > initial setup seems very slow: SVK is retrieving each of 54165 > revisions and it'll probably take over an hour to complete. It's even worse than that. Retrying with the trunk, SVK synced 500 revisions in about 10 m

Re: [Python-Dev] Encouraging developers

On Tue, Mar 06, 2007 at 01:03:39PM -0600, [EMAIL PROTECTED] wrote: > Could the Summer of Code be used as a vehicle to match up current developers > with potentially new ones? The svn sandbox (or a branch) could serve as a > place for developers to get their feet wet. Perhaps Raymond can comment on

Re: [Python-Dev] Bug Days

On Wed, Mar 07, 2007 at 04:32:27PM +0100, Georg Brandl wrote: > If it was the last bug day you speak about, this was a bit unfortunate > since it > was only me and Tim who were present for a longer time, and not busy with > some > server maintenance tasks. I guess I just picked the wrong day ;)

Re: [Python-Dev] Encouraging developers

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 question comes up every so often, and after much discussion I think python-dev always con

Re: [Python-Dev] deprecate commands.getstatus()

On Tue, Mar 13, 2007 at 04:55:07PM -0700, Guido van Rossum wrote: > What does that buy us? subprocess offers better error-trapping, I think, and additional features such as closing all file descriptors after forking. At work, I found this fixed a number of bugs in our daemons code because if you

[Python-Dev] What's New maintenance

On Thu, Mar 15, 2007 at 10:31:06PM +0100, "Martin v. L?wis" wrote: > I would do that, except that Andrew explicitly reserved the right to > change whatsnew.tex. I believe he does go over Misc/NEWS in doing so. It's actually OK to add things to whatsnew.tex, subject to the warning that: 1) I will

Re: [Python-Dev] r54457 - python/trunk/Doc/whatsnew/whatsnew26.tex

On Tue, Mar 20, 2007 at 06:08:24AM +0100, neal.norwitz wrote: > Author: neal.norwitz > Date: Tue Mar 20 06:08:23 2007 > New Revision: 54457 > > +% Should there be a new section here for 3k migration? > +% Or perhaps a more general section describing module changes/deprecation? > +% sets module depr

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

On Wed, Mar 21, 2007 at 01:51:37PM -0400, Raymond Hettinger wrote: > What are the current thoughts on when Py2.5.1 will go out? > Do we need a bug-day beforehand? A bug day would be a great idea! I have a mailbox bug that'd greatly benefit from discussion about how to fix the problem. --amk

Re: [Python-Dev] A Survey on Defect Management Practices in Free/Open Source Software

On Wed, Apr 04, 2007 at 04:07:18PM +1000, Anthony Baxter wrote: > This one was at least personally addressed > (well, to "Python Contributors"), which is a step ahead of most of > them. What gets me is that such surveys are invalid because the respondents aren't randomly selected -- they're the

Re: [Python-Dev] Checking PEP autobuild results

On Tue, Apr 10, 2007 at 07:58:02PM +1000, Nick Coghlan wrote: > Have I forgotten a step in the process somewhere, or is something broken? Something's broken; I'm looking into it. --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python

Re: [Python-Dev] Checking PEP autobuild results

On Tue, Apr 10, 2007 at 07:30:13AM -0400, A.M. Kuchling wrote: > Something's broken; I'm looking into it. David Goodger found the problem and repaired it. It was nothing to do with the PEPs; another directory was causing the build process to stop with an

Re: [Python-Dev] RELEASED Python 2.5.1, release candidate 1

On Wed, Apr 11, 2007 at 03:03:47PM -0400, Gustavo Tabares wrote: > The title for the highlights page also says Python 2.4 I've fixed the broken download links that Thomas reported. I can't find the above error, though the bugs and license pages did have a 'Python 2.4.4' heading. --amk

Re: [Python-Dev] RELEASED Python 2.5.1, release candidate 1

On Thu, Apr 12, 2007 at 12:12:48PM -0400, Terry Reedy wrote: > | Open http://www.python.org/2.5/highlights.html > | > | The title of the page says "Highlights: Python 2.4" Ah, so it's a 2.5 page, not a 2.5.1 page; that's why my grep didn't find it. Fixed now; thanks! --amk

[Python-Dev] Fwd: AMD64 version of Python

>From Walter Beck <[EMAIL PROTECTED]> to webmaster: >I tried to install the AMD64 version of python on my new laptop, Vista >system. The installer said the processor was not correct. My processor >is a Turion64x2. 32 bit Python installed and ran fine. Is there a bug >in the installer o

Re: [Python-Dev] PEP 30XZ: Simplified Parsing

On Wed, May 02, 2007 at 04:42:09PM +0100, Michael Foord wrote: > Implicit string concatenation is massively useful for creating long > strings in a readable way though: This PEP doesn't seem very well-argued: "It's a common mistake to leave off a comma, and then scons complains that it can't find

Re: [Python-Dev] The docs, reloaded

On Mon, May 21, 2007 at 09:23:47AM -0400, Fred L. Drake, Jr. wrote: > I'll be happy to pull the existing tools out into a separate distribution if > we move to something else for Python. There are too many users of the > existing tools to abandon. That seems like a straightforward task. The

[Python-Dev] Outcome of Georg's documentation work?

What was the outcome of the discussion of Georg Brandl's reworked documentation ("The docs, reloaded")? Was any decision made on whether to go with reST, or on what changes need to made before that's possible? Did Fred Drake say what he thought? Georg, do you want access to python.org to host a

Re: [Python-Dev] Outcome of Georg's documentation work?

On Sat, Jun 16, 2007 at 11:31:56AM +0200, Georg Brandl wrote: > That would be really nice. Should I subscribe to the pydotorg list? Yes, please, and e-mail me an SSH key. Such work should be done on ximinez for security reasons, I think, even though the machine is fairly heavily loaded. --amk _

[Python-Dev] Wanted: readers for a mailbox.py article

I'm writing an article about the mailbox module for an online publication, and would like to get comments on the current draft from people familiar with the module. If you'd like to take a look, please e-mail me and I'll tell you the draft's URL. --amk

Re: [Python-Dev] Proposal for a new function "open_noinherit" to avoid problems with subprocesses and security risks

On Sat, Jun 23, 2007 at 08:39:38AM -0700, Stephen Hansen wrote: > I just wanted to express to the group at large that these experiences aren't > just Henning's; we spent a *tremendous* amount of time and effort debugging > serious problems that arose from file handles getting shared to subprocesses

Re: [Python-Dev] add bool type to optparse

On Mon, Jul 30, 2007 at 09:50:38AM -0400, Neal Becker wrote: > Subject says it all. Why is boolean support needed, given that optparse has store_true and store_false actions? Example usage: parser.add_option('--confirm', action='store_true', dest='confirm') --amk __

Re: [Python-Dev] Bug Day in January?

On Fri, Dec 07, 2007 at 10:04:38PM +0100, Georg Brandl wrote: > there wasn't much response to the bug day proposal, but I still think it's > a good idea. I'd propose a date in January, when Christmas etc. is over. > It would also be nice if someone did the organizing who hasn't got a > daily batch

Re: [Python-Dev] Contributing to Python

On Thu, Jan 03, 2008 at 02:49:27PM -0500, Fred Drake wrote: > Python 2.6 seems to be entirely targeted at people who really want to > be on Python 3, but have code that will need to be ported. I > certainly don't view it as interesting in its own right. The bulk of the *language* changes in 2

[Python-Dev] Bug day proposal: January 19th

A while ago Georg suggested holding a bug day some time soon. I suggest Saturday January 19th. It's a weekend day; it gives us two weeks to prepare by drawing up bug lists; there's a PyPy sprint January 12-19 (http://codespeak.net/pypy/dist/pypy/doc/news.html), so it may be helpful to have the Py

[Python-Dev] Bug day tasks

I've updated the bug day pages in the wiki: http://wiki.python.org/moin/PythonBugDay http://wiki.python.org/moin/PythonBugDayStatus How do we want to flag good candidate bugs? Should we add a keyword to Roundup, or just list them on the PythonBugDayStatus wiki page? Another task

Re: [Python-Dev] Bug day tasks

On Fri, Jan 04, 2008 at 04:53:46PM +0100, Christian Heimes wrote: > It'd be nice if we can also get a bot into #python-dev to broadcast svn > commits and bug tracker changes. The Twisted guys have good bot with > decent msg coloring but IIRC it's tight into TRAC. For svn we could > probably use CIA

[Python-Dev] Repeatability of looping over dicts

This post describes work aimed at getting Django to run on Jython: http://zyasoft.com/pythoneering/2008/01/django-on-jython-minding-gap.html One outstanding issue is whether to use Java's ConcurrentHashMap type to underly Jython's dict type. See

Re: [Python-Dev] Repeatability of looping over dicts

On Sat, Jan 05, 2008 at 07:05:55AM +1100, Tim Delaney wrote: > >So, do Python implementations need to guarantee that list(dict_var) == > >a later result from list(dict_var)? > > As I just posted to the blog, yes. Look at section 3.8 of the reference > manual > (Mapping Types), specifically footno

Re: [Python-Dev] Repeatability of looping over dicts

On Fri, Jan 04, 2008 at 02:54:49PM -0800, Guido van Rossum wrote: > What code would break if we loosened this restriction? I guess > defining d.items() as zip(d.keys(), d.values()) would no longer fly, > but does anyone actually depend on this? Just like we changed how we http://www.google.com/cod

Re: [Python-Dev] Contributing to Python

On Fri, Jan 04, 2008 at 11:45:34PM -0800, Mike Klaas wrote: > Question: should patches include edits to whatsnew.rst, or is the > committer responsible for adding a note? It's OK to submit or commit patches that don't update whatsnew.rst; I'll notice the checkin and decide whether to include the

Re: [Python-Dev] Coverity Scan, Python upgraded to rung 2

On Wed, Jan 09, 2008 at 09:11:21PM -0800, Neal Norwitz wrote: > For mmapmodule.c, fd should be checked for -1 before calling stat on line > 1064. I'll fix the mmap problem. --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/

Re: [Python-Dev] Coverity Scan, Python upgraded to rung 2

On Wed, Jan 09, 2008 at 09:11:21PM -0800, Neal Norwitz wrote: > For mmapmodule.c, fd should be checked for -1 before calling stat on line > 1064. On looking at this, it doesn't seem like an actual problem. fstat(-1, ...) returns a -1 and errno is set to EBADF, 'bad file descriptor'. /*

Re: [Python-Dev] Bug day preparations: tagging bugs?

On Fri, Jan 11, 2008 at 09:45:14PM +0100, Christian Heimes wrote: > Please add two keywords, one for bug day and one for easy tasks. May > "beginner task", "easy" or "novice level" makes a good keyword. I think marking easy tasks is all we need. That would certainly be useful during ongoing non-b

[Python-Dev] Bug day preparations: tagging bugs?

No one pushed back on the 19th as a bug day, so I'm going to go ahead and send out announcements this evening. We should mark issues in the tracker that are good candidates for new developers. How do we want to do this? We could add a new keyword ('beginner', 'bugday', ???) or add a prefix to

Re: [Python-Dev] Bug day preparations: tagging bugs?

On Fri, Jan 11, 2008 at 03:58:35PM -0800, Guido van Rossum wrote: > Let me know if more is needed, Andrew. Thanks! I've run searches for a few different components and marked a few bugs with the 'easy' keyword; I see that Tiran is doing this, too. > (I have no idea if anyone can add keywords or

Re: [Python-Dev] docs.python.org

On Mon, Jan 14, 2008 at 10:20:05AM +0100, Jeroen Ruigrok van der Werven wrote: > Will docs.python.org be redirected to www.python.org/doc? > > I think I am not the only person on the planet that had been using > docs.python.org for a long time now to get to the documentation. (And some > links are

[Python-Dev] Bug Day outcome

Today's bug day was a great success. Experienced people like Georg, Facundo, and Gregory P. Smith participated, and we also had people who submitted their first patches, some of which got applied today, too. Hopefully we'll see those people again. As of this writing, 37 issues were closed today

Re: [Python-Dev] Bug Day outcome

On Sun, Jan 20, 2008 at 11:23:38AM +0100, Quentin Gallet-Gilles wrote: > Excellent ! When will be the next one ? :-) We could certainly try to hold one in February. Maybe on the 16th? For March the best date is probably the Monday of the sprints at PyCon, because there will be a Python core sprin

Re: [Python-Dev] Bug Day outcome

On Sun, Jan 20, 2008 at 10:13:44PM +0100, Georg Brandl wrote: > Since this bug day was a relative success, I suggest to introduce a > more-or-less regular schedule. > > Feb 23 would make a nice second bug day in 2008, wouldn't it? That works for me. I've updated the wiki page to give Feb. 23 as

Re: [Python-Dev] Upcoming 2.4.5 and 2.3.7 releases

On Sun, Jan 27, 2008 at 08:27:27PM +0100, "Martin v. Löwis" wrote: > For 2.3, there are only few revisions that would be rolled back: > r52798, r52803, r52824, r54342. These changes can be reverted if you like; they were added for Jython's sake, but it looks like they've now decided to skip direct

Re: [Python-Dev] Buildbot failures

On Wed, Feb 06, 2008 at 08:34:21PM -0500, Raymond Hettinger wrote: > Also, test_docxmlrpc hasn't been happy. One of the tests isn't > getting the exact response string it expected. Any ideas what is > causing this? My fault; it should be fixed now. > There is also a recurring failure in SocketSe

[Python-Dev] Python Bug Day on Feb. 23

After the success of January's bug day, which closed 37 issues, let's have another one this month! Here's the brief announcement: Python Bug Day: Saturday, February 23 2008. Meet in the #python-dev IRC channel on irc.freenode.net and help improve Python. For more information, see http://wiki.py

Re: [Python-Dev] Mutable sequence .sort() signature

On Tue, Feb 12, 2008 at 08:19:27PM -0800, Guido van Rossum wrote: > [on the 'What's New in 3.0' document] > I think that's a good start. Andrew Kuchling can always move it later > if that section becomes too crowded or uneven. I won't be able to work on the 3.0 document in time for 3.0 final (assu

Re: [Python-Dev] Py3k and asyncore/asynchat

On Thu, Feb 14, 2008 at 06:24:04PM -0800, Josiah Carlson wrote: > 1.a. Figure out what the hell is up with OOB data, how to handle it, > and stop making it use handle_expt(). Does OOB data actually need to be supported? For a long time TCP implementations usually had buggy OOB implementations bec

[Python-Dev] Reminder: bug day on Saturday

We have a bug day this Saturday. Join us on IRC and let's see how many issues we can clear up. http://wiki.python.org/moin/PythonBugDay for more. There are currently 69 bugs marked as 'easy', which is probably more than enough, but if you see anything that's suitable for a new developer, please

Re: [Python-Dev] Reminder: bug day on Saturday

On Wed, Feb 20, 2008 at 12:37:42PM -0800, Brett Cannon wrote: > How about marking already submitted patches as easy to get help > reviewing? For instance, there are a bunch of test rewrites to move > old tests to unittest where it would be rather nice to have another > pair of eyes make sure that t

Re: [Python-Dev] Small RFEs and the Bug Tracker

On Thu, Feb 21, 2008 at 08:59:51AM +0100, Virgil Dupras wrote: > Thanks for running it. The rate is better than I expected, so I was > wrong in my assumption. > > What would be the difference between accepted and fixed for a closed ticket? 'accepted' is probably used more for patches, while 'fixe

Re: [Python-Dev] Small RFEs and the Bug Tracker

On Fri, Feb 22, 2008 at 01:06:05PM -0800, Brett Cannon wrote: > I think Martin is right that someone needs to take the lead and do a > complete review of how issues are handled. That way we can do a change > in one big batch to something that works better for Python. Are we, as a development commu

Re: [Python-Dev] Small RFEs and the Bug Tracker

On Sat, Feb 23, 2008 at 01:55:06AM +0100, Christian Heimes wrote: > We have over 1,700 open issues - bug reports, feature requests and > patches - in our bug tracker. In my humble opinion it's a sure sign for > a problem. Sure, but is that because the bug life cycle is sub-optimal, or because we d

[Python-Dev] February bug day outcome

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 number of contributions from new people. Should we have one next month? The PyCon

Re: [Python-Dev] February bug day outcome

On Sun, Feb 24, 2008 at 07:06:42PM -0800, Neal Norwitz wrote: > I'd rather push it out to mid-month assuming Barry starts releasing > alphas at the end of each month. That should provide some time to > stabalize. Any one see the buildbots recently? :-( > http://www.python.org/dev/buildbot/all/ I

Re: [Python-Dev] Buildbots for trunk are all red

On Tue, Feb 26, 2008 at 09:46:04PM -0800, Gregory P. Smith wrote: > My opinion on bsddb as a standard library module is based mostly on "its > always been there" and a vague memory of the last time this came up I > thought people piped up saying they liked batteries being included, > including bsdd

Re: [Python-Dev] Documentation for ability to execute zipfiles & directories

On Tue, Mar 04, 2008 at 08:58:57AM -0500, Steve Holden wrote: > While I hesitate to suggest a change of such magnitude, there's > something to recommend the old IBM mainframe approach of separating out > "Principles of Operation" (which would be the reference manuals, in > Python's case the Lang

Re: [Python-Dev] How we can get rid of eggs for 2.6 and beyond

On Fri, Mar 21, 2008 at 06:41:00PM -0400, Phillip J. Eby wrote: > I'm making the assumption that the author(s) of PEP 262 had good > reason for including what they did, rather than assuming that we > should start the entire process over from scratch. The goal *was* originally to provide for RPM-

Re: [Python-Dev] How we can get rid of eggs for 2.6 and beyond

On Sat, Mar 22, 2008 at 09:13:24PM +0100, "Martin v. L?wis" wrote: > Unfortunately no. I was looking for it, but couldn't find it. He > mentioned a website with a "call for action", but I couldn't find > that, either :-( We're working on the video, but I think it'll be a few weeks before things st

Re: [Python-Dev] Py3k and asyncore/asynchat

On Mon, Mar 24, 2008 at 10:04:20PM +0100, Thomas Wouters wrote: > I remember only a couple of dissenting voices, and only a small number of > participants. Of the dissenting voices, I do not recall any actual arguments Weren't some of those dissenting voices the Twisted developers, though? --amk

Re: [Python-Dev] Py3k and asyncore/asynchat

On Mon, Mar 24, 2008 at 03:51:56PM -0700, Josiah Carlson wrote: > reasonable question; 2.6 alpha 1 has been released. It's a question > as to whether someone with commit access can or will commit the patch > as posted, run the tests to verify that they aren't broken, and > perhaps actually look at

Re: [Python-Dev] very bad network performance

On Mon, Apr 14, 2008 at 11:10:12AM -0700, Curt Hagenlocher wrote: > while True: > left = size - buf_len > ! recv_size = max(self._rbufsize, left) > data = self._sock.recv(recv_size) What version is this patch against? (The last 2.5

Re: [Python-Dev] Global Python Sprint Weekends: May 10th-11th and June 21st-22nd.

On Wed, Apr 16, 2008 at 10:51:53AM -0700, Trent Nelson wrote: > Following on from the success of previous sprint/bugfix weekends and > sprinting efforts at PyCon 2008, I'd like to propose the next two > Global Python Sprint Weekends take place on the following dates: A great idea; than

Re: [Python-Dev] sock.close() not closing?

On Wed, May 07, 2008 at 10:29:02AM -0700, Bill Janssen wrote: > This particular nasty pattern is deeply entwined in all the code that > touches the HTTP library in any way, so it will be a big job to get > rid of it -- basically re-writing HTTP support and all the services > which use it. I didn't

Re: [Python-Dev] sock.close() not closing?

On Wed, May 07, 2008 at 03:29:33PM -0300, Facundo Batista wrote: > > This would be a good chance for Py3K to dump httplib/urllib/urllib2 > > and use some more modern library. > > Which modern library do you propose? I have no idea -- presumably we'd need to compare a bunch of them (curl, libwget

Re: [Python-Dev] [Python-checkins] [Python-3000] r62848 - python/trunk/Objects/setobject.c

On Thu, May 08, 2008 at 11:23:11PM +1000, Nick Coghlan wrote: > It's actually the time zone issues that get me in relation to code > freezes... so I just try to avoid committing anything for a day or two :) Subscribers to the python-dev digests may also not see a posting immediately, waiting unti

Re: [Python-Dev] Adding start to enumerate()

On Mon, May 12, 2008 at 12:21:00PM +1200, Greg Ewing wrote: > Parsing a file and wanting to be able to print > error messages with line numbers would seem to > be a fairly likely use. Couldn't people be using the fileinput module for this, though? --amk ___

[Python-Dev] Distutils & configparser rename

Python 2.6 renames the ConfigParser module to be configparser. Distutils imports ConfigParser in various places. I just made a commit updating the import in one places, and then noticed that part of commit r63248, which made the same change, was reverted in order to preserve backward-compatibilit

Re: [Python-Dev] Addition of "pyprocessing" module to standard lib.

On Fri, May 16, 2008 at 10:32:30AM +0200, Ulrich Berning wrote: > As long as the ctypes extension doesn't build on major Un*x platforms > (AIX, HP-UX), I don't like to see ctypes dependend modules included into > the stdlib. Please keep the stdlib as portable as possible. > More and more people t

Re: [Python-Dev] Addition of "pyprocessing" module to standard lib.

On Mon, May 19, 2008 at 08:50:39PM +0200, Thomas Heller wrote: > Myself I would rather spend my energy to make ctypes more portable, within my > skills and the platforms I have access to. Someone could run Solaris x86 inside a hosted virtual machine and make it available to the Python developers.

Re: [Python-Dev] Addition of "pyprocessing" module to standard lib.

On Mon, May 19, 2008 at 06:13:11PM -0700, Bill Janssen wrote: > And these are all SYSV derivatives, aren't they? So perhaps it's some > common fix for all three? This reminds of a Tim-ism: == > Just for the record, on AIX, the following C program: Oh no you don't! I followed AIX

Re: [Python-Dev] [Python-checkins] r64407 - python/trunk/Doc/library/multiprocessing.rst

On Thu, Jun 19, 2008 at 03:04:11PM -0500, Benjamin Peterson wrote: > I don't think the whole introduction had to go. I think it helped give > some idea of how multiprocessing works before jumping straight to the > API reference. I don't think overview material like that should be buried inside the

[Python-Dev] sum() in math module not duplicated?

In the comments before the implementation of sum() in mathmodule.c, note 4 says: Note 4: A similar implementation is in Modules/cmathmodule.c. Be sure to update both when making changes. I can't find a sum implementation or similar code in cmathmodule.c. Did someone intend to port the sum f

Re: [Python-Dev] [Python-checkins] r64407 - python/trunk/Doc/library/multiprocessing.rst

On Thu, Jun 19, 2008 at 05:16:38PM -0400, Jesse Noller wrote: > Where would that chapter end up (source-wise) I think a few of us > might have additional things to add ;) This would be Doc/library/ipc.rst. The chapter is 'Interprocess Communication and Networking'. Is anyone else finding it incr

Re: [Python-Dev] r64407 - python/trunk/Doc/library/multiprocessing.rst

On Fri, Jun 20, 2008 at 08:55:13AM -0700, Bill Janssen wrote: > > Is anyone else finding it increasingly odd that subprocess, signal, > > socket/ssl, and syncore are in the same chapter? I'm tempted to move > > socket, ssl, asyncore+asynchat into a 'networking' chapter, and then > > also move Sock

Re: [Python-Dev] [Python-3000] No beta2 tonight

yOn Fri, Jul 18, 2008 at 10:45:06AM -0700, Josiah Carlson wrote: >> It's entirely possible that I know very little about what was being > made available via the bsddb module, but to match the API of what is > included in the documentation (plus the dictionary interface that it > supports) shouldn't

Re: [Python-Dev] git repositories for trunk and py3k

On Fri, Jul 18, 2008 at 11:12:41AM -0700, Brett Cannon wrote: > And those two periods are significant for people who think they are > line noise. Damn is Git quirky. Oh my, yes. We use git at work; there's a reason I now use Bazaar for personal projects. > I assume the ^ operator means "just bef

Re: [Python-Dev] Fuzzing bugs: most bugs are closed

On Sun, Jul 20, 2008 at 10:45:39PM +0200, Victor Stinner wrote: > Hum... how can I say it? It's trivial to crash _sre :-) So I blacklisted > _sre.compile() in my fuzzer. We should certainly try to fix those issues, then; people usually assume the re module is safe for use inside a sandbox and pro

Re: [Python-Dev] Fuzzing bugs: most bugs are closed

yOn Mon, Jul 21, 2008 at 03:53:18PM +, Antoine Pitrou wrote: > The underscore at the beginning of _sre clearly indicates that the module is > not recommended for direct consumption, IMO. Even the functions that don't > themselves start with an underscore... Sure, but if someone is trying to

Re: [Python-Dev] Looking for the email addresses of some committers

On Thu, Jul 31, 2008 at 07:20:15PM -0700, Brett Cannon wrote: > * Jackilyn Hoxworth She was a Google SoC person in 2006; since she hasn't done anything subsequently, her commit privs can be revoked. --amk ___ Python-Dev mailing list Python-Dev@python.or

Re: [Python-Dev] Unicode 5.1.0

On Fri, Aug 22, 2008 at 07:59:46AM -0700, Guido van Rossum wrote: > That's up to us. I don't know what the reason was for keeping the > 3.2.0 database around -- does anyone here recall ever using it? For > what? RFC 3491, one of the internationalized domain name RFCs, explicitly requires Unicode 3

Re: [Python-Dev] bsddb alternative (was Re: [issue3769] Deprecate bsddb for removal in 3.0)

On Thu, Sep 04, 2008 at 09:25:43AM -0700, Bill Janssen wrote: > Yeah, but bsddb is one of those exploding batteries. I've used it for > years, and have had lots and lots of problems with it. Having SQLite > in there is great; now we need implementations of anydbm and shelve > which use it. What

Re: [Python-Dev] Not releasing rc1 tonight

On Sun, Sep 07, 2008 at 12:02:06PM -0400, Barry Warsaw wrote: > There are 8 open release blockers, a few of which have patches that need > review. So I think we are still not ready to release rc1. But it > worries me because I think this is going to push the final release > beyond our October

[Python-Dev] 2.6 rc1 performance results

Three weeks ago, Antoine Pitrou posted the pybench results for 2.6 trunk: http://mail.python.org/pipermail/python-dev/2008-August/081951.html The big discovery in those results were TryExcept being 48% slower, but there was a patch in the bug tracker to improve things. I've re-run the tests to c

Re: [Python-Dev] [Python-checkins] python-checkins seems broken

On Sat, Oct 04, 2008 at 12:14:43AM +0200, Amaury Forgeot d'Arc wrote: > Do other subscribed people receive these commit messages? > Is there a problem with the mailer, or some SVN trigger? It looks like mail from dinsdale.python.org to mail.python.org isn't working due to a DNS issue: rcpt to: [E

Re: [Python-Dev] 3.1 focus (was Re: for __future__ import planning)

On Sat, Oct 04, 2008 at 09:45:27AM +0200, Georg Brandl wrote: > Barry Warsaw schrieb: > two problems: The libraries they depend on aren't ported, and the > KLOC of code they care about are hard and tedious work to port, not > to mention that it typically isn't viewed as productive work by those > w

Re: [Python-Dev] status of 2.5

On Mon, Oct 06, 2008 at 12:53:01PM -0700, Raymond Hettinger wrote: > The 2.6/3.0 development process was so disruptive that I doubt > that 2.5 received adequate attention for bug fixes. Why not wait > two or three months for the dust to settle? Can you please clarify your meaning? Do you mean tha

Re: [Python-Dev] Python 2.5.3: call for patches

On Tue, Oct 07, 2008 at 09:27:24AM +0200, "Martin v. Löwis" wrote: > Within a few weeks, we will release Python 2.5.3. This will be the last > bug fix release of Python 2.5, afterwards, future releases of 2.5 will > only include security fixes, and no binaries (for Windows or OSX) will > be provide

[Python-Dev] 2.5.3: assessing commits

I've begun the task of assessing the 2.6 commits, but the job is unexpectedly large. What I did: * Took the output of 'svn log -r60999:66717'. (2.5.2 was branched from rev. 60999, so I'm ignoring commits to the trunk before 2.5.2 was branch, which may miss some things.) * Wrote a little sc

Re: [Python-Dev] 2.5.3: assessing commits

On Tue, Oct 07, 2008 at 08:44:09PM -0400, A.M. Kuchling wrote: > At this point I still have 1191 files left. Many of these commits are > still irrelevant, but this is a lot for me to look through. A tarball > with the remaining commits is at > > http://www.amk.ca/f

Re: [Python-Dev] 2.5.3: assessing commits

On Wed, Oct 08, 2008 at 08:06:09AM -0400, A.M. Kuchling wrote: > look at commits individually. I'll turn the lists of commits into a > set of wiki pages that we can examine and edit down in parallel. I decided to put them in SVN instead, in sandbox/py2.5.3/ . How do we want to a

Re: [Python-Dev] Subversion access down?

On Thu, Oct 09, 2008 at 10:50:24AM +0200, Ulrich Eckhardt wrote: > Is it only me or does it fail for other people, too? I'm getting > > | Server sent unexpected return value (503 Service > | Unavailable) in response to OPTIONS request > | for 'http://svn.python.org/projects/python/trunk' svn.p

<    1   2   3   4   >