cpython/Mac/PythonLauncher/main.m

//
//  main.m
//  PythonLauncher
//
//  Created by Jack Jansen on Fri Jul 19 2002.
//  Copyright (c) 2002 __MyCompanyName__. All rights reserved.
//

#import <Cocoa/Cocoa.h>
#include <unistd.h>

int main(int argc, const char *argv[])
{
    char *home = getenv("HOME");
    if (home) chdir(home);
    return NSApplicationMain(argc, argv);
}
First stab at the launcher application. This will be run when the user 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. 2002-07-29 21:36:35 +00:00			`//`
			`// main.m`
			`// PythonLauncher`
			`//`
			`// Created by Jack Jansen on Fri Jul 19 2002.`
			`// Copyright (c) 2002 __MyCompanyName__. All rights reserved.`
			`//`

			`#import <Cocoa/Cocoa.h>`
On startup, attempt to set the working directory to $HOME. Fixes #913581. 2004-06-03 14:15:50 +00:00			`#include <unistd.h>`
First stab at the launcher application. This will be run when the user 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. 2002-07-29 21:36:35 +00:00
			`int main(int argc, const char *argv[])`
			`{`
Issue #18377: Code cleanup in Python Launcher This changeset fixes a number of compiler warnings in the Python Launcher binary for OSX. It also cleans up whitespace usage in those sources. 2013-07-07 09:53:08 +02:00			`char *home = getenv("HOME");`
			`if (home) chdir(home);`
First stab at the launcher application. This will be run when the user 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. 2002-07-29 21:36:35 +00:00			`return NSApplicationMain(argc, argv);`
			`}`