From faassen at startifact.com Tue Nov 6 21:39:14 2007 From: faassen at startifact.com (Martijn Faassen) Date: Tue, 06 Nov 2007 21:39:14 +0100 Subject: [py-dev] py.path svn status() does not support R Message-ID: Hi there, In wccommand.py there is a status() method with support for retrieving the status of files in SVN. At some point there's an else branch that I'm now hitting: else: raise NotImplementedError("received flag %r" % % c0) My svn working copy contains files with status 'R'. What does this mean? Item has been replaced in your working copy. This means the file was scheduled for deletion, and then a new file with the same name was scheduled for addition in its place It would be nice if py.path had support for this case instead of bailing out with a NotImplementedError. Regards, Martijn From cfbolz at gmx.de Tue Nov 6 23:13:21 2007 From: cfbolz at gmx.de (Carl Friedrich Bolz) Date: Tue, 06 Nov 2007 23:13:21 +0100 Subject: [py-dev] py.path svn status() does not support R In-Reply-To: References: Message-ID: <4730E701.7000508@gmx.de> Hi Martijn, Martijn Faassen wrote: > In wccommand.py there is a status() method with support for retrieving > the status of files in SVN. > > At some point there's an else branch that I'm now hitting: > > else: > raise NotImplementedError("received flag %r" % % c0) > > My svn working copy contains files with status 'R'. What does this mean? > > Item has been replaced in your working copy. > This means the file was scheduled for deletion, and > then a new file with the same name was scheduled for > addition in its place > > It would be nice if py.path had support for this case instead of bailing > out with a NotImplementedError. I implemented this in revision 48347. I guess you could have done it yourself in the time you wrote this mail ? it was completely trivial :-). Cheers, Carl Friedrich From faassen at startifact.com Wed Nov 7 16:08:39 2007 From: faassen at startifact.com (Martijn Faassen) Date: Wed, 07 Nov 2007 16:08:39 +0100 Subject: [py-dev] py.path svn status() does not support R In-Reply-To: <4730E701.7000508@gmx.de> References: <4730E701.7000508@gmx.de> Message-ID: Carl Friedrich Bolz wrote: [snip] >> It would be nice if py.path had support for this case instead of bailing >> out with a NotImplementedError. > > I implemented this in revision 48347. I guess you could have done it > yourself in the time you wrote this mail ? it was completely trivial :-). Thanks! I didn't have a development copy set up at all, so it'd taken a bit more time than that. I'm using a release as just one more egg that's coming in. No tests to write either? Regards, Martijn From faassen at startifact.com Wed Nov 7 16:12:32 2007 From: faassen at startifact.com (Martijn Faassen) Date: Wed, 07 Nov 2007 16:12:32 +0100 Subject: [py-dev] a new py release? Message-ID: Hi there, The latest release on the cheeseshop is Py 0.9, from last february. Since the trunk now contains a bugfix I'd like to have, this is a good time to start bugging you guys for a release again. :) What would releasing a new version of py entail? Do you guys maintain a changelog? I just tried to look for one in SVN but I can't find one. I can find a TODO.txt in doc with todo items. Regards, Martijn From fijal at genesilico.pl Wed Nov 7 16:32:52 2007 From: fijal at genesilico.pl (Maciek Fijalkowski) Date: Wed, 07 Nov 2007 16:32:52 +0100 Subject: [py-dev] a new py release? In-Reply-To: References: Message-ID: <4731DAA4.5000100@genesilico.pl> Martijn Faassen wrote: > Hi there, > > The latest release on the cheeseshop is Py 0.9, from last february. > Since the trunk now contains a bugfix I'd like to have, this is a good > time to start bugging you guys for a release again. :) > > What would releasing a new version of py entail? Do you guys maintain a > changelog? I just tried to look for one in SVN but I can't find one. I > can find a TODO.txt in doc with todo items. > > Regards, > > Martijn > The first thing on todo list is to bug holger to find some time for pylib :-) I've got quite a bit pending changes on a branch and would like to have it merged before the release. There are also other things to do (such as rewrite of web reporter) to make things even more cool, but IMHO the main blocker is lack of tutorial/easy-startup on the web page. Cheers, fijal :. From cfbolz at gmx.de Wed Nov 7 17:44:47 2007 From: cfbolz at gmx.de (Carl Friedrich Bolz) Date: Wed, 07 Nov 2007 17:44:47 +0100 Subject: [py-dev] a new py release? In-Reply-To: <4731DAA4.5000100@genesilico.pl> References: <4731DAA4.5000100@genesilico.pl> Message-ID: <4731EB7F.20309@gmx.de> Maciek Fijalkowski wrote: > Martijn Faassen wrote: >> The latest release on the cheeseshop is Py 0.9, from last february. >> Since the trunk now contains a bugfix I'd like to have, this is a good >> time to start bugging you guys for a release again. :) >> >> What would releasing a new version of py entail? Do you guys maintain a >> changelog? I just tried to look for one in SVN but I can't find one. I >> can find a TODO.txt in doc with todo items. >> >> Regards, >> >> Martijn >> > The first thing on todo list is to bug holger to find some time for > pylib :-) I agree with that :-). > I've got quite a bit pending changes on a branch and would > like to have it merged before the release. There are also other things > to do (such as rewrite of web reporter) to make things even more cool, > but IMHO the main blocker is lack of tutorial/easy-startup on the web page. What's wrong with this page: http://codespeak.net/py/dist/test.html ? I quite liked it when I learned about py.test first. Cheers, Carl Friedrich From cfbolz at gmx.de Wed Nov 7 17:47:18 2007 From: cfbolz at gmx.de (Carl Friedrich Bolz) Date: Wed, 07 Nov 2007 17:47:18 +0100 Subject: [py-dev] py.path svn status() does not support R In-Reply-To: References: <4730E701.7000508@gmx.de> Message-ID: <4731EC16.2010009@gmx.de> Martijn Faassen wrote: > Carl Friedrich Bolz wrote: > [snip] >>> It would be nice if py.path had support for this case instead of bailing >>> out with a NotImplementedError. >> I implemented this in revision 48347. I guess you could have done it >> yourself in the time you wrote this mail ? it was completely trivial :-). > > Thanks! > > I didn't have a development copy set up at all, so it'd taken a bit more > time than that. I'm using a release as just one more egg that's coming > in. No tests to write either? Of course a test. Test: 12 lines, actual fix: 3 lines. Just kidding, of course, it was a 5 min job for me, so I am not complaining. Cheers, Carl Friedrich From faassen at startifact.com Wed Nov 7 18:07:23 2007 From: faassen at startifact.com (Martijn Faassen) Date: Wed, 7 Nov 2007 18:07:23 +0100 Subject: [py-dev] py.path svn status() does not support R In-Reply-To: <4731EC16.2010009@gmx.de> References: <4730E701.7000508@gmx.de> <4731EC16.2010009@gmx.de> Message-ID: <8928d4e90711070907l4ca4f6bcl5443c3d046b5e1c2@mail.gmail.com> Hey, On Nov 7, 2007 5:47 PM, Carl Friedrich Bolz wrote: > Martijn Faassen wrote: [snip] > > I didn't have a development copy set up at all, so it'd taken a bit more > > time than that. I'm using a release as just one more egg that's coming > > in. No tests to write either? > > Of course a test. Test: 12 lines, actual fix: 3 lines. Just kidding, of > course, it was a 5 min job for me, so I am not complaining. Thanks again for the fix. It would've taken me a bit more time to figure out how to set everything up. Anyway, a good bug report is half the fix already. :) Regards, Martijn From holger at merlinux.de Thu Nov 8 17:40:57 2007 From: holger at merlinux.de (holger krekel) Date: Thu, 8 Nov 2007 17:40:57 +0100 Subject: [py-dev] a new py release? In-Reply-To: <4731EB7F.20309@gmx.de> References: <4731DAA4.5000100@genesilico.pl> <4731EB7F.20309@gmx.de> Message-ID: <20071108164057.GO27907@solar.trillke> On Wed, Nov 07, 2007 at 17:44 +0100, Carl Friedrich Bolz wrote: > Maciek Fijalkowski wrote: > > Martijn Faassen wrote: > >> The latest release on the cheeseshop is Py 0.9, from last february. > >> Since the trunk now contains a bugfix I'd like to have, this is a good > >> time to start bugging you guys for a release again. :) > >> > >> What would releasing a new version of py entail? Do you guys maintain a > >> changelog? I just tried to look for one in SVN but I can't find one. I > >> can find a TODO.txt in doc with todo items. > >> > >> Regards, > >> > >> Martijn > >> > > The first thing on todo list is to bug holger to find some time for > > pylib :-) > > I agree with that :-). me as well ... However, i am still in sabbatical and hardly-online-at-all mode. should we go for a 0.9.1 release by backporting (verbatim, if possible) some bugfixes and their tests from dist/trunk to svn/py/release/0.9.x and then releasing 0.9.1 from it? I think that going for merging Maciej's reporter branch, reviewing accumulated trunk and dist changes is too much - i wouldn't like to tackle it this year (at least if you ask me today). Martijn, a related question: aren't you involved with launchpad? Do you think using it would be benefitial for the py lib and its development/releases? Could you possibly help with setting us up? What do others think about the idea? best & cheers, holger > > I've got quite a bit pending changes on a branch and would > > like to have it merged before the release. There are also other things > > to do (such as rewrite of web reporter) to make things even more cool, > > but IMHO the main blocker is lack of tutorial/easy-startup on the web > page. > > What's wrong with this page: http://codespeak.net/py/dist/test.html ? I > quite liked it when I learned about py.test first. > > Cheers, > > Carl Friedrich > _______________________________________________ > py-dev mailing list > py-dev at codespeak.net > http://codespeak.net/mailman/listinfo/py-dev > -- merlinux GmbH Steinbergstr. 42 31139 Hildesheim http://merlinux.de tel +49 5121 20800 75 (fax 77) From faassen at startifact.com Thu Nov 8 22:11:52 2007 From: faassen at startifact.com (Martijn Faassen) Date: Thu, 8 Nov 2007 22:11:52 +0100 Subject: [py-dev] a new py release? In-Reply-To: <20071108164057.GO27907@solar.trillke> References: <4731DAA4.5000100@genesilico.pl> <4731EB7F.20309@gmx.de> <20071108164057.GO27907@solar.trillke> Message-ID: <8928d4e90711081311yc081a00g66ccbfab20c697a7@mail.gmail.com> Hi there, On Nov 8, 2007 5:40 PM, holger krekel wrote: [about a Py release] > should we go for a 0.9.1 release by backporting (verbatim, if possible) some > bugfixes and their tests from dist/trunk to svn/py/release/0.9.x and then > releasing 0.9.1 from it? > I think that going for merging Maciej's reporter branch, reviewing > accumulated trunk and dist changes is too much - i wouldn't like to tackle it > this year (at least if you ask me today). best & cheers, > > holger > Backporting would be work for people, but might be the most stable way to go about it if you think the trunk contains a lot of destabilizing changes. Does it? This sounds like you should be doing a release more often so that so many changes don't get a chance to accumulate. :) > Martijn, a related question: aren't you involved with launchpad? Do you think > using it would be benefitial for the py lib and its development/releases? > Could you possibly help with setting us up? What do others think about the idea? I'm not involved with launchpad at all in any official capacity, I'm just a user. I use it in a couple of projects. I don't recall setting up launchpad project accounts myself but I think it's just a matter of getting a sign-in and requesting a new project, unless there's data to port. I'm not 100% happy about the launchpad user interface; I always keep having to hunt up how to use the issue tracker each time I use it. Roundup was simpler. Kit even released a note for Infrae customers: http://www.infrae.com/products/silva/auxiliary_docs/launchpad_mapping Launchpad does add a lot of planning features and so on but I suspect these need a project of significant size to be very useful. So, if you need an issue tracker and more, Launchpad might be useful. What I'm mostly hoping for myself is that you guys develop a procedure to do some form of regular releases to the cheeseshop so I can get to bugfixes without having to wait an unknown period. :) Regards, Martijn From fijal at genesilico.pl Fri Nov 9 14:00:46 2007 From: fijal at genesilico.pl (Maciek Fijalkowski) Date: Fri, 09 Nov 2007 14:00:46 +0100 Subject: [py-dev] a new py release? In-Reply-To: <8928d4e90711081311yc081a00g66ccbfab20c697a7@mail.gmail.com> References: <4731DAA4.5000100@genesilico.pl> <4731EB7F.20309@gmx.de> <20071108164057.GO27907@solar.trillke> <8928d4e90711081311yc081a00g66ccbfab20c697a7@mail.gmail.com> Message-ID: <473459FE.2090106@genesilico.pl> Martijn Faassen wrote: > Hi there, > > On Nov 8, 2007 5:40 PM, holger krekel wrote: > [about a Py release] > > >> should we go for a 0.9.1 release by backporting (verbatim, if possible) some >> bugfixes and their tests from dist/trunk to svn/py/release/0.9.x and then >> releasing 0.9.1 from it? >> > > >> I think that going for merging Maciej's reporter branch, reviewing >> accumulated trunk and dist changes is too much - i wouldn't like to tackle it >> this year (at least if you ask me today). >> > best & cheers, > >> holger >> >> > Backporting would be work for people, but might be the most stable way > to go about it if you think the trunk contains a lot of destabilizing > changes. Does it? > > This sounds like you should be doing a release more often so that so > many changes don't get a chance to accumulate. :) > +1 for 0.9.1 from me. Including all bugfixes & cheesshop entry. > >> Martijn, a related question: aren't you involved with launchpad? Do you think >> using it would be benefitial for the py lib and its development/releases? >> Could you possibly help with setting us up? What do others think about the idea? >> > > I'm not involved with launchpad at all in any official capacity, I'm > just a user. I use it in a couple of projects. I don't recall setting > up launchpad project accounts myself but I think it's just a matter of > getting a sign-in and requesting a new project, unless there's data to > port. > > I'm not 100% happy about the launchpad user interface; I always keep > having to hunt up how to use the issue tracker each time I use it. > Roundup was simpler. Kit even released a note for Infrae customers: > > http://www.infrae.com/products/silva/auxiliary_docs/launchpad_mapping > > Launchpad does add a lot of planning features and so on but I suspect > these need a project of significant size to be very useful. > > So, if you need an issue tracker and more, Launchpad might be useful. > What I'm mostly hoping for myself is that you guys develop a procedure > to do some form of regular releases to the cheeseshop so I can get to > bugfixes without having to wait an unknown period. :) > > Regards, > > Martijn > I think the holger point is about decreasing the cost of maintining codespeak for all projects, but that's just my opinion. IMHO we would never like the idea of not being able to do svn commit for everything. :. From fijal at genesilico.pl Tue Nov 27 21:39:24 2007 From: fijal at genesilico.pl (Maciek Fijalkowski) Date: Tue, 27 Nov 2007 21:39:24 +0100 Subject: [py-dev] pylib Message-ID: <474C807C.1070202@genesilico.pl> Regarding issue that you filled. This is a known cpython bug. I cannot really do much, but on svn trunk it's fixed. We will try to have 0.9.1 release which would be a bug-fix only release. Cheers, fijal :.