Mailman 3 July 2000 - Python-Dev

Windows vs SourceForge (was RE: [Python-Dev] Just spotted on SourceForge main page)
by Tim Peters July 4, 2000

July 4, 2000

[Tim] > The great thing about all the instructions I've found so far is > that they're written by people who apparently have no real understanding > of how the underlying components (and/or Windows) work. [an anonymous Guido replied in pvt] > That was not my impression of Andy's instructions. They were to the > point and effective. Yes, they certainly *looked* that way <wink>. I didn't mean to slander Andy! His instructions didn't work for me, but then nobody else's … [View More]did either, and I've increasingly suspected it's because I've got so many half-broken SSH, CVS, and WinCVS installations on this machine fighting each other. So, without an imminent release busting my homeless balls, I decided to take the time to start over from scratch: + Ran an official uninstaller for everything that left one behind (only WinCVS). + Manually tracked down all the crap WinCVS left behind in the registry anyway, and deleted it. + Deleted all the ssh and cvs .exe's on machine. + Got the crap out of my autoexec.bat (I'm running Win98SE) that various packages had inserted there (I *think* this stuff was left behind by the SourceForge setup tool). + Deleted all the .ssh directories on my machine (and found some in surprising places! e.g., one was hiding under "\My Documents"(!)). + Got rid of an absurd \etc directory (again suspect the SF setup tool, although several goofy sets of instructions demanded you create one of these). + Nuked my entire Python tree. + Rebooted. + Did a full tape backup of the machine <wink -- but I've had it with this junk>. + Retrieved Andy Robinson's instructions and tried them again. Worked great! I'll attach a modified version below, where I filled in blanks and repaired (just a few) typos as I went along. This should get you a functional Windows cmdline CVS running with SourceForge, and I don't want a GUI version anyway. If there's anything here that isn't crystal clear or doesn't work, gripe at me, not Andy ... all's-well-that-ends-ly y'rs - tim Setting up a cmdline CVS to work with SourceForge under Windows --------------------------------------------------------------- 28-Jun-2000 Original by Andy Robinson (andy(a)reportlab.com) 03-Jul-2000 Modified by Tim Peters (tim_one(a)msn.com) 1. Get ftp.reportlab.com/tools/cvs-1.10-win.zip ftp.reportlab.com/tools/ssh-1.2.14-win32bin.zip (copied from somewhere obscure for safety, I forget where) 2. Unzip these to a location on your path. Type 'cvs' and 'ssh' from somewhere else to verify. 3. Choose where to keep your CVS projects; let's assume C:\Code 4. Create a subdirectory C:\Code\.ssh (yes, dot-ssh) 5. (see #8 for an alternative) Create two environment variables: HOME=C:\Code CVS_RSH=ssh HOME must point to the directory above your .ssh directory. On Win9x, this can be done in a batch file or autoexec.bat; e.g., set HOME=c:\Code set CVS_RSH=ssh Run the batch file, or reboot if you're using autoexec.bat. On NT or 2000, go to Control Panel | System | Environment and set them at either user or machine level. 6. If not done so, get a Sourceforge account and a project you can log in to. 7. Teach SSH about your project's home, by doing ssh -l $USERNAME $MYPROJECT.sourceforge.net where $USERNAME is your SourceForge login name and $MYPROJECT your SourceForge project name. You'll see Host "$MYPROJECT.sourceforge.net" added to the list of known hosts. and then Creating random seed file ~/.ssh/random_seed. This may take a while. After a while it will prompt for a password. Type your SourceForge password and hit ENTER. After some SourceForge msgs scroll by, you'll be left at a SourceForge shell prompt. Type exit and hit ENTER. Now you're back at the DOS prompt. 8. You will need either a lengthy command line or a batch file for each sourceforge project. I set cvsroot in a batch file in my 'c:\code' directory, and have one such file for each CVS project I use (about ten of them!): set CVSROOT=:ext:$USERNAME@cvs.$MYPROJECT.sourceforge.net:/cvsroot/$DIRNAME where $USERNAME and $MYPROJECT are again your SourceForge login and project names, and $DIRNAME is the top-level directory in the SourceForge CVS tree; a project can have several, but usually there is just one. Note: you can keep HOME and CVS_SSH out of your permanent environment (see #5) by adding those definitions to this batch file instead. 9. Execute this batch file. You can now go to C:\Code and do cvs -z7 checkout $MYPROJECT (z7 means 'compress network traffic', handy over dialup lines) 10. From now on, just use CVS normally, running this batch file first each time you bring up a DOS box you're going to use for CVS work. Note that you'll be asked for your password each time you enter a CVS command. I wouldn't survive without Karl Fogel's book "Open Source Development with CVS", Coriolis Press. The CVS reference material (about 225 printed pages!) from this book is available for free download from http://cvsbook.red-bean.com/ Footnote: for anonymous checkout, I think you just omit the 'my_user_name@' part from the CVSROOT variable. I hope this helps; let me know if people have any problems with the instructions. - Andy Robinson ReportLab [View Less]

1 0

Copyright notice
by Martin v. Loewis July 4, 2000

July 4, 2000

On startup, the current CVS python reports (on my system) Python 2.0b1 (#31, Jul 1 2000, 23:13:39) [GCC 2.95.2 19991024 (release)] on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam Copyright 1995-2000 Corporation for National Research Initiatives (CNRI) Now that the file copyrights are changed, I expect this message to change as well. May I suggest that, instead of adding another line, the two last lines of this message are removed? People who need to find out who … [View More]

6 6

Just spotted on SourceForge main page
by Greg Ward July 3, 2000

July 3, 2000

Maybe this is what all you Windows folks are looking for. SFSetup v1 released mhearn - 06/28/00 11:00 - SourceForge Setup for Win32 SFSetup is a program to automatically setup SSH and WinCVS for SourceForge projects under the Windows 32 platform. It's now available for download so if you have not yet set up SSH and WinCVS and want it done for you, you can use this program. Go to sfsetup.sourceforge.net to find out how to use it. It's open source and written in Delphi - … [View More]

3 2

Re: [Python-Dev] Test results of linuxaudiodev.c
by Michael Hudson July 3, 2000

July 3, 2000

Ka-Ping Yee <pingster(a)ilm.com> writes: > On Thu, 29 Jun 2000, Ka-Ping Yee wrote: > > Try setting the environment variable AUDIODEV to /dev/audio > > before running the test script. Does that work any better? > > Even if that works, i realize that's not the way the interface > was intended to be used. To play an AU file, the routine should > look something like this (not tested, as i don't have a working > Linux box)... [snip] Yup, that works fine. Don'… [View More]

4 3

unicode alphanumerics
by Fredrik Lundh July 3, 2000

July 3, 2000

when looking through skip's coverage listing, I noted a bug in SRE: #define SRE_UNI_IS_ALNUM(ch) ((ch) < 256 ? isalnum((ch)) : 0) this predicate is used for \w when a pattern is compiled using the "unicode locale" (flag U), and should definitely not use 8-bit locale stuff. however, there's no such thing as a Py_UNICODE_ISALNUM (or even a Py_UNICODE_ISALPHA). what should I do? how about using: Py_UNICODE_ISLOWER || Py_UNICODE_ISUPPER || Py_UNICODE_ISTITLE || Py_UNICODE_ISDIGIT </F>

3 6

Minidom and Unicode
by Martin v. Loewis July 3, 2000

July 3, 2000

While trying the minidom parser from the current CVS, I found that repr apparently does not work for nodes: Python 2.0b1 (#29, Jun 30 2000, 10:48:11) [GCC 2.95.2 19991024 (release)] on linux2 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam Copyright 1995-2000 Corporation for National Research Initiatives (CNRI) >>> from xml.dom.minidom import parse >>> d=parse("/usr/src/python/Doc/tools/sgmlconv/conversion.xml") >>> d.childNodes [Traceback (most recent … [View More]

5 16

FYI: Perl Unicode Handling HOWTO
by Fredrik Lundh July 3, 2000

July 3, 2000

for the curious: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-07/msg00004.html </F>

1 0

Typo in pty.py
by Phillip Porch July 3, 2000

July 3, 2000

I was compiling and testing the current snapshot of python (current as of 7:00 AM CDT 7/3/00) and found that test_pty failed. Here is the output of the test. [sco root-tty01 src] ./python Lib/test/test_pty.py Calling master_open() Got master_fd '6', slave_name '/dev/ttyp1' Calling slave_open('/dev/ttyp1') Got slave_fd '7' Writing to slave_fd I wish to buy a fish license. For my pet fish, Eric. calling pty.fork() Traceback (most recent call last): File "Lib/test/test_pty.py", line 50, in ? … [View More]

1 0

test coverage summaries - now updated nightly
by Skip Montanaro July 3, 2000

July 3, 2000

I've spent amount as much time on generating automated statement and branch coverage as I can afford for the next few days. At this point I think I have it generating a reasonable facsimile of useful output. A cron job on www.musi-cal.com does the following early each morning (4:45AM Pacific time): make clean cvs update config.status --recheck make python with gcov flags make test > testresults.txt generate coverage pages (lines.html & branches.html) The … [View More]

5 9

(harmless?) CVS error on SourceForge
by Tim Peters July 3, 2000

July 3, 2000

Recent commit had an error msg at the end; don't remember enough about CVS to recall whether it matters; anyone else? C:\pysrc>cvs commit python/dist/src/PC/example_nt CVS.EXE commit: Examining python/dist/src/PC/example_nt Password: Checking in python/dist/src/PC/example_nt/example.dsp; /cvsroot/python/python/dist/src/PC/example_nt/example.dsp,v <-- example.dsp new revision: 1.3; previous revision: 1.2 done Checking in python/dist/src/PC/example_nt/example.dsw; /cvsroot/python/python/… [View More]

2 1