| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Test case for the pty module.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
- fixed parser flag propagation (of all stupid bugs...)
|
| | |
|
| |
|
|
| |
more suitable.
|
| |
|
|
| |
if the multiline flag isn't given.
|
| |
|
|
| |
we want to have GC enabled in the beta.
|
| |
|
|
| |
attempting a recursive import and causing a fatal error.
|
| | |
|
| | |
|
| |
|
|
|
| |
Someone who knows what they are doing needs to replace this with something
that makes sense -- I'm not running Windows right now.
|
| |
|
|
|
|
| |
This'll work fine with 2.0 or 1.5.2, but is less than ideal for
1.6a1/a2. But the code to accomodate 1.6a1/a2 was released with
Distutils 0.9, so it can go away now.
|
| |
|
|
|
|
| |
Regression test for the new winreg.py module.
[Could a Windows person someone please review this?]
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
- removed evil tabs from sre_parse and sre_compile
|
| |
|
|
| |
suggestion from Frank for an example and further explanation.
|
| |
|
|
| |
Change a 1.6 version number used in a an example in a comment to 2.0.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Trent Mick <trentm@activestate.com>:
Fix PC/msvcrtmodule.c and PC/winreg.c for Win64. Basically:
- sizeof(HKEY) > sizeof(long) on Win64, so use PyLong_FromVoidPtr()
instead of PyInt_FromLong() to return HKEY values on Win64
- Check for string overflow of an arbitrary registry value (I know
that ensuring that a registry value does not overflow 2**31 characters
seems ridiculous but it is *possible*).
Closes SourceForge patch #100517.
|
| |
|
|
| |
also, fix type (not caught by Rob Hooft, but could have been :-)
|
| |
|
|
| |
newline in configure --help.
|
| |
|
|
|
|
|
|
|
| |
allows the caller to execute the various tests in pseudo-random order -
default is still to execute tests in the order returned by findtests().
* moved initialization of the various flag variables to the main() function
definition, making it possible to execute regrtest.main() interactively
and still override default behavior.
|
| |
|
|
|
| |
is actually by Fredrik Lundh). This will break the re tests --
Fredrik will fix this before the final release.
|
| |
|
|
|
|
|
|
|
| |
disables it. The gc test is moved to just after the thread test, as
is the wctype-functions test.
Modules/Setup.config is generated instead of Modules/Setup.thread.
Applied SF patch #100684 (loewis) to fix help alignment bug.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The common technique for printing out a pointer has been to cast to a long
and use the "%lx" printf modifier. This is incorrect on Win64 where casting
to a long truncates the pointer. The "%p" formatter should be used instead.
The problem as stated by Tim:
> Unfortunately, the C committee refused to define what %p conversion "looks
> like" -- they explicitly allowed it to be implementation-defined. Older
> versions of Microsoft C even stuck a colon in the middle of the address (in
> the days of segment+offset addressing)!
The result is that the hex value of a pointer will maybe/maybe not have a 0x
prepended to it.
Notes on the patch:
There are two main classes of changes:
- in the various repr() functions that print out pointers
- debugging printf's in the various thread_*.h files (these are why the
patch is large)
Closes SourceForge patch #100505.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes possible overflow in the use of
PyOS_GetLastModificationTime in getmtime.c and Python/import.c.
Currently PyOS_GetLastModificationTime returns a C long. This can
overflow on Win64 where sizeof(time_t) > sizeof(long). Besides it
should logically return a time_t anyway (this patch changes this).
As well, import.c uses PyOS_GetLastModificationTime for .pyc
timestamping. There has been recent discussion about the .pyc header
format on python-dev. This patch adds oveflow checking to import.c so
that an exception will be raised if the modification time
overflows. There are a few other minor 64-bit readiness changes made
to the module as well:
- size_t instead of int or long for function-local buffer and string
length variables
- one buffer overflow check was added (raises an exception on possible
overflow, this overflow chance exists on 32-bit platforms as well), no
other possible buffer overflows existed (from my analysis anyway)
Closes SourceForge patch #100509.
|
| | |
|
| |
|
|
|
| |
Setup.config.in. The latter contains all configure-time selectable
modules; currently thread and gc.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Do not forget to install the xml packages!
|
| | |
|
| | |
|
| |
|
|
| |
as nice. ;)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The common technique for printing out a pointer has been to cast to a long
and use the "%lx" printf modifier. This is incorrect on Win64 where casting
to a long truncates the pointer. The "%p" formatter should be used instead.
The problem as stated by Tim:
> Unfortunately, the C committee refused to define what %p conversion "looks
> like" -- they explicitly allowed it to be implementation-defined. Older
> versions of Microsoft C even stuck a colon in the middle of the address (in
> the days of segment+offset addressing)!
The result is that the hex value of a pointer will maybe/maybe not have a 0x
prepended to it.
Notes on the patch:
There are two main classes of changes:
- in the various repr() functions that print out pointers
- debugging printf's in the various thread_*.h files (these are why the
patch is large)
Closes SourceForge patch #100505.
|
| |
|
|
| |
A previous patch by Jack Jansen was accidently reverted.
|
| |
|
|
|
|
|
| |
- The Tcl minor version should be 3 -- we're now using 8.3.1.
- Remove the version number from yet another Tcl source file.
Note that Tcl should be installed in C:\src\tcl for this to work.
|
| |
|
|
| |
variable...
|
| | |
|
| | |
|
