| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
and also create a symlink "python" pointing to "python$(VERSION)".
Fixes #675745.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
knows about plat-mac subdirectories, and configure adds a variable
EXTRAPLATDIR. These together take care of copying Lib/plat-mac to
the destination on darwin.
Adding plat-mac is still done with a .pth file which is only created when
you do a framework build. I'm not 100% happy with this, but fixing it
really needs a functional pythonw in non-framework builds, and I don't
think I can do that before 2.3a1 (but I'll try:-).
|
|
|
|
| |
window) to a combobox listing the known interpreters.
|
|
|
|
|
| |
normal 2.3 framework install) and MacPython-OSX-$(VERSION) (for the
experimental Jaguar addon install).
|
| |
|
|
|
|
|
|
| |
externally visible difference is that the factory defaults are
now in a plist file in the bundle, in stead of being hard-coded in
the application.
|
| |
|
| |
|
|
|
|
| |
/usr/bin/python.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Apple-installed Python 2.2 from /usr/bin as it's underlying engine.
All the MacPython stuff is installed into /Applications/MacPython-OSX,
and .pth files and other magic are used to tie everything together.
So far only the raw windowing interpreter and BuildApplet work.
|
|
|
|
|
|
| |
IDLE (it was a fatal error before)
- Shuffled a few things around to facilitate the experimental building
of MacPython for Jaguar's pre-installed python.
|
|
|
|
|
|
|
|
|
|
| |
dialogs are now stored in Mac/Lib, and loaded on demand through macresource.
Not only does this simplify a MacPython based on Apple's Python, but
it also makes Mac error codes come out symbolically when running command
line python (if you have Mac/Lib in your path).
The resource files are copied from Mac/Resources. The old ones will disappear
after the OS9 build procedure has been adjusted.
|
| |
|
|
|
|
| |
I modified the patch to make it a non-fatal error if IDLE isn't built.
|
| |
|
|
|
|
| |
rewrapped: as usual with my files everything was far wider than 80 chars.
|
|
|
|
| |
Unfinished.
|
|
|
|
| |
Use the build python for as many things as possible.
|
|
|
|
| |
Tweaks to make builds work for non-standard dstroot.
|
|
|
|
| |
Fix for sh: use : in stead of an empty then clause in an if.
|
|
|
|
|
| |
in stead of 644 (755). This makes a subsequent install fail. Changed
the INSTALL_MODE_FLAG to fix this.
|
|
|
|
|
|
| |
HTML tarball and use it to create a documentation tree readable and
searchable with Apple Help Viewer. The documentation also shows up in
Project Builder (if you add Python.framework to your project).
|
|
|
|
|
|
| |
in Python.app, and refer to it in Info.plist. This makes Apple Help
Viewer recognize the Python documentation.
- Changed the externally visible name of Python.app to "Python" (was PythonW).
|
|
|
|
|
| |
unix cvs. In this case the resource files are actual resource files
in stead of AppleSingle encoded files.
|
| |
|
|
|
|
|
| |
- Pre-cache .rsrc files in Mac subtree after installing
- Fixed nameclash in Make variables
|
|
|
|
|
|
|
|
|
| |
the framework, the MacOSX apps and the unix tools.
Most of the hard work is done by Mac/OSX/Makefile.
Also, it should now be possible to install in a different directory,
such as /tmp/dist/Library/Frameworks, for building binary installers.
The fink crowd wanted this.
|
| |
|
| |
|
| |
|
|
|
|
| |
etc. Still not enough, probably, but better than what we had.
|
| |
|
|
|
|
| |
surprises later (the IDE won't work without waste).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
actual script to run in case we are running from an applet. If we are indeed
running an applet we skip the normal option processing leaving it all to the
applet code.
This allows us to get use the normal python binary in the Python.app bundle,
giving us all the normal command line options through PythonLauncher while
still allowing Python.app to be used as the template for building applets.
Consequently, pythonforbundle is gone, and Mac/Python/macmain.c isn't used
on OSX anymore.
|
|
|
|
|
|
|
| |
be invoked by PythonLauncher when needed.
Also changed the names of various variables in the Makefile to match
what the main Makefile has.
|
|
|
|
| |
dragging or double-clicking the script.
|
|
|
|
| |
- Build PythonLauncher.app and PythonIDE.app as well as Python.app.
|
| |
|
|
|
|
| |
optimal, especially if Terminal wasn't running yet, but it works.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
doubleclicks a .py, .pyw or .pyc file. It runs the file by invoking the
relevant interpreter (either the command line Python in a terminal window
or a Python.app for GUI-based scripts). Interpreter to use and the options
to pass are settable through preferences.
If PythonLauncher wasn't running it does its thing for one script and exits.
If it was manually started before a dialog is presented where the user
can set the options to use, etc.
To be done:
- option-drag/doubleclick should always open the interactive dialog
- Terminal-window isn't done yet
- Should be reimplemented in Python, but pyobjc isn't part of the core.
- Various menu entries should be disabled.
|
|
|
|
|
|
| |
which uses a .pth file to add the Mac/Lib from your source tree to sys.path.
Also put the Python version number in a variable.Killed by signal 2.
|
|
|
|
|
|
|
|
|
| |
OSX framework build process. Things fixed/modified:
- the filesystem case-sensitivity test now works for builds outside
the source directory
- various other fixes for building outside the source directory
- python.app now has a target in the main Makefile
- WASTE and AquaTk are found more automatically
|
|
|
|
| |
and maintain. Fixes #557482.
|
| |
|
| |
|