delta/cpython-git.git/Modules/getpath.c, branch v2.5.4 github.com: python/cpython.git Patch #1516912: improve Modules support for OpenVMS. 2006-07-10T01:18:57+00:00 Neal Norwitz nnorwitz@gmail.com 2006-07-10T01:18:57+00:00 2a30cd0ef0673710a1a4e188b50c11026c403b2a 






spread the extern "C" { } magic pixie dust around. Python itself builds now
2006-04-13T02:06:09+00:00

Anthony Baxter
anthonybaxter@gmail.com

2006-04-13T02:06:09+00:00

ac6bd46d5c30f4e643120aeef1ccd531801a2181

using a C++ compiler. Still lots and lots of errors in the modules built by
setup.py, and a bunch of warnings from g++ in the core.





using a C++ compiler. Still lots and lots of errors in the modules built by
setup.py, and a bunch of warnings from g++ in the core.







Some more changes to make code compile under a C++ compiler.
2006-04-11T12:14:09+00:00

Anthony Baxter
anthonybaxter@gmail.com

2006-04-11T12:14:09+00:00

64182fe0b39870d30b08da54696c4d02e7b52bc5












Patch #931938: prevent setting sys.prefix to ""
2006-02-20T17:37:36+00:00

Georg Brandl
georg@python.org

2006-02-20T17:37:36+00:00

e393bf6fe30acff8168d78a09661453046aadec1












squash compiler warning on Mac OSX 10.3
2006-01-05T10:49:13+00:00

Skip Montanaro
skip@pobox.com

2006-01-05T10:49:13+00:00

2b47445234bd44b1382cc434c408a390eb4aa07e












Change type on variable to silence gcc 4 warning.  Call signature was found at
2005-09-16T02:43:35+00:00

Brett Cannon
bcannon@gmail.com

2005-09-16T02:43:35+00:00

bd9c3f702825a82e0ac8fbcc2cdc40364de6747f

http://darwinsource.opendarwin.org/10.4.2/dyld-43.1/src/dyldAPIs.cpp .





http://darwinsource.opendarwin.org/10.4.2/dyld-43.1/src/dyldAPIs.cpp .







Bug 1003471: Python 1.5.2 security vulnerability still present in 2.3.4
2004-08-08T01:00:47+00:00

Tim Peters
tim.peters@gmail.com

2004-08-08T01:00:47+00:00

ec8c5a931136b61231b295f2aded8dc04035e9b7

That's the title of the report, but the hole was probably plugged since
Python 2.0.  See corresponding checkin to PC/getpathp.c:  a crucial
precondition for joinpath() was neither documented nor verified, and there
are so many callers with so many conditional paths that no "eyeball
analysis" is satisfactory.  Now Python dies with a fatal error if the
precondition isn't satisfied, instead of allowing a buffer overrun.

NOT TESTED!  The Windows version of the patch was, but not this one.  I
don't feel like waiting for someone to notice the patch I attached to the
bug report.  If it doesn't compile, sorry, but fix it <wink>.  If it
does compile, it's "obviously correct".





That's the title of the report, but the hole was probably plugged since
Python 2.0.  See corresponding checkin to PC/getpathp.c:  a crucial
precondition for joinpath() was neither documented nor verified, and there
are so many callers with so many conditional paths that no "eyeball
analysis" is satisfactory.  Now Python dies with a fatal error if the
precondition isn't satisfied, instead of allowing a buffer overrun.

NOT TESTED!  The Windows version of the patch was, but not this one.  I
don't feel like waiting for someone to notice the patch I attached to the
bug report.  If it doesn't compile, sorry, but fix it <wink>.  If it
does compile, it's "obviously correct".







Modules/getpath.c now compiles properly under OS X when using the
2004-06-26T04:03:06+00:00

Brett Cannon
bcannon@gmail.com

2004-06-26T04:03:06+00:00

f6af76da61fcbd9e6f0d43dcbd236864e12ec334

--disable-framework build; header file was protected in an #if using the wrong
macro to check.

Closes bug #978645.





--disable-framework build; header file was protected in an #if using the wrong
macro to check.

Closes bug #978645.







Change comment from C++ style to C.
2004-06-24T00:48:44+00:00

Brett Cannon
bcannon@gmail.com

2004-06-24T00:48:44+00:00

6cc48148fe0ecd600f796031ecfd16813f7f0d1e












Fix for #932977: MacOSX does not pass the whole pathname in argv[0] for
2004-06-03T14:33:03+00:00

Jack Jansen
jack.jansen@cwi.nl

2004-06-03T14:33:03+00:00

1afd4807d9b3df5ba24fa245920d677497025722

#!-scripts, only the filename part, and this can lead to incorrect
initialization of sys.path and sys.executable if there is another python
on $PATH before the one used in #!.

The fix was picked up from the darwinports crowd, thanks!





#!-scripts, only the filename part, and this can lead to incorrect
initialization of sys.path and sys.executable if there is another python
on $PATH before the one used in #!.

The fix was picked up from the darwinports crowd, thanks!