| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This closes SF bug #458785.
|
|
|
|
| |
Fixes bug reported as SF bug #453728.
|
|
|
|
|
| |
less hostile to newbie use at the interactive prompt.
This is in response to SF bug #458654.
|
|
|
|
| |
Add refcount information for other recently documented APIs.
|
| |
|
|
|
|
|
| |
statement that this is a proof-of-concept meant for people to
experiment with, nothing more.
|
|
|
|
| |
in Python.
|
| |
|
|
|
|
| |
headers. This is the final checkin for SF bug #458768.
|
| |
|
|
|
|
| |
Python/C style guide.
|
|
|
|
|
|
|
|
| |
(1) Allow multiple -u options to extend each other (and the initial
value of use_resources passed into regrtest.main()).
(2) When a test is run stand-alone (not via regrtest.py), needed
resources are always granted.
|
| |
|
|
|
|
| |
This closes SF bug #458771.
|
|
|
|
| |
Based on a patch by Skip Montanaro, this closes SF bug #458885.
|
|
|
|
| |
This covers regression on SF bug #458860.
|
|
|
|
| |
This closes SF bug #458860.
|
|
|
|
| |
support.
|
| |
|
|
|
|
|
|
| |
added all the telnet options known to arpa/telnet.h
added all the options registered with IANA as of today
added the possibility for the user to have it's own option negotiation callback
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch is similar to that proposed by Jeremy. The proposed patch altered
the interface of TestResult such that it would be passed the error
information as a string rather than an exc_info() tuple.
The implemented change leaves the interface untouched so that TestResults
are still passed the tracebacks, but stor them in stringified form for
later reporting.
Notes:
- Custom subclasses of TestResult written by users should be unaffected.
- The existing 'unittestgui.py' will still work with this module after the
change.
- Support can later be added to pop into the debugger when an error occurs;
this support should be added to a TestRunner rather than to TestCase itself,
which this change will enable.
(Jeremy, Fred, Guido: Thanks for all the feedback)
|
|
|
|
| |
instead.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1. That seeking beyond the end of a file increases the size of a file.
2. That files so extended are magically filled with null bytes.
I find no support for either in the C std, and #2 in particular turns out
not to be true on Win32 (you apparently see whatever trash happened to be
on disk). Left #1 intact, but changed the test to check only bytes it
explicitly wrote. Also fiddled the "expected" vs "got" failure reports
to consistently use repr (%r) -- they weren't readable otherwise.
|
|
|
|
|
|
|
|
|
| |
Curious: the MS docs say stati64 etc are supported even on Win95, but
Win95 doesn't support a filesystem that allows partitions > 2 Gb.
test_largefile: This was opening its test file in text mode. I have no
idea how that worked under Win64, but it sure needs binary mode on Win98.
BTW, on Win98 test_largefile runs quickly (under a second).
|
| |
|
| |
|
|
|
|
|
|
| |
While not even documented, they were clearly part of the C API,
there's no great difficulty to support them, and it has the cool
effect of not requiring any changes to ExtensionClass.c.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
requires that errno ever get set, and it looks like glibc is already
playing that game. New rules:
+ Never use HUGE_VAL. Use the new Py_HUGE_VAL instead.
+ Never believe errno. If overflow is the only thing you're interested in,
use the new Py_OVERFLOWED(x) macro. If you're interested in any libm
errors, use the new Py_SET_ERANGE_IF_OVERFLOW(x) macro, which attempts
to set errno the way C89 said it worked.
Unfortunately, none of these are reliable, but they work on Windows and I
*expect* under glibc too.
|
|
|
|
|
|
| |
fullblown OSX application. It is starting to work, but building
the application bundle is still handwork, and we need a minimal
readme file too.
|
|
|
|
|
|
|
|
|
|
| |
fullblown drag and drop application. To my surprise it is starting
to work already: Python actually executes a script dropped on it.
To be done:
- Make sure this still works in MacPython
- Don't lose argv[0] in the process
- Applet support
|
| |
|
|
|
|
|
|
| |
32 characters per component. This makes mkdir() calls and such fail with EINVAL.
For now I am disabling the test on the Mac, and I'll open a bugreport.
|
| |
|
|
|
|
|
|
| |
that provide a somewhat more uniform interface to getting values.
This is from SF patch #453691.
|
|
|
|
| |
Fix up docstring for itemconfigure.
|
| |
|
|
|
|
|
|
| |
I don't know what difference it makes, but '/' indeed makes less sense
as an include dir than '.', so I'm changing the default. Just so I
can close the bug. ;-)
|
|
|
|
| |
date.
|
|
|
|
| |
order. Add breaks in SYNOPSIS.
|
| |
|
|
|
|
|
| |
Patch by Jim Ahlstrom which lets java's zipfile classes read zipfiles
create by zipfile.py.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I believe this works on Linux (tested both on a system with large file
support and one without it), and it may work on Solaris 2.7.
The changes are twofold:
(1) The configure script now boldly tries to set the two symbols that
are recommended (for Solaris and Linux), and then tries a test
script that does some simple seeking without writing.
(2) The _portable_{fseek,ftell} functions are a little more systematic
in how they try the different large file support options: first
try fseeko/ftello, but only if off_t is large; then try
fseek64/ftell64; then try hacking with fgetpos/fsetpos.
I'm keeping my fingers crossed. The meaning of the
HAVE_LARGEFILE_SUPPORT macro is not at all clear.
I'll see if I can get it to work on Windows as well.
|
| |
|