| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
compiler-flag argument).
|
| |
|
| |
|
| |
|
|
|
|
| |
for urllib.
|
|
|
|
|
| |
__future__.py reverted to 1.9.
newmodule.c reverted to 2.32.
|
| |
|
| |
|
|
|
|
|
| |
Added tests for boundary cases in magical PEP 237 int->long auto-overflow,
but nothing here addresses the rest of the bug report so left it open.
|
|
|
|
|
|
| |
modules and extensions on Windows is now $PREFIX/Lib/site-packages.
Includes backwards compatibility code for pre-2.2 Pythons. Contributed
by Paul Moore.
|
| |
|
| |
|
|
|
|
|
| |
DateTime constructor. use ServerProxy instead of Server in sample
code.
|
| |
|
|
|
|
| |
ftp urls.
|
|
|
|
| |
or you will break something:-)
|
|
|
|
| |
SchedParams() method, and there's no need to call it anyway.
|
|
|
|
| |
OverflowError test succeed.
|
|
|
|
|
|
|
|
| |
python -Wdefault
or
python -Wdefault::OverflowWarning
|
|
|
|
| |
level to 2.2a2+
|
|
|
|
|
|
|
|
|
|
| |
- file URL now starts with "file://" (standard) rather than "file:"
- new optional argument 'context' to enable()
- repeated variable names don't have their values shown twice
- dotted attributes are shown; missing attributes handled reasonably
- highlight the whole logical line even if it has multiple physical lines
- use nice generator interface to tokenize
- formatting fixed so that it looks good in lynx, links, and w3m too
|
|
|
|
| |
However, this is only enabled with regrtest's --use=network switch.
|
|
|
|
| |
tests should be run.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
flag, which specifies external or resource intensive tests to
perform. This is used by test_largefile and test_socket_ssl.
-u/--use takes a comma separated list of flags, currently supported:
largefile, network.
usage(): New function. Note that the semantics of main() have changed
slightly; instead of returning an error code, it raises a
SystemExit (via sys.exit()) with the given error code.
main(): use_large_resources => use_resources
Also, added support for long-option alternative to the short
options.
_expectations: Added test_socket_ssl to the list of expectedly skipped
tests.
|
|
|
|
|
|
|
|
| |
requires(): New function which can be used to `assert' that a specific
-u/--use resource flag is present. Raises a TestSkipped if not.
This is used in test_largefile and test_socket_ssl to enable
external or resource consumptive tests that are normally
disabled.
|
| |
|
|
|
|
|
|
|
| |
to stdout. Repaired by not printing at all except in verbose mode.
Made the test about 6x faster -- envelope analysis showed it took time
proportional to the square of the # of tasks. Now it's linear.
|
|
|
|
|
|
|
|
| |
module has to deal with "class" HTML-as-deployed as well as XHTML, so we
cannot be as strict as XHTML allows.
This closes SF bug #453059, but uses a different fix than suggested in
the bug comments.
|
|
|
|
| |
a module.
|
|
|
|
|
| |
Add test case to cover multiple future statements on separate lines of
a module.
|
|
|
|
| |
pass these tests.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
code. grrr...
|
|
|
|
| |
reported by Greg Ball on python-dev.
|
|
|
|
|
| |
443614. I will submit a new feature request and patch to threading.py and
libthreading.tex to address the bounded semaphore issue.
|
|
|
|
|
| |
class, I came up with an even simpler solution: raise the error in
__getattr__().
|
|
|
|
|
|
|
|
|
|
| |
right way"). Fiddle __future__.py to use them.
Jeremy's pyassem.py may also want to use them (by-hand duplication of
magic numbers is brittle), but leaving that to his judgment.
Beef up __future__'s test to verify the exported feature names appear
correct.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
For the HTTPS class (when available), ensure that the x509 certificate data
gets passed through to the HTTPSConnection class. Create a new
HTTPS.__init__ to do this, and refactor the HTTP.__init__ into a new _setup
method for both init's to call.
Note: this is solved differently from the patch, which advocated a new
**x509 parameter on the base HTTPConnection class. But that would open
HTTPConnection to arbitrary (ignored) parameters, so was not as desirable.
|
|
|
|
| |
Entries taken from the standard Debian mime.types file.
|
|
|
|
| |
A few enhancements are pending, but this should work reliably.
|
|
|
|
|
| |
This breaks software that excepts a socket.error but not an
AttributeError.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
somewhat less horrid hack <wink>: if a module does
from __future__ import X
then the module dict D is left in a state such that (viewing X as a
string)
D[X] is getattr(__future__, X)
So by examining D for all the names of future features, and making that
test for each, we can make a darned good guess as to which future-features
were imported by the module. The appropriate flags are then sucked out
of the __future__ module, and passed on to compile()'s new optional
arguments (PEP 264).
Also gave doctest a meaningful __all__, removed the history of changes
(CVS serves that purpose now), and removed the __version__ vrbl (similarly;
before CVS, it was a reasonable clue, but not anymore).
|
|
|
|
| |
Fix Module() handler to avoid including the doc string in the AST
|