summaryrefslogtreecommitdiffstats
path: root/Modules/zipimport.c
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove unused variable.Jeremy Hylton2003-07-171-2/+1
|
* Patch #734231: Update RiscOS support. In particular, correctMartin v. Löwis2003-05-101-0/+10
| | | | riscospath.extsep, and use os.extsep throughout.
* tentative fix for #712322: modification time stamp checking failedJust van Rossum2003-04-081-1/+1
| | | | when DST began.
* Make private function and data static.Neal Norwitz2003-03-231-2/+3
|
* use proper constant instead of comment (noted by nnorwitz)Just van Rossum2003-02-281-1/+1
|
* Fix 64-bit problem, ParseTuple("i") needs C ints; ("l") needs C longs.Neal Norwitz2003-02-181-1/+1
| | | | | Use "l" as that *probably* makes more sense (at least to me it does :-) And the test passes on the alpha.
* Use correct function name to PyArg_ParseTuple("is_package").Neal Norwitz2003-02-171-5/+2
| | | | | | | | | | | | 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).
* Fix for bug #661136Just van Rossum2003-01-031-12/+14
| | | | | | | | | | | | | 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-1/+1
| | | | | | | | | | | | | 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.
* removed unused get_short() functionJust van Rossum2002-12-311-14/+0
|
* - added missing decrefJust van Rossum2002-12-311-4/+5
| | | | - whitespace normalization
* Added casts to forestall warnings with MetroWerks.Jack Jansen2002-12-301-4/+4
|
* Squashed compiler wng from MSVC6.Tim Peters2002-12-301-1/+1
|
* Wouldn't compile on Windows; fixed.Tim Peters2002-12-301-1/+1
|
* PEP 302 + zipimport:Just van Rossum2002-12-301-0/+1187
- 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.