| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
unchanged (and sys.gettotalrefcount() remains constant).
Fix a few typos.
|
|
|
|
|
|
|
|
|
| |
[ 784825 ] fix obscure crash in descriptor handling
Should be applied to release23-maint and in all likelyhood
release22-maint, too.
Certainly doesn't apply to release21-maint.
|
| |
|
|
|
|
| |
UnicodeTranslateError message.
|
|
|
|
|
| |
If there is only one bad character it will now be printed in a
form that is a valid Python string.
|
| |
|
|
|
|
|
|
| |
under Cygwin. The attached patch corrects this problem.
I tested this patch under Red Hat Linux 8.0 too.
|
|
|
|
|
|
| |
time.daylight is true. Add an explicit test for this situation.
Fixed some wording in docstrings.
|
|
|
|
|
|
|
| |
The default seed is time.time().
Multiplied by 256 before truncating so that fractional seconds are used.
This way, two successive calls to random.seed() are much more likely
to produce different sequences.
|
| |
|
|
|
|
| |
which can now take zero arguments.
|
| |
|
|
|
|
| |
Include a test case that failed for one of my efforts to repair this.
|
|
|
|
| |
Will also check in on the 2.3 branch.
|
| |
|
|
|
|
| |
(From SF patch #543867)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also remove now unnecessary property attributes for thread safety
(no longer have lazy attributes) and code simplicity reasons.
Timezone storage has been reworked to be simpler and more flexible. All values
in LocaleTime instances are lower-cased. This is all done to simplify the
module.
The module now assumes nothing beyond the strptime function will be exposed for
general use beyond providing functionality for strptime.
|
| |
|
| |
|
|
|
|
| |
see how much of the file was not covered by the build process
|
|
|
|
| |
by returning an empty list instead of raising a TypeError.
|
|
|
|
|
|
| |
caught when executing test_strptime, test_logging, and test_time in that order
when the testing of "%c" occured. Suspect the cache was not being recreated
(the test passed when test_logging was forced to re-establish the locale).
|
| |
|
|
|
|
|
| |
all I know, the original locale may be '' (I don't think that's possible,
but ...), and if so we would certainly want to restore it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Obtain the original locale in the documented way. This way actually
works for me.
Restore the original locale at the end, instead of forcing to "C".
Move the locale fiddling into the test driver instead of doing it as a
side effect of merely importing the module. I don't know why the test
is mucking with locale (and also added a comment saying so), but it
surely has no justification for doing that as an import side-effect.
Now whenever the locale-changing code executes, the locale-restoring code
will also get run.
|
| |
|
|
|
|
| |
This patch just adds test_ioctl to the list of expected skips for Cygwin.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
If some other test comes along and uses mimetypes, it will be
initialized from the system files.
|
|
|
|
|
|
| |
If this doesn't happen, it leaves the locale in a state that can cause
other tests to fail. For example, running test_strptime,
test_logging, and test_time in that order.
|
| |
|
|
|
|
|
| |
unittest environment. Since his extension finds docstrings in private
functions, it exposed a bug in the difflib doctests.
|
| |
|
|
|
|
| |
encoding. Use sys.getfilesystemencoding().
|
|
|
|
| |
doctests.
|
|
|
|
|
| |
Checking // would call floor division but did not test that
true division had become the default with 'from __future__ import division'.
|
|
|
|
|
| |
Checking // would call floor division but did not test that
true division had become the default with 'from __future__ import division'.
|
|
|
|
| |
Bug fix candidate.
|
| |
|
|
|
|
|
|
| |
- wrap some long lines
- shorten others
- fix indentation
|
|
|
|
|
|
|
| |
closing idempotent (it used to raise a nuisance exception on the 2nd
close attempt).
Bugfix candidate? Probably, but arguable.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* It ran fine under "python regrtest.py test_warnings" but failed under
"python regrtest.py" presumably because other tests would add to
filtered warnings and not reset them at the end of the test.
* Converted to a unittest format for better control. Renamed
monkey() and unmonkey() to setUp() and tearDown().
* Increased coverage by testing all warnings in __builtin__.
* Increased coverage by testing regex matching of specific messages.
|
|
|
|
|
|
| |
reported consistently with the *nix world. 'Lib/test/test_warnings.py'
came out as 'lib\test\test_warnings.py'. The basename is all we care
about so I used that.
|
| |
|
|
|
|
|
|
|
|
|
| |
Add API function simplefilter() that does not create or install
regular expressions to match message or module. Extend the filters
data structure to store None as an alternative to re.compile("").
Move the _test() function to test_warnings and add some code to try
and avoid disturbing the global state of the warnings module.
|
| |
|
| |
|
| |
|