| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
are satisfied in a case-insensitive manner, the attempt to import (the
non-existent) fcntl gets satisfied by FCNTL.py instead, and the tempfile
module defines a Unix-specific _set_cloexec() function in that case. As
a result, temp files can't be created then (blows up with an AttributeError
trying to reference fcntl.fcntl). This just popped up in the spambayes
project, where there is no apparent workaround (which is why I'm pushing
this in now).
|
|
|
|
| |
may cause some tests to fail but it prevents them from hanging.
|
|
|
|
|
| |
Pimp crashed if you tried to install a non-installable package, in stead
of printing a decent error message. Fixes #773450..
|
|
|
|
| |
setting of sCursor happened in an assert.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
problems with the tests
|
|
|
|
| |
I tested against VC 7.0 and it caused no problems there.
|
|
|
|
|
|
|
|
|
|
|
|
| |
skip over functions with private names (as indicated by the underscore
naming convention). The old default created too much of a risk that
user tests were being skipped inadvertently. Note, this change could
break code in the unlikely case that someone had intentionally put
failing tests in the docstrings of private functions. The breakage
is easily fixable by specifying the old behavior when calling testmod()
or Tester(). The more likely case is that the silent failure was
unintended and that the user needed to be informed so the test could be
fixed.
|
|
|
|
|
| |
unittest environment. Since his extension finds docstrings in private
functions, it exposed a bug in the difflib doctests.
|
|
|
|
|
| |
Note, these tests were not getting exercised because
doctest skips over private functions.
|
| |
|
|
|
|
| |
encoding. Use sys.getfilesystemencoding().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Extensions must still be configured manually and there is currently one
set of extension key bindings for all platforms.
Bring NEWS.txt up to date.
Update CREDITS.txt and idlever.py for release.
M NEWS.txt
M config-extensions.def
M extend.txt
M help.txt
M idlever.py
|
|
|
|
| |
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
|
|
|
|
| |
database corruption problems with Spambayes.
|
|
|
|
|
|
|
| |
(contributed by Vincent Delft.)
The script updated os.environ but failed to pass the whole environment
to the child process (the CGI script).
|
|
|
|
|
|
|
| |
closing idempotent (it used to raise a nuisance exception on the 2nd
close attempt).
Bugfix candidate? Probably, but arguable.
|
|
|
|
| |
(Contributed by George Yoshida.)
|
| |
|
|
|
|
| |
Needs to be backported to both IDLE and IDLEFORK.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
|
|
|
|
|
| |
Related to SF patch 723231 (which pointed out the problem, but didn't
fix it, just shut up the warning msg -- which was pointing out a dead-
serious bug!).
Bugfix candidate.
|
| |
|
|
|
|
| |
Usability fix. Makes the error message more helpful.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
databases are associated with corruption problems, so I studied this code
carefully and ran some brutal stress tests. I didn't find any bugs,
although it's unclear whether this code *intends* that __setitem__ can
leave the directory file out of synch with the data file (so
if a dumbdbm isn't properly closed, and the value of an existing key
was ever replaced, corruption is almost certain, where "corruption"
means the directory file is out of synch with the data file).
Added many comments and generally modernized the code. Examples of the
latter: we have better ways of reading a whole file line-by-line now;
eval() now tolerates a trailing newline; the %r format code can be used
to avoid explicit repr/backtick calls; and the code often broke tuples
into their components when it was clearer and faster to just leave them
as tuples.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At this point, the problem appears particular to the OS/2 EMX port of
gdbm (which is at v1.7.3) - this combination produces a .pag file but
no .dir file.
A more sophisticated patch which checks magic numbers when dbm.library
indicates that dbm is linked to gdbm, and there is no .dir file, is
still attached to the above patch entry for reconsideration after 2.3
is released.
This checkin applies a workaround specific to the known failure case.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
until now: the inheritance of default values was the wrong way around.
This caused app bundles to get a type of "BNDL" instead of "APPL".
Apparently this is not a problem until you try to drag your app to
the dock.
----------------------------------------------------------------------
|