| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
seems worth keeping.
|
|
|
|
|
|
| |
Unicode string snippets to larger Unicode strings.
This fix should also go into Python 2.2.1.
|
| |
|
|
|
|
| |
for zone hours. Fixes #499169.
|
|
|
|
|
|
| |
Test that the file methods raise ValueError when called on a closed file.
Test .isatty()
Test name, closed attributes
|
|
|
|
| |
test_complex: repair new test's usage of vereq().
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
deepcopy(), _reconstruct(): pass the memo to the other function, so
that recursive data structures built out of new-style objects may be
deeply copied correctly.
2.2.1 bugfix!
|
| |
|
|
|
|
|
| |
Utils.parseaddr('<>') -- i.e. on an empty address, returns the empty
string. Built on rfc822, this used to return None.
|
| |
|
| |
|
| |
|
|
|
|
| |
under regrtest.
|
|
|
|
| |
__safe_for_unpickling__ attribute.
|
|
|
|
| |
instead.
|
|
|
|
|
| |
skipped on Mac OS X. Not sure yet about test_locale.py: this may be
due to my copy of Mac OS X (although it talks english fine enough).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix for SF bug #492345. (I could've sworn I checked this in, but
apparently I didn't!)
This code:
class Classic:
pass
class New(Classic):
__metaclass__ = type
attempts to create a new-style class with only classic bases -- but it
doesn't work right. Attempts to fix it so it works caused problems
elsewhere, so I'm now raising a TypeError in this case.
|
| |
|
|
|
|
| |
tests of complex().
|
|
|
|
|
| |
and only if there is no second arg.
This closes SF patch #479551.
|
| |
|
| |
|
|
|
|
|
| |
on the return values from isleap(). Also checks firstweekday() and
setfirstweekday().
|
| |
|
| |
|
| |
|
|
|
|
| |
(SF patch #491418, #491420, #491421.)
|
|
|
|
| |
callback.
|
|
|
|
|
|
|
|
|
| |
- the repr of unicode. Jython only add the u'' if the string contains char
values > 255.
- A unicode arg to unicode() is perfectly valid in jython.
- A test buffer() test. No buffer() on Jython
This closes patch "[ #490920 ] Jython and test_unicode".
|
|
|
|
| |
This closes patch "[ #490850 ] Jython and test_StringIO".
|
|
|
|
|
|
|
| |
backed out of broken minimal repeat patch from July
also fixed a couple of minor potential resource leaks in pattern_subx
(Guido had already fixed the big one)
|
|
|
|
|
|
| |
module and from string methods.
This closes patch "[ #490811 ] Jython and test_string".
|
|
|
|
|
| |
the output fails to compare correctly for jython. This change was part
of the original patch #403666.
|
|
|
|
|
|
| |
will fix the remaining Jython issues.
This closes patch "[ #490411 ] Jython and test_grammar.py".
|
|
|
|
| |
This closes patch "[ #490414 ] Jython and test_socket".
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
type.__module__ behavior.
This adds the module name and a dot in front of the type name in every
type object initializer, except for built-in types (and those that
already had this). Note that it touches lots of Mac modules -- I have
no way to test these but the changes look right. Apologies if they're
not. This also touches the weakref docs, which contains a sample type
object initializer. It also touches the mmap test output, because the
mmap type's repr is included in that output. It touches object.h to
put the correct description in a comment.
|
|
|
|
|
|
|
|
|
| |
1. Acknowledge the welknown difference that jython
allows continue in the finally clause.
2. Avoid using _testcapi when running with jython.
This closes patch "[ #490417 ] Jython and test_exceptions"
|
|
|
|
|
| |
pickled and we do *not* expect exceptions from either pickle or
cPickle.
|
|
|
|
| |
Don't even try to import _socket when running under Jython.
|
|
|
|
|
|
| |
twice! Fixed this by avoiding the import of test_email, which loads
the module a second time in that situation, and fiddled the __main__
section to resemble other test suites using unittest.
|
|
|
|
| |
This closes patch "[ #490330 ] String format bug in test_b2."
|
|
|
|
| |
so that test_sundry won't fail if the bsddb module is absent.
|
|
|
|
| |
properly set. This fixes that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Big Hammer to implement -Qnew as PEP 238 says it should work (a global
option affecting all instances of "/").
pydebug.h, main.c, pythonrun.c: define a private _Py_QnewFlag flag, true
iff -Qnew is passed on the command line. This should go away (as the
comments say) when true division becomes The Rule. This is
deliberately not exposed to runtime inspection or modification: it's
a one-way one-shot switch to pretend you're using Python 3.
ceval.c: when _Py_QnewFlag is set, treat BINARY_DIVIDE as
BINARY_TRUE_DIVIDE.
test_{descr, generators, zipfile}.py: fiddle so these pass under
-Qnew too. This was just a matter of s!/!//! in test_generators and
test_zipfile. test_descr was trickier, as testbinop() is passed
assumptions that "/" is the same as calling a "__div__" method; put
a temporary hack there to call "__truediv__" instead when the method
name is "__div__" and 1/2 evaluates to 0.5.
Three standard tests still fail under -Qnew (on Windows; somebody
please try the Linux tests with -Qnew too! Linux runs a whole bunch
of tests Windows doesn't):
test_augassign
test_class
test_coercion
I can't stay awake longer to stare at this (be my guest). Offhand
cures weren't obvious, nor was it even obvious that cures are possible
without major hackery.
Question: when -Qnew is in effect, should calls to __div__ magically
change into calls to __truediv__? See "major hackery" at tail end of
last paragraph <wink>.
|
|
|
|
|
| |
the node being added is a fragment node.
This closes SF bug #487929.
|