| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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
|
|
|
|
|
|
|
| |
builtin_eval wasn't merging in the compiler flags from the current frame;
I suppose we never noticed this before because future division is the
first future-feature that can affect expressions (nested_scopes and
generators had only statement-level effects).
|
|
|
|
|
| |
#449043 supporting __future__ in simulated shells
which implements PEP 264.
|
| |
|
| |
|
|
|
|
| |
given and the path is gleaned from the uu header.
|
|
|
|
|
|
|
|
|
| |
specified in the uu header already exists. No additional
workaround is provided since out_file=pathname is a deprecated
interface, so it is better to simply pass a file-like object into
out_file anyway. This closes SF bug #438083.
Use isinstance() tests instead of type comparisons.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
#449043 supporting __future__ in simulated shells
in support of PEP 264.
Much has changed from the patch version:
+ Repaired bad hex constant for nested_scopes.
+ Defined symbolic CO_xxx names so global search will find these uses.
+ Made the exported list of feature names explicit, instead of abusing
__all__ for this purpose (and redefined __all__ accordingly).
+ Added gross .compiler_flag verification to test___future__.py, and
reworked it a little to make use of the newly exported explicit list
of feature names.
|
|
|
|
|
|
|
|
|
|
| |
is pickled as a global must now exist by the name under which it is
pickled, otherwise the pickling fails. Previously, such things would
fail on unpickling, or unpickle as the wrong global object. I'm
hoping that this won't break existing code that is playing tricks with
this.
I need a volunteer to do this for cPickle too.
|
|
|
|
|
|
|
|
| |
- Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled
- check for Py_USING_UNICODE in all places that use Unicode functions
- disables unicode literals, and the builtin functions
- add the types.StringTypes list
- remove Unicode literals from most tests.
|
|
|
|
|
|
|
|
| |
expression. This is needed for certain servers that (in violation of
the standard) don't return the parentheses in the response.
This fixes SF bug #441712 by Henrik Weber (not exactly using his
patch).
|
|
|
|
| |
class has a correct repr().
|
|
|
|
|
|
| |
when an unbound method of class A is stored as a class variable of
class B, and class B is *not* a subclass of class A, that method
should *not* get bound to B instances.
|
| |
|
|
|
|
|
| |
subclasses type, one that doesn't (the latter isn't fully functional
yet).
|
|
|
|
| |
really long. Closes SF bug #437984.
|
|
|
|
|
|
|
| |
assigned to a class variable and then accessed via an instance, it
should not be rebound.
test_descr.py:methods(): test for the condition above.
|
|
|
|
| |
I have no way of testing this.
|
| |
|
| |
|