Re: [Python-Dev] Python source code on Bazaar vcs
[EMAIL PROTECTED] wrote: > Benjamin> Once you've pushed the branches, is there a way to remove them? > > Related question: is there a way to view the various branches in a non-local > repository? IIUC, conceptually, no. A branch is not *in* a repository; a branch *is* a repository (*). So your question is almost equivalent to "is there a way to find out all clones of a repository that have ever been made?", to which the answer is "no". Now, if you have a convention of where you put the branches, you should be able to find them later. E.g. if they are all in a directory tree that is exposed through http, you can use a web browser to see them, e.g. by going to http://code.python.org/python/users/skip/ Likewise, if you are accessing the repository over bzr+ssh, in general, you can just ssh to the machine, and do a regular ls. In the specific setup, regular ssh is restricted to running "bzr serve", which (apparently) has no support for directory browsing. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Python source code on Bazaar vcs
>> Once you've pushed the branches, is there a way to remove them? > > Do you mean the local branches? If yes, then 'rm -rf mymergedbranch' > does exactly what you want. :) Notice that, unlike subversion, this will cause the entire branch to go away, irrevocably (unless you had pushed it elsewhere before, or was branched from). IIUC, if this is a "shared repository", the actual revisions will still be stored, but unaccessible, as the branch files store the information what revision was the head revision. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] nested classes leaking in compiler
Amaury Forgeot d'Arc schrieb:
> The approach I used is a bit brute-force, but it may work for other
> reference leaks:
> - First write a big leaking script:
> for x in xrange(10): leaking_function()
> - Since memory usage does not increase dramatically, it's only a
> refcount problem - no new object every time.
> - Modify the Py_INCREF macro so that it generates a breakpoint in the
> debugger when the refcount is large:
> On Windows, it is something like:
> if (ob->refcount > 1) { __asm int 3; }
> (with gdb I think you may signal SIGUSR1)
> - carefully inspect the code each time the debugger stops.
> Fortunately, many functions can be skipped: PyDict_SetItem and other
> bullet-proof parts of the code.
> The 20th break was the good one: a lack of symmetry between
> Py_INCREF and Py_DECREF.
Nice! Can you write a short howto for the wiki? The idea is ingenious.
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] No time for svn merge
For your information: I won't have time to do another svn merge before the next alphas of 2.6 and 3.0 are to be released. Somebody else has to do the merge. Christian ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
> I won't have time to do another svn merge before the next alphas of 2.6 > and 3.0 are to be released. Somebody else has to do the merge. I merged a few revisions, but I'm done now (until Tuesday or so). Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
On Sun, Mar 30, 2008 at 3:51 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > I won't have time to do another svn merge before the next alphas of 2.6 > > and 3.0 are to be released. Somebody else has to do the merge. > > I merged a few revisions, but I'm done now (until Tuesday or so). If you'd like, I can merge the rest. > > > Regards, > Martin > ___ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/musiccomposition%40gmail.com > -- Cheers, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
On Sun, Mar 30, 2008 at 5:54 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > If you have the time to figure it all out, sure. > I found that quite a tedious task, and had to spent > on some patches quite a long time to figure out what > they do, and what the 3.x equivalent should be. > Is there any easy way that the burden of trunk -> py3k merging could be moved to the original committers of the trunk patches? Presumably the original committer of a patch is well-placed to understand what the patch does and how best to translate it to 3.0. Mark ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
> If you'd like, I can merge the rest. If you have the time to figure it all out, sure. I found that quite a tedious task, and had to spent on some patches quite a long time to figure out what they do, and what the 3.x equivalent should be. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
> Is there any easy way that the burden of trunk -> py3k > merging could be moved to the original committers of > the trunk patches? I'm not sure I understand the question. If the committer of the original patch would do the merge himself, then certainly the burden would be on him, and that's an easy way. If you meant to say "an easy way to enforce...", then I cannot see how that could work, other than establishing that as a policy, and starting to revoke commit privileges to people who don't follow the policy. Rather than actually merging changes, one could start sending out messages automatically to committers who don't either merge or block their changes within 24 hours (or send a summary message every day to python-dev). Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
On Sun, Mar 30, 2008 at 5:16 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > Is there any easy way that the burden of trunk -> py3k > > merging could be moved to the original committers of > > the trunk patches? > > I'm not sure I understand the question. If the committer > of the original patch would do the merge himself, then > certainly the burden would be on him, and that's an easy > way. > > If you meant to say "an easy way to enforce...", then I > cannot see how that could work, other than establishing > that as a policy, and starting to revoke commit privileges > to people who don't follow the policy. I think we could just ask politely and try it for a while. If things aren't working, we can reevaluate. > > > Rather than actually merging changes, one could start > sending out messages automatically to committers who > don't either merge or block their changes within 24 hours > (or send a summary message every day to python-dev). Like above, let's try a little before we start setting up new infrastructure left and right. > > > Regards, > Martin > > > -- Cheers, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
On Sun, Mar 30, 2008 at 6:16 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > Is there any easy way that the burden of trunk -> py3k > > merging could be moved to the original committers of > > the trunk patches? > > I'm not sure I understand the question. If the committer > of the original patch would do the merge himself, then > certainly the burden would be on him, and that's an easy > way. > Yes, that's all I meant: make it the committer's job to merge or block as appropriate. I just wasn't sure if there was some reason that this would be difficult or undesirable. I'm not suggesting that this be enforced (mechanically or otherwise); just that it might be worth considering instituting a policy to encourage individual committers to take responsibility for forward porting their commits. Mark ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
On Sun, Mar 30, 2008 at 4:54 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > If you'd like, I can merge the rest. > > If you have the time to figure it all out, sure. > I found that quite a tedious task, and had to spent > on some patches quite a long time to figure out what > they do, and what the 3.x equivalent should be. Ok. I merged some more of the low hanging fruit. Somebody who understands AST better than me should probably do the merges with that. > > > Regards, > Martin > -- Cheers, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
On Sun, Mar 30, 2008 at 7:41 PM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > > > > On Sun, Mar 30, 2008 at 4:54 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> > wrote: > > > > > If you'd like, I can merge the rest. > > > > If you have the time to figure it all out, sure. > > I found that quite a tedious task, and had to spent > > on some patches quite a long time to figure out what > > they do, and what the 3.x equivalent should be. > Ok. I merged some more of the low hanging fruit. Somebody who understands > AST better than me should probably do the merges with that. Are you done for today/tonight? If so, I can merge the rest. The last checkin to regrtest I saw looked like it doesn't work. I thought it had print foo without parens. Did I miss something? n ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Py3k and asyncore/asynchat
(sorry for top posting) I haven't really had time to update the tests/documentation, but again, I wasn't experiencing any strange test failures with asyncore/asynchat, nor have I been able to find the buildbot failures that you are referring to. Could someone please link the failures that are not related to being unable to discover a port number? According to the release schedule, we should have at least a couple more months for documentation and tests to be updated (I can get patches ready for alpha 3). - Josiah On Wed, Mar 26, 2008 at 12:21 AM, Josiah Carlson <[EMAIL PROTECTED]> wrote: > On Tue, Mar 25, 2008 at 11:26 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > > Any reason this was sent just to me and not the list? > > Because gmail only replies to the sender by default. I need to > remember to cc python-dev when I reply (I used the same email client > for 8 1/2 years, remembering the quirks of gmail may take some time). > > > > > On Tue, Mar 25, 2008 at 10:34 PM, Josiah Carlson > > <[EMAIL PROTECTED]> wrote: > > > > > > On Tue, Mar 25, 2008 at 9:00 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > > > > On Thu, Feb 14, 2008 at 10:09 AM, Giampaolo Rodola' <[EMAIL > PROTECTED]> wrote: > > > > > On 14 Feb, 16:36, "Giampaolo Rodola'" <[EMAIL PROTECTED]> wrote: > > > > > > Ok, I'll try to take a look at all asyncore/chat reports and > try to > > > > > > summarize them by splitting patches which solve bugs and > patches which > > > > > > add enhancements or functionalities. > > > > > > > > > > > > > > > > > > === Patches for existing issues === > > > > > > > > > > - 1736190 which includes fixes for the following issues among > other > > > > > improvements: > > > > > - 1063924 (asyncore should handle ECONNRESET in send()) > > > > > - 1736101 (asyncore should handle ECONNABORTED in recv()) > > > > > - 760475 (handle_error() should call handle_close() instead of > > > > > close()) > > > > > - 1740572 (refill_buffer() should call handle_close() rather > than > > > > > close()) > > > > > - 777588 (wrong "connection refused" behavior on Windows) > > > > > - 889153 (wrong connect() behavior) > > > > > - 953599 (asyncore misses socket closes when poll is used) > > > > > - 1025525 (asyncore.file_dispatcher should not take fd as > argument) > > > > > > > > > > - 1519 (async_chat.__init__() and asyncore.dispatcher.__init__ > > > > > parameters inconsistency) > > > > > - 1541 (Bad OOB data management when using asyncore with > > > > > select.poll()) > > > > > - 2073 (asynchat push always sends 512 bytes (ignoring > > > > > ac_out_buffer_size)) > > > > > > > > > > > > > > > === Open issues with no patches (need review) === > > > > > > > > > > - 658749 (asyncore connect() and winsock errors) > > > > > - 1161031 (neverending warnings from asyncore) > > > > > > > > > > > > > > > === Enhancements & new features === > > > > > > > > > > - 1641 (add delayed calls feature) > > > > > - 1563 (conversion to py3k and some other changes) > > > > > > > > That's a lot of patches. My immediate concern is that test_asynchat > > > > is very flaky and fails often. Sometimes it causes other tests to > > > > fail. Is there a patch that addresses this? If you need examples, > > > > just look through the buildbot mails that mention test_asynchat in: > > > > http://mail.python.org/pipermail/python-checkins/ > > > > > > No, it's one patch. All of the fixes were performed mostly by myself > > > last spring, tested and verified in personal servers, then re-used by > > > Giampaolo in his async ftp server (which pointed out a few small bugs, > > > which have been fixed). > > > > > > > > > > Some platforms have more problems than others, but almost all > > > > platforms have failed test_asynchat at one point or another. > > > > > > Certainly that is the case. And according to my reading of a few > > > buildbot failures, aside from someone breaking asyncore itself, the > > > failures seem to stem from the test being unable to create a port to > > > listen on in order to test the server/client functionality. This is a > > > buildbot configuration issue (per host), not an asyncore issue. > > > > That was the case a long time (~3? months) ago, but hasn't been the > > case recently. See my recent message about the release. > > I'll look for it tomorrow. For reference, searches of > 'site:mail.python.org test_asynchat failure buildbot' only seem to > produce the socket listen error. If there is a better incantation to > get google to produce the proper errors (and/or a link), I would > appreciate the help. > > > > > > > Please break up the patches into 2 sets and prioritize the patches > > > > with the set. > > > > > > > > Set #1: Patches th
Re: [Python-Dev] No time for svn merge
On Sun, Mar 30, 2008 at 9:43 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > On Sun, Mar 30, 2008 at 7:41 PM, Benjamin Peterson > <[EMAIL PROTECTED]> wrote: > > > > > > > > On Sun, Mar 30, 2008 at 4:54 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> > > wrote: > > > > > > > If you'd like, I can merge the rest. > > > > > > If you have the time to figure it all out, sure. > > > I found that quite a tedious task, and had to spent > > > on some patches quite a long time to figure out what > > > they do, and what the 3.x equivalent should be. > > Ok. I merged some more of the low hanging fruit. Somebody who > understands > > AST better than me should probably do the merges with that. > > Are you done for today/tonight? If so, I can merge the rest. Be my guest! I'm going to bed. > > > The last checkin to regrtest I saw looked like it doesn't work. I > thought it had print foo without parens. Did I miss something? I just merged it incorrectly, so I reverted it. > > > n > -- Cheers, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] No time for svn merge
> Yes, that's all I meant: make it the committer's job > to merge or block as appropriate. I just wasn't sure if > there was some reason that this would be difficult or > undesirable. Ah, yes. It is indeed difficult or undesirable, or was so in the past: Some committers don't care (didn't care) at all about 3k. They would have to setup sandboxes, learn what the nature of changes is, and invest some regular time into forward-porting. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
