summaryrefslogtreecommitdiffstats
path: root/Lib
Commit message (Collapse)AuthorAgeFilesLines
* Fix for issue 9164Ronald Oussoren2010-07-111-2/+1
|
* Stricter verification for file based url scheme and reliance on ftp protocol.Senthil Kumaran2010-07-112-1/+5
|
* ValueError is eventually what we want to move to, I supposeBenjamin Peterson2010-07-101-2/+2
|
* Fix error message for comparing single line strings in ↵Michael Foord2010-07-102-3/+23
| | | | | | unittest.TestCase.assertEqual. Issue 9174.
* Fix 'refleak' introduced by fnmatch cache purge tests.R. David Murray2010-07-102-2/+11
| | | | | This introduces a 'purge' function for the fnmatch module analogous to the 'purge' function in the re module.
* #1434090: properly append child in expatbuilder doctype handler.Georg Brandl2010-07-101-1/+1
|
* #3071: tell how many values were expected when unpacking too many.Georg Brandl2010-07-101-3/+3
|
* Oops. Fix distutils tests that r82746 broke.Jeffrey Yasskin2010-07-091-1/+3
|
* be more robust across platformsBenjamin Peterson2010-07-091-1/+1
|
* remove SocketIO.__del__; close() can handle itBenjamin Peterson2010-07-091-4/+0
|
* Issue #9189: Allow users to set $CFLAGS, $CPPFLAGS, and $LDFLAGS when runningJeffrey Yasskin2010-07-091-0/+5
| | | | | | | | | | | | | configure to append to Python's default values for those variables, and similarly allow users to set $XXFLAGS on the make command line to append to the values set by configure. In the makefile, this renames the variables that used to be $XXFLAGS to $PY_XXFLAGS, and renames the old $PY_CFLAGS to $PY_CORE_CFLAGS. To compensate, sysconfig now aliases $XXFLAGS=$PY_XXFLAGS so that scripts using it keep working. I see that as the right interface, not a backward-compatibility hack, since these are logically the $XXFLAGS variables; we just use a different name in the makefile to deal with make's semantics.
* Re-flow several long lines from #1578269.Brian Curtin2010-07-095-11/+18
|
* Fix the breakage of Lib/tarfile.py on non-Windows platforms due toBrian Curtin2010-07-092-6/+15
| | | | | | | | | using WindowsError in a try/except. Only add WindowsError to the list of exceptions to catch when we are actually running on Windows. Additionally, add a call that was left out in test_posixpath. Thanks Amaury, Antoine, and Jason.
* wrapBenjamin Peterson2010-07-091-1/+2
|
* allow more exceptionsBenjamin Peterson2010-07-091-3/+3
|
* OverflowError is fineBenjamin Peterson2010-07-091-1/+2
|
* 7846: limit fnmatch pattern cache to _MAXCACHE=100 entries.R. David Murray2010-07-092-1/+19
| | | | Patch by Andrew Clegg.
* use assert methodBenjamin Peterson2010-07-091-1/+1
|
* fix repr of complicated structseqs #9206Benjamin Peterson2010-07-081-1/+9
|
* assert tuple inheritanceBenjamin Peterson2010-07-081-0/+1
|
* Undo inadvertant checkin.Brian Curtin2010-07-081-1/+1
|
* Implement #1578269. Patch by Jason R. Coombs.Brian Curtin2010-07-0813-253/+609
| | | | | | | | | | | | | | | | Added Windows support for os.symlink when run on Windows 6.0 or greater, aka Vista. Previous Windows versions will raise NotImplementedError when trying to symlink. Includes numerous test updates and additions to test_os, including a symlink_support module because of the fact that privilege escalation is required in order to run the tests to ensure that the user is able to create symlinks. By default, accounts do not have the required privilege, so the escalation code will have to be exposed later (or documented on how to do so). I'll be following up with that work next. Note that the tests use ctypes, which was agreed on during the PyCon language summit.
* Issue #9136: Profiling Decimal gave 'dictionary changed size during iteration'.Mark Dickinson2010-07-081-13/+31
| | | | Remove the use of locals() that caused this error.
* Fix misplaced exactness check that was causing unnecessary work in ↵Mark Dickinson2010-07-081-3/+4
| | | | Decimal.__pow__.
* Fix a performance issue in Decimal.pow. Thanks Stefan Krah for finding this.Mark Dickinson2010-07-082-6/+21
|
* Issue #8605: Skip test_gdb if Python is compiled with optimizations.Antoine Pitrou2010-07-081-0/+10
|
* In test_decimal, convert heuristic for skipping tests into an explicit skiplist.Mark Dickinson2010-07-081-41/+35
|
* ValueError in this case is also acceptableBenjamin Peterson2010-07-071-4/+8
|
* don't ignore exceptions from PyObject_IsTrueBenjamin Peterson2010-07-071-0/+6
|
* this needn't be in the loopBenjamin Peterson2010-07-071-2/+2
|
* Issue #9186: log1p(-1.0) should raise ValueError, not OverflowError.Mark Dickinson2010-07-072-8/+72
|
* Issue #9000: datetime.timezone objects now have eval-friendly repr.Alexander Belopolsky2010-07-061-0/+9
|
* Fix test_xmlrpc_net to no longer fail since there are no more buildbots for ↵Brett Cannon2010-07-051-1/+1
| | | | trunk.
* Added two more test cases for datetimeAlexander Belopolsky2010-07-051-0/+6
|
* looking up on the type is correct, so this isn't an XXXBenjamin Peterson2010-07-051-7/+0
|
* Added more tests for utctimetuple()Alexander Belopolsky2010-07-051-1/+21
|
* pydoc still has a silly encodingBenjamin Peterson2010-07-051-1/+1
|
* Revert -r82559; it's not clear that this is the right thing to do, and the ↵Mark Dickinson2010-07-041-2/+3
| | | | change obscures the original intentions.
* Re-encode shlex.py in UTF-8, and remove coding cookie.Mark Dickinson2010-07-041-3/+2
|
* Remove coding cookie from heapq.py.Mark Dickinson2010-07-041-3/+1
|
* Issue #9130: Validate ellipsis tokens in relative imports.Mark Dickinson2010-07-041-0/+6
|
* Fix symbol numbers in test_parser test.Mark Dickinson2010-07-041-8/+8
|
* Issue #9130: Fix validation of relative imports in parser module.Mark Dickinson2010-07-041-0/+20
|
* Issue #9118: help(None) will now return NoneType doc instead ofAlexander Belopolsky2010-07-041-2/+3
| | | | starting interactive help.
* Merged revisions 81478,82530-82531 via svnmerge fromBenjamin Peterson2010-07-042-2/+9
| | | | | | | | | | | | | | | | | | svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r81478 | benjamin.peterson | 2010-05-22 13:47:39 -0500 (Sat, 22 May 2010) | 1 line ensure doctests have some future_features ........ r82530 | benjamin.peterson | 2010-07-04 11:11:41 -0500 (Sun, 04 Jul 2010) | 1 line simplify ignore star imports from itertools #8892 ........ r82531 | benjamin.peterson | 2010-07-04 11:13:20 -0500 (Sun, 04 Jul 2010) | 1 line wrap with parenthesis not \ ........
* Issue #9128: Fix validation of class decorators in parser module.Mark Dickinson2010-07-041-0/+7
|
* Make importlib.abc.SourceLoader the primary mechanism for importlib.Brett Cannon2010-07-032-27/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This required moving the class from importlib/abc.py into importlib/_bootstrap.py and jiggering some code to work better with the class. This included changing how the file finder worked to better meet import semantics. This also led to fixing importlib to handle the empty string from sys.path as import currently does (and making me wish we didn't support that instead just required people to insert '.' instead to represent cwd). It also required making the new set_data abstractmethod create any needed subdirectories implicitly thanks to __pycache__ (it was either this or grow the SourceLoader ABC to gain an 'exists' method and either a mkdir method or have set_data with no data arg mean to create a directory). Lastly, as an optimization the file loaders cache the file path where the finder found something to use for loading (this is thanks to having a sourceless loader separate from the source loader to simplify the code and cut out stat calls). Unfortunately test_runpy assumed a loader would always work for a module, even if you changed from underneath it what it was expected to work with. By simply dropping the previous loader in test_runpy so the proper loader can be returned by the finder fixed the failure. At this point importlib deviates from import on two points: 1. The exception raised when trying to import a file is different (import does an explicit file check to print a special message, importlib just says the path cannot be imported as if it was just some module name). 2. the co_filename on a code object is not being set to where bytecode was actually loaded from instead of where the marshalled code object originally came from (a solution for this has already been agreed upon on python-dev but has not been implemented yet; issue8611).
* Make importlib.abc.SourceLoader the primary mechanism for importlib.Brett Cannon2010-07-033-1/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This required moving the class from importlib/abc.py into importlib/_bootstrap.py and jiggering some code to work better with the class. This included changing how the file finder worked to better meet import semantics. This also led to fixing importlib to handle the empty string from sys.path as import currently does (and making me wish we didn't support that instead just required people to insert '.' instead to represent cwd). It also required making the new set_data abstractmethod create any needed subdirectories implicitly thanks to __pycache__ (it was either this or grow the SourceLoader ABC to gain an 'exists' method and either a mkdir method or have set_data with no data arg mean to create a directory). Lastly, as an optimization the file loaders cache the file path where the finder found something to use for loading (this is thanks to having a sourceless loader separate from the source loader to simplify the code and cut out stat calls). Unfortunately test_runpy assumed a loader would always work for a module, even if you changed from underneath it what it was expected to work with. By simply dropping the previous loader in test_runpy so the proper loader can be returned by the finder fixed the failure. At this point importlib deviates from import on two points: 1. The exception raised when trying to import a file is different (import does an explicit file check to print a special message, importlib just says the path cannot be imported as if it was just some module name). 2. the co_filename on a code object is not being set to where bytecode was actually loaded from instead of where the marshalled code object originally came from (a solution for this has already been agreed upon on python-dev but has not been implemented yet; issue8611).
* Fix a spelling mistake in a comment.Brett Cannon2010-07-031-1/+1
|
* Make importlib.abc.SourceLoader the primary mechanism for importlib.Brett Cannon2010-07-0316-542/+415
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This required moving the class from importlib/abc.py into importlib/_bootstrap.py and jiggering some code to work better with the class. This included changing how the file finder worked to better meet import semantics. This also led to fixing importlib to handle the empty string from sys.path as import currently does (and making me wish we didn't support that instead just required people to insert '.' instead to represent cwd). It also required making the new set_data abstractmethod create any needed subdirectories implicitly thanks to __pycache__ (it was either this or grow the SourceLoader ABC to gain an 'exists' method and either a mkdir method or have set_data with no data arg mean to create a directory). Lastly, as an optimization the file loaders cache the file path where the finder found something to use for loading (this is thanks to having a sourceless loader separate from the source loader to simplify the code and cut out stat calls). Unfortunately test_runpy assumed a loader would always work for a module, even if you changed from underneath it what it was expected to work with. By simply dropping the previous loader in test_runpy so the proper loader can be returned by the finder fixed the failure. At this point importlib deviates from import on two points: 1. The exception raised when trying to import a file is different (import does an explicit file check to print a special message, importlib just says the path cannot be imported as if it was just some module name). 2. the co_filename on a code object is not being set to where bytecode was actually loaded from instead of where the marshalled code object originally came from (a solution for this has already been agreed upon on python-dev but has not been implemented yet; issue8611).
generated by cgit v0.12 at 2025-03-12 02:47:35 (GMT)