[ python-Bugs-764447 ] cvs update warnings

SourceForge.net noreply at sourceforge.net
Sun Oct 8 00:44:06 CEST 2006


Bugs item #764447, was opened at 2003-07-02 00:56
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=764447&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Macintosh
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Sjoerd Mullender (sjoerd)
Assigned to: Just van Rossum (jvr)
Summary: cvs update warnings

Initial Comment:
On Windows, when you do "cvs update" in the "Mac/IDE
scripts" directory, you get the following warnings
(example uses Cygwin, but it also happens with other
CVS clients):

$ cd "Mac/IDE scripts"; cvs update
? Hold option to open a script
? Insert file name
? Insert folder name
? Search Python Documentation
? Hack/Remove .pyc files
? Hack/Toolbox Assistant
cvs server: Updating .
cvs server: Updating Hack
cvs server: Updating Widget demos
$

This is due to the fact that Windows can't deal with
periods at the end of file names.  All files giving
warnings end in "...".  These periods are removed when
the files get created, and so CVS sees the files
without periods and complains about them.

At one level the solution is simple: rename those
files.  At another level, I don't know what the
consequences are for the Mac, so assigning to Just
(Jack doesn't seem to want to deal with this :-)


----------------------------------------------------------------------

>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-10-07 15:44

Message:
Logged In: YES 
user_id=33168

Mac/IDE scripts is gone, so is CVS.  :-)

----------------------------------------------------------------------

Comment By: Nick Coghlan (ncoghlan)
Date: 2004-07-04 20:46

Message:
Logged In: YES 
user_id=1038590

The leading spaces on some filenames are causing Eclipse to
choke on the checkout, too (I'm guessing the spaces are
there to get the right sequencing of the filenames).

One possibility that would give a minimal change is to
prepend and append underscores to all of the filenames, then
modify the code that reads these files to remove the first
and last character before performing the same parsing it
does now.

----------------------------------------------------------------------

Comment By: Sjoerd Mullender (sjoerd)
Date: 2003-09-09 07:12

Message:
Logged In: YES 
user_id=43607

It's now past 2.3 final, so can you look into this again?

----------------------------------------------------------------------

Comment By: Sjoerd Mullender (sjoerd)
Date: 2003-07-02 03:36

Message:
Logged In: YES 
user_id=43607

I've lived with this for years.  A few more weeks won't matter.

----------------------------------------------------------------------

Comment By: Just van Rossum (jvr)
Date: 2003-07-02 02:33

Message:
Logged In: YES 
user_id=92689

Any objections to postponing this to after 2.3 final? The thing is, 
currently these file names map to menu items directly, and to fix 
this I have to build a way to specify the menu item from within 
the file. This will cause way more changes than I'm comfortable 
with, just before 2.3. Removing the spaces from folder names can 
be done at the same time.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=764447&group_id=5470


More information about the Python-bugs-list mailing list