[ python-Bugs-1010952 ] running test_codecmaps_* takes too much effort

SourceForge.net noreply at sourceforge.net
Tue Aug 17 21:19:19 CEST 2004


Bugs item #1010952, was opened at 2004-08-17 21:13
Message generated for change (Comment added) made by ronaldoussoren
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1010952&group_id=5470

Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Ronald Oussoren (ronaldoussoren)
Assigned to: Nobody/Anonymous (nobody)
Summary: running test_codecmaps_* takes too much effort

Initial Comment:
The only way I've found to actually run the codecmap tests is by 
running it over and over again, downloading the missing files when 
a test complains in between, until the tests no longer complains.

E.g 
$ make test
- test_codecmap_jp complains about a missing file
- download this file
$ make test
- test_codecmap_jp complains about another missing filie
- ...

Another problem: it is completely unclear where I should place the 
downloaded files. I've worked around this by placing the files in 
Lib/test and patching test_multibytecodec_support to look for the 
files in os.path.dirname(__file__):

cvs diff: Diffing .
Index: test_multibytecodec_support.py
=========================================
==========================
RCS file: /cvsroot/python/python/dist/src/Lib/test/
test_multibytecodec_support.py,v
retrieving revision 1.5
diff -r1.5 test_multibytecodec_support.py
165a166
>         self.mapfilename = 
os.path.join(os.path.dirname(__file__), self.mapfilename)

It would be nice if there were a document that described what 
should be done to run these tests, adding the required files to CVS 
would be fine too :-)

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

>Comment By: Ronald Oussoren (ronaldoussoren)
Date: 2004-08-17 21:19

Message:
Logged In: YES 
user_id=580910

test_normalization suffers from a simular problem.

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

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


More information about the Python-bugs-list mailing list