This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: WinCVs & Python 2.3
Type: Stage:
Components: None Versions:
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: loewis, rhettinger, ypostgresql
Priority: normal Keywords:

Created on 2003-09-16 16:44 by ypostgresql, last changed 2022-04-10 16:11 by admin. This issue is now closed.

Messages (4)
msg18164 - (view) Author: Partho Bhowmick (ypostgresql) Date: 2003-09-16 16:44
I don't know what changed between Python 2.2.3 & 
Python 2.3 but WinCVS1.3.1 cannot detect Python 2.3, 
though it works fine with Python 2.2.3. Curioulsly, the 
Tcl that comes with Python 2.3 is detected
msg18165 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2003-09-16 19:31
Logged In: YES 
user_id=80475

This may seem obvious but it is worth a try.  See if WinCVS 
has some equivalent of "cvs up -A" which will turn-off the 
sticky flags associated with each file.  The symptoms sound 
like your setup is locked into checking for release22-maint 
when it should be looking for release23-maint (for the most 
current 23) or release23-branch (for the one that went out 
the door).
msg18166 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2003-09-18 18:13
Logged In: YES 
user_id=21627

ypostgresql, can you please elaborate what you mean by
"detect"? In what way can WinCVS detect Python?

If WinCVS has somehow a mechanism to invoke Python, why do
you think you have found a bug in Python, instead of a bug
in WinCVS?
msg18167 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2003-09-27 07:55
Logged In: YES 
user_id=21627

Assuming this is indeed a WinCVS bug, closing it as third-party.
History
Date User Action Args
2022-04-10 16:11:10adminsetgithub: 39237
2003-09-16 16:44:07ypostgresqlcreate