| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
The fact that this was failing and went unnoticed so long seems like a good argument for being able to enable and disble py3kwarnings through Python.
|
| | |
|
| |
|
|
| |
Thanks to Wummel for the patch
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
to lookup properties declared in base classes. Looking at it I'm not sure
what the official scope if the property codes is, maybe it is only the
(OSA) class in which they are used. But giving them global scope hasn't been
a problem so far.
Regenerated the standard suites, which are now also space-indented.
|
| | |
|
| |
|
|
|
| |
which sometimes seems to result in different terminology. It does
seem to be mostly compatible, though.
|
| |
|
|
|
|
| |
This is a first step towards regenerating the modules with newer, MacOSX,
versions of these programs, and using the programmatic interface to
get at the terminology in stead of poking in resource files.
|
| | |
|
|
|
in MacPython-OS9 and MacPython-OSX (or the equivalent unix Python on
Mac OS X). The only items remaining in Mac/Lib are modules that are
meaningful only for MacPython-OS9 (CFM stuff, MacPython preferences
in resources, etc).
|
