I'm preparing the argparse module for the 2.7 and 3.2 branches. Could
someone remind me again what the commit process is? Commit to 2.7 and
merge to 3.2? And do we merge with svnmerge.py or svn merge? There's
probably a webpage explaining this somewhere, but my Google-fu is
failing me right now.
Where did you get that preposterous hypothesis?
Did Steve tell you that?
--- The Hiphopopotamus
I had to reinstall my OS recently and I checked out pristine copies of
While svnmerge.py init on release26-maint and release31-maint worked
fine and I was able to merge a revision to release26-maint.
On py3k, the svn init gave the following problem.
$ python svnmerge.py init
svnmerge: command execution failed (exit code: 1)
svn --non-interactive info "svn+ssh://firstname.lastname@example.org/python/branches/py3k-struni"
svn+ssh://email@example.com/python/branches/py3k-struni: (Not a valid URL)
svn: A problem occurred; see other errors for details
What's the problem? How do I resolve it?
I'm organising a Python Language Summit on Sunday 18th July, in
Birmingham UK immediately preceding EuroPython 2010.
I'll be sending out invitations soon and would like to make sure I
include European Python-committers. If you're in Europe, or able to
come, please let me know so that I can include you (assuming I don't get
overwhelmed by responses...).
All the best,
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
On Mar 16, 2010, at 03:51 PM, Benjamin Peterson wrote:
>My plan is to tag 3.1.2 sometime on Thursday, so binaries can be built
>for the final release on Saturday. Agreeable?
I might as well do the same for 2.6.5, though I plan on releasing it Friday.