Re: [Python-Dev] Draft PEP 385: Migrating from svn to Mercurial
At PyCon, we discussed moving Jython's svn repository to Python's with Martin von Löwis. I would think that Jython would live in Python's hg repository in the same way as stackless and distutils. Has the parallel project strategy been determined? Will they be separate repositories, separate "forests", something else? Also, Martin suggested we migrate to Python's svn and then go along for the svn->hg ride. Does that still make sense now that some planning has been done? -Frank ___ 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] Roundup keywords for bug tracking
On Sat, Jun 6, 2009 at 4:07 AM, Daniel Diniz wrote: > anatoly techtonik wrote: >> >> It is impossible to edit roundup keywords and this takes away the >> flexibility in selecting bugs related to a module/function/test or >> some other aspect of development. For example, I need to gather all >> subprocess bugs in one query and things that won't be fixed in >> deprecated os.popen() into another. In Trac I would use "subprocess" >> and "os.popen" keywords. On ohloh I would add similar tags (if bugs >> were software) without, but I can't do anything about Python roundup. >> Is there any reason for such restriction? > > Well, keywords are used as a very restricted set of tags, so only > users in the Developer group can create them. We've discussed free > form issue tags that any user can create or edit in #python-dev and > tracker-discuss[0]. I'm pretty sure they'd cover your use-case. I've > submitted a patch to Rietveld[1], but it seems I never filled it in > the meta-tracker, oopsie. >From [0] discussion it seems that tags are planned to be a replacement for component or keywords field, but in my vision they should be just tags that doesn't have any specific meaning or administration interface. Autocomplete with ajax lookup is nice, but no drop-down lists etc. I made some comments in Rietveld at [1], but was unable to test it live, because [2] is offline. > If you (or anyone else) want to test-drive the tags feature, I can > create an account in the experimental tracker[2] (which needs some > attention anyway). I should be able to submit the patch to the > meta-tracker during the weekend. Hope this went well. I would definitely like to see how far this feature from how I imagine it, but b.p.o. deployment could be a better alternative for a real testing. > Also, if you would like to bookmark arbitrary sets of issues, the > bookmarklet and form in http://static.bot.bio.br/tool.html may be of > help. You can paste the ids into the search page's ID field and create > a query for a given (static) set of issues. Seems like it can come in handy. Thanks. -- anatoly t. ___ 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] Draft PEP 385: Migrating from svn to Mercurial
Frank Wierzbicki schrieb: > At PyCon, we discussed moving Jython's svn repository to Python's with > Martin von Löwis. I would think that Jython would live in Python's hg > repository in the same way as stackless and distutils. Has the > parallel project strategy been determined? Will they be separate > repositories, separate "forests", something else? It should definitely be a separate repository, repositories tend to be a smaller unit in hg than in SVN, due to the fact that partial clones/checkouts are not supported. > Also, Martin suggested we migrate to Python's svn and then go along > for the svn->hg ride. Does that still make sense now that some > planning has been done? I don't think so. It should not matter from which repository the conversion is done, especially since there is no shared history at all. 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 be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ 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] Draft PEP 385: Migrating from svn to Mercurial
On Mon, Jun 8, 2009 at 16:29, Frank Wierzbicki wrote: > At PyCon, we discussed moving Jython's svn repository to Python's with > Martin von Löwis. I would think that Jython would live in Python's hg > repository in the same way as stackless and distutils. Has the > parallel project strategy been determined? Will they be separate > repositories, separate "forests", something else? I think they should just be separate repositories. The svn.python.org "repository" is more like a collection of actual repositories than a repository in itself. > Also, Martin suggested we migrate to Python's svn and then go along > for the svn->hg ride. Does that still make sense now that some > planning has been done? I'd say migrating to Python's svn doesn't make a whole lot of sense at this point, but I'll leave that to Martin (since he has to do the work). For the conversion, I can just as well take the Jython repo from your current server. I've started a svnsync job with your repo so I can run some test conversions. It's a relatively small repository, so it shouldn't be much of a problem. Cheers, Dirkjan ___ 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] Status of 2.7 and 3.2
On Sun, Jun 7, 2009 at 6:21 AM, Terry Reedy wrote: > > I have thought that 2.7 was now to come out instead with 3.2 and would > include backported 3.2 new features. Others expect 2.7 to come out soon > after 3.1 and to only contain new 3.1 features. So Guido or someone, please > clarify: is 2.7 to be the counterpart of 3.1 or 3.2? Just my 0.02 cents, but struggling with all warts of 2.5 subprocessing in Windows I would vote for more time for stabilizating things - not adding new features. Long awaited subprocess as replacement for os.popen() AFAIK is still incapable to asynchronously communicate with spawned processes on Windows. I would call this feature as critical even on 2.6 As a release testcase - try porting pyexpect module to this platform. Absence of native curses/console/readline module also makes Python one-way unix shell language while many users expect it to be crossplatform. -- anatoly t. ___ 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] Status of 2.7 and 3.2
anatoly techtonik gmail.com> writes: > > Just my 0.02 cents, but struggling with all warts of 2.5 subprocessing > in Windows I would vote for more time for stabilizating things - not > adding new features. Long awaited subprocess as replacement for > os.popen() AFAIK is still incapable to asynchronously communicate with > spawned processes on Windows. I would call this feature as critical > even on 2.6 As a release testcase - try porting pyexpect module to > this platform. Absence of native curses/console/readline module also > makes Python one-way unix shell language while many users expect it to > be crossplatform. As always, patches and proposals are welcome! However, as far as the above issues are concerned, it seems to be less a matter of time between releases than of motivation to get things done (tm). I don't think a knowledgeable and determined Windows programmer would have much trouble solving each of them. Regards Antoine. ___ 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] Draft PEP 385: Migrating from svn to Mercurial
On Mon, Jun 8, 2009 at 11:32 AM, Dirkjan Ochtman wrote: > I'd say migrating to Python's svn doesn't make a whole lot of sense at > this point, but I'll leave that to Martin (since he has to do the > work). For the conversion, I can just as well take the Jython repo > from your current server. I've started a svnsync job with your repo so > I can run some test conversions. It's a relatively small repository, > so it shouldn't be much of a problem. Great! Thanks for giving this a try! For my part I'm fine either way (and I agree that Martin should decide based on what is best for him). -Frank ___ 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] Draft PEP 385: Migrating from svn to Mercurial
Frank Wierzbicki schrieb: > On Mon, Jun 8, 2009 at 11:32 AM, Dirkjan Ochtman wrote: >> I'd say migrating to Python's svn doesn't make a whole lot of sense at >> this point, but I'll leave that to Martin (since he has to do the >> work). For the conversion, I can just as well take the Jython repo >> from your current server. I've started a svnsync job with your repo so >> I can run some test conversions. It's a relatively small repository, >> so it shouldn't be much of a problem. > Great! Thanks for giving this a try! > > For my part I'm fine either way (and I agree that Martin should decide > based on what is best for him). For CPython, we still need SVN, e.g. for the website repo, and several others like it that probably won't get converted (yet), and also for reference since we won't convert every old branch to hg. If that isn't necessary for Jython, I see no reason for moving into svn.python.org first. 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 be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ 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] Draft PEP 385: Migrating from svn to Mercurial
>> Also, Martin suggested we migrate to Python's svn and then go along >> for the svn->hg ride. Does that still make sense now that some >> planning has been done? > > I don't think so. It should not matter from which repository the conversion > is done, especially since there is no shared history at all. Also, I would not merge the Jython SVN into the /projects repository, but instead set up a separate repository (http://svn.python.org/jython, and svn+ssh://jyt...@svn.python.org/). As discussed at PyCon, we should collect SSH keys for Jython committers in advance of the svn switchover; we would have to do that either way (also for hg), so now might be the right time to start doing it. As for the repository organization: I have now opinion (or, rather, no experience with hg). 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] Draft PEP 385: Migrating from svn to Mercurial
> For my part I'm fine either way (and I agree that Martin should decide > based on what is best for him). See my other message. We need to collect SSH keys, and I don't mind moving the Jython repository. OTOH, if the Jython repository gets converted into hg right away, it's certainly (a little) less work. Of course, the Jython committers would need to relocate their svn sandboxes now, and then completely abandon them and re-checkout from hg in a few months, so if you can wait a few months until the hg conversion is ready, it's also less work for your committers. FWIW, I really think that PEP 385 should really grow a timeline pretty soon. Are we going to switch this year, next year, or 2011? 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] Status of 2.7 and 3.2
> Just my 0.02 cents, but struggling with all warts of 2.5 subprocessing
> in Windows I would vote for more time for stabilizating things - not
> adding new features. Long awaited subprocess as replacement for
> os.popen() AFAIK is still incapable to asynchronously communicate with
> spawned processes on Windows. I would call this feature as critical
> even on 2.6 As a release testcase - try porting pyexpect module to
> this platform. Absence of native curses/console/readline module also
> makes Python one-way unix shell language while many users expect it to
> be crossplatform.
I am not quite sure whether you are for new features or not. Your
first sentence ("vote for ... not adding new features") seems to
suggest that you would not like to see new features, and your last
sentence ("absence of native curses/console/readline module")
suggests that you *do* want to see new features (namely, a native
curses module, and a native readline module).
Which one is it?
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] Draft PEP 385: Migrating from svn to Mercurial
On Mon, Jun 8, 2009 at 3:57 PM, "Martin v. Löwis" wrote: > FWIW, I really think that PEP 385 should really grow a timeline > pretty soon. Are we going to switch this year, next year, or 2011? > +1 -- Alexandre ___ 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] Draft PEP 385: Migrating from svn to Mercurial
On Mon, Jun 8, 2009 at 21:57, "Martin v. Löwis" wrote: > See my other message. We need to collect SSH keys, and I don't mind > moving the Jython repository. OTOH, if the Jython repository gets > converted into hg right away, it's certainly (a little) less work. Yeah, I guess if you move it to a separate repo on the svn.python.org server that might be nice. But it's not a big deal either way. > FWIW, I really think that PEP 385 should really grow a timeline > pretty soon. Are we going to switch this year, next year, or 2011? Sorry, I should've been clearer. I fully intend to complete the conversion in a few months, say by October 1st or sooner. That would be between 3.1 and whatever the next release will end up being, I hope? It's just hard to be very specific at this point. BTW, I tried my hand at rewriting the revlog for the manifest, as described in the PEP, and it made the full conversion *much* (as in 70%) smaller. I've also been looking at what branches we should keep and will ask for definitive feedback on that point soonish. Cheers, Dirkjan ___ 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] Cannot set PYTHONPATH with big paths with Python 3.0 and 3.1
Hi all, I've reported bug http://bugs.python.org/issue5924 some time ago and I think it's a release blocker -- it seems easy to fix, but I don't have time to actually submit a patch, so, I'd like to draw attention to it, especially as a release candidate is already out. Cheers, Fabio ___ 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] Cannot set PYTHONPATH with big paths with Python 3.0 and 3.1
> I've reported bug http://bugs.python.org/issue5924 some time ago and I > think it's a release blocker -- it seems easy to fix, but I don't have > time to actually submit a patch, so, I'd like to draw attention to it, > especially as a release candidate is already out. In absence of a patch, it can't be a release blocker, IMO. It's not a really critical bug (just an annoying one), as it is possible to work around it (e.g. by setting sys.path in sitecustomize, or by moving all modules into a single directory so that sys.path doesn't have to be that long). If nobody else has time to submit a patch, either, Python 3.1 will get released with this bug. 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
