Hello, skip@pobox.com wrote:

martin> The Python source code repository is now converted to martin> subversion; please feel free to start checking out new martin> sandboxes.

Excellent... Thanks for all the effort.

Good work. I checked the http and viewcvs access and all worked. But why is an old subversion used ? (Powered by Subversion version 1.1.4) bye by Wolfgang

Am 27.10.2005 um 19:18 schrieb Martin v. Löwis:

Walter Dörwald wrote:

...

Thanks for doing this. BTW, will there be daily tarballs, like the one available from: http://cvs.perl.org/snapshots/python/python/python-latest.tar.gz

Will be, yes (I'm saddened that you refer to this location, and not http://www.dcl.hpi.uni-potsdam.de/home/loewis/python.tgz :-)

I didn't know that, although I probably should, the links are on the official page at http://www.python.org/dev/. ;) BTW, http://www.dcl.hpi.uni-potsdam.de/home/loewis/python.tgz is just 45 bytes.

I'm planning to provide them at http://svn.python.org/snapshots.

Great! BTW, ViewCVS seems to be missing the stylesheet. http:// svn.python.org/view/*docroot*/styles.css gives an exception complaining about "No such file or directory: '/etc/viewcvs/doc/ styles.css'" Bye, Walter Dörwald

On 27 okt 2005, at 19.57, Martin v. Löwis wrote:

Michael Hudson wrote:

...

Do checkins to svn.python.org go to the python-checkins list already?

They do indeed - you should have received one commit message by now (me testing whether committing works, on PEP 347).

Could the subject lines of those messages please be changed to something more informative? Having which files were changed in the subject seems better than having only the new rev and the folders the files are in. //Simon

On Sat, 2005-10-29 at 12:44, "Martin v. Löwis" wrote:

What do others think? I personally found those long subject lines listing all the changed files very ugly and unreadable.

Me too. At work our subject lines contain something like: Subject: [SVN][reponame] checkin of r12345 - dir/containing/changes Note that we send a different commit message for every directory the change happens in, even though it's all one revision. We like it that way because some people don't care about certain directories and can filter based on that. Inside the body of the email you'll see something like: Author: person Date: when New Revision: r12345 Log: Log message comes next. Definitely best to show up before the diff. diff comes next... FWIW, this format has worked well for us. -Barry

Guido van Rossum wrote:

Woo hoo! Thanks for all the hard work and good thinking, Martin.

My pleasure!

...

svn+ssh://pythondev@svn.python.org/python/trunk svn+ssh://pythondev@svn.python.org/python/branches/release24-maint svn+ssh://pythondev@svn.python.org/peps

This doesn't work for me. I'm sure the problem is on my end, but my svn skills are too rusty to figure it out.

It's actually not: you missed the pythondev@ part. To access the repository, your SSH key must be added to pythondev's authorized_keys file; it previously wasn't. I have now added your key <something>.comcast.net to the file; I did not add guido@eric, as SSH1 is not supported. Please try again. The list of committers is (now) at http://www.python.org/dev/committers Anybody not on the list who wishes to (and had access to the CVS) please send your key; if you have access to dinsdale, just let us know and we copy your key. Regards, Martin

Brett Cannon wrote:

Why the entire 'peps' directory and not just the trunk like with 'python'? It looks like no tags or branches have ever been created for the PEPs and thus are not really needed.

Right.

I am also curious as to what you would have me check out for the sandbox; whole directory or just the trunk?

You would usually only check out the trunk (unless you want to work on a branch, of course). Regards, Martin

Brett> I have started a svn section in the dev FAQ Brett> (http://www.python.org/dev/devfaq.html) pertaining to checking Brett> out a project from the repository and other stuff discussed so Brett> far. If something is not clear or people feel a step is missing, Brett> let me know. We're starting to look at how much information we can push over to the Wiki. Any pages where multiple people might contribute, especially if they are not the typical website maintainers, seems to me like good Wiki candidates to me. That goes double for anything FAQ-ish. Skip

On Thursday 27 October 2005 23:03, Brett Cannon wrote:

I guess, but I just don't like wikis personally so I have no inclination to make the conversion. If someone wants to make the conversion over to the wiki and keep it up that's fine, but I have no problem keeping the dev FAQ updated like I have for CVS in the past.

And I'm sure we all appreciate your efforts! I certainly do. Regarding using the wiki... I have mixed feelings. Wikis are really, really good for some things. Anything that's "how-to" based on technology (how to use SVN, CVS, etc.) seems like a reasonable candidate, because we get the advantages of peer review. For things that describe policy, I don't think that's so great. For policy (how to use SVN for Python development, because we have certain rules), I think we want to maintain strict editorial control. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org>

Brett Cannon wrote:

I have started a svn section in the dev FAQ (http://www.python.org/dev/devfaq.html) pertaining to checking out a project from the repository and other stuff discussed so far. If something is not clear or people feel a step is missing, let me know.

One think that should be carried over from svn.ht is how to setup Putty on Windows. The issue is that subversion will look for a ssh binary in its path, and if there is none, it fails. Saying [tunnels] ssh="c:/program files/putty/plink.exe" -T in subversion's config file does the trick (see svn.html). If you use a different SSH client, you need to adjust the configuration accordingly. FYI, -T specifies to not allocate a terminal. plink has the nice feature of giving GUI feedback if there is no terminal for interactive feedback (such as whether the remote key is trusted). This makes it useful for TortoiseSVN. Regards, Martin

Thomas Heller <theller@python.net> writes:

Can anyone recommend an XEmacs svn plugin to use - I've tried psvn.el from http://www.xsteve.at/prg/emacs/psvn.el which seems to work?

I've heard http://www.xsteve.at/prg/emacs/psvn.el works :) I also have vc-svn.el installed (I think it's from the subversion source, but it might be part of newer emacs distributions). Cheers, mwh -- <exarkun> INEFFICIENT CAPITALIST YOUR OPULENT TOILET WILL BE YOUR UNDOING -- from Twisted.Quotes

On Fri, 2005-10-28 at 03:53, Thomas Heller wrote:

Can anyone recommend an XEmacs svn plugin to use - I've tried psvn.el from http://www.xsteve.at/prg/emacs/psvn.el which seems to work?

Yep, that's the one I use, albeit a few revs back from what's up there now. It's had some performance problems in the past, but is generally pretty good these days. I've had issues with it bogging down XEmacs /after/ running stat on a very large tree. It seems (seemed?) as though it was still hogging cpu even after the actual back-end svn command was finished. My only other nit is that I wish I could svn stat a few directories at a time. Say I know that only directory A and B are out of date. At the command line I can say "svn stat A B" or "svn commit A B". Can't really do that in psvn.el, but I can understand why that's problematic. I also would love it to be hooked into vc-mode too, for modeline updates and commits of single files. I can understand why those things aren't there yet though. All in all psvn.el works very well, although it's not (for me) a complete replacement for the command line. -Barry