summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_zipimport.py
Commit message (Collapse)AuthorAgeFilesLines
* Fix for [ 765456 ]: testAFakeZlib failed on platforms that use aJust van Rossum2003-11-181-0/+7
| | | | | statically linked zlib module, but since the problem it tests can't exist on these systems, simply skip it then. Will backport.
* Change the zipimport implementation to accept files containingThomas Heller2003-07-221-1/+20
| | | | | | | | | arbitrary bytes before the actual zip compatible archive. Zipfiles containing comments at the end of the file are still not supported. Add a testcase to test_zipimport, and update NEWS. This closes sf #775637 and sf #669036.
* Patch #734231: Update RiscOS support. In particular, correctMartin v. Löwis2003-05-101-1/+1
| | | | riscospath.extsep, and use os.extsep throughout.
* Combine the functionality of test_support.run_unittest()Walter Dörwald2003-05-011-2/+4
| | | | | | | | | | and test_support.run_classtests() into run_unittest() and use it wherever possible. Also don't use "from test.test_support import ...", but "from test import test_support" in a few spots. From SF patch #662807.
* Whitespace normalization.Tim Peters2003-02-191-5/+5
|
* Use correct function name to PyArg_ParseTuple("is_package").Neal Norwitz2003-02-171-1/+4
| | | | | | | | | | | | Fix off-by-1 error in normalize_line_endings(): when *p == '\0' the NUL was copied into q and q was auto-incremented, the loop was broken out of, then a newline was appended followed by a NUL. So the function, in effect, was strcpy() but added two extra chars which was caught by obmalloc in debug mode, since there was only room for 1 additional newline. Get test working under regrtest (added test_main).
* cleaned up Jack's Mac OS9 changesJust van Rossum2003-01-091-5/+1
|
* Various tweaks to make the test work on the Mac.Jack Jansen2003-01-081-3/+12
|
* Fix for bug #661136Just van Rossum2003-01-031-3/+8
| | | | | | | | | | | | | Lesson learned: kids should not be allowed to use API's starting with an underscore :-/ zipimport in 2.3a1 is even more broken than I thought: I attemped to _PyString_Resize a string created by PyString_FromStringAndSize, which fails for strings with length 0 or 1 since the latter returns an interned string in those cases. This would cause a SystemError with empty source files (and no matching pyc) in the zip archive. I rewrote the offending code to simply allocate a new buffer and avoid _PyString_Resize altogether. Added a test that would've caught the problem.
* Ugh, zipimport is virtually broken in 2.3a1 :-( It worked by accident inJust van Rossum2003-01-021-4/+5
| | | | | | | | | | | | | the test set as it only tested with a zip archive in the current directory, but it doesn't work at all for packages when the zip archive was specified as an absolute path. It's a real embarrassing bug: a strchr call should have been strrchr; fever apparently implies dyslexia. Second stupid bug: the zipimport test failed with a name error __importer__ (which I had renamed to __loader__ everywhere but here). I would've sworn I ran the test after that change but that can't be true. What I don't understand that noone reported a failing test_zipimport.py before the release of 2.3a1.
* PEP 302 + zipimport:Just van Rossum2002-12-301-0/+180
- new import hooks in import.c, exposed in the sys module - new module called 'zipimport' - various changes to allow bootstrapping from zip files I hope I didn't break the Windows build (or anything else for that matter), but then again, it's been sitting on sf long enough... Regarding the latest discussions on python-dev: zipimport sets pkg.__path__ as specified in PEP 273, and likewise, sys.path item such as /path/to/Archive.zip/subdir/ are supported again.