| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
svn+ssh://pythondev@svn.python.org/python/trunk
........
r81029 | antoine.pitrou | 2010-05-09 16:46:46 +0200 (dim., 09 mai 2010) | 3 lines
Untabify C files. Will watch buildbots.
........
|
| |
|
|
|
|
|
| |
http://mail.python.org/pipermail/python-dev/2008-June/079988.html
Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names
in the spirit of 3.0 are available via a #define only. See the email thread.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds a new configure argument on OSX:
--with-universal-archs=[32-bit|64-bit|all]
When used with the --enable-universalsdk option this controls which
CPU architectures are includes in the framework. The default is 32-bit,
meaning i386 and ppc. The most useful alternative is 'all', which includes
all 4 CPU architectures supported by MacOS X (i386, ppc, x86_64 and ppc64).
This includes limited support for the Carbon bindings in 64-bit mode as well,
limited because (a) I haven't done extensive testing and (b) a large portion
of the Carbon API's aren't available in 64-bit mode anyway.
I've also duplicated a feature of Apple's build of python: setting the
environment variable 'ARCHFLAGS' controls the '-arch' flags used for building
extensions using distutils.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Cleaned up various things in the toolbox modules.
|
| | |
|
| |
|
|
| |
MacOS9isms.
|
| |
|
|
| |
Untested, but at least it still compiles.
|
| |
|
|
|
| |
- Regenerated with the correct calls to PyType_Ready and the correct
deallocator calls.
|
| |
|
|
|
|
| |
TARGET_API_MAC_OS8 (or !TARGET_API_MAC_CARBON) is gone. Also some
TARGET_API_MAC_OSX conditional code is gone, because it is no longer
used on OSX-only Python (only in MacPython-OS9).
|
| |
|
|
|
|
| |
some of the more compilcated cases (CF, Res) haven't been done yet. Also,
various types should inherit from each other (anything with an as_Resource
method should be a Resource subtype, the CF types should become one family).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
descriptors in stead of manual getattr hooks to get at attributes
of the objects.
For Qd I have in stead gotten rid of most of the attribute access
in favor of the carbon-style accessor methods (with the exception
of visRgn, to be done later), and of the Carbon.Qd.qd global object,
for which accessor functions are also available.
For List I have fixed the fact that various methods were incorrectly
generated as functions.
CF is untouched: PEP252 doesn't allow "poor-mans-inheritance" with
basechain, so it will have to wait for PEP253 support.
|
| |
|
|
| |
for Python 2.2.
|
| |
|
|
|
|
| |
them.
The FutureWarnings are still there, until a way has been found to
say "I know what I'm doing here when I say 0xff000000".
|
| |
|
|
| |
we catch errors during the build process in stead of later during runtime.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
usage is through a wrapper module (without underscore) which lives in the Carbon package.
|
| | |
|
| |
|
|
| |
prototypes. Most toolbox modules now compile, link and import in MacOSX-MachO python.
|
| | |
|
| |
|
|
| |
for Carbon and Classic. The Carbon module is rather empty, though, for now.
|
| | |
|
| |
|
|
|
| |
functions. Include it in stead of duplicating the declarations everywhere. Also
cleaned up toolbox module exports, and got rid of resNotFound error.
|
| | |
|
| | |
|
| |
|
