summaryrefslogtreecommitdiffstats
path: root/PC/getpathp.c
Commit message (Collapse)AuthorAgeFilesLines
...
* Trent Mick: familiar simple Win64 patchesGuido van Rossum2000-06-281-7/+6
|
* Patch from M.-A. Lemburg:Jeremy Hylton2000-05-261-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Python on UNIX now trusts PYTHONHOME unconditionally Modules/getpath.c: Landmark changed to os.py. Setting PYTHONHOME now unconditionally sets sys.prefix (and sys.exec_prefix). No further checks are done whether the standard lib can be found in that location or not. This is in sync with the PC subdir getpath implementations. PC/getpathp.c: Landmark changed to os.py. PC/os2vacpp/getpathp.c: Landmark changed to os.py. Note: BAW's checkin on exceptions.c eliminates earlier concerns about a bogus PYTHONHOME value leading to a core dump. Instead it causes a useless sys.path and prevents imports.
* Revamped path access again, by Mark Hammond, to be more robust in theGuido van Rossum2000-03-301-91/+193
| | | | | | | | | | | light of three different situations: (1) running from build; (2) running from installed; (3) running without being able to find an installation (e.g. as a COM object). The system paths in the repository are only used for (3); the path deduced from the installation location are used otherwise. PYTHONHOME overrides in all cases. Read the comments for more details.
* Changes to completely ignore the registry when it detects that you areGuido van Rossum2000-03-291-25/+30
| | | | | | running out of the build directory. This means that it will no longer try to use an older version of the library when an older version has been installed.
* Back out of a recent policy change (Mark Hammond disagreed).Guido van Rossum1998-08-111-27/+8
| | | | The registry always comes first and the default is always appended.
* Sigh. More restructuring was needed.Guido van Rossum1998-08-081-27/+57
| | | | | Make an explicit test for whether the prefix is in fact the source directory, and then don't use the registry.
* This file's previous log message is bogus. The real change is thatGuido van Rossum1998-08-081-1/+1
| | | | | when it gets the path from the registry, it no longer appends the default path to the end (which would mostly be a duplication).
* Different version games:Guido van Rossum1998-08-081-9/+16
| | | | | | | - MS_DLL_ID is now set to "1.5" instead of "1.5.x" so Mark Hammond's extensions won't have to be changed. - FILEVERSION and PRODUCTVERSION are set to 1,5,2,1. (The last number could be the build# or the alpha release# or so.)
* Two changes:Guido van Rossum1998-07-271-3/+15
| | | | | | (1) Use Py_GetPythonHome() instead of getenv("PYTHONHOME"); (2) Mark Hammond's patch to search for .pyc/.pyo landmark as well.
* Fix some outdated comments (mostly by removing a large comment blockGuido van Rossum1998-02-191-16/+11
| | | | | that was only causing confusing). Add free(userpath) and free(machinepath) statements to prevent some leaks.
* Allocate one byte extra in some cases.Guido van Rossum1997-12-111-1/+1
|
* Seem to be some changes related to DLL version from string resource,Guido van Rossum1997-09-291-2/+19
| | | | again (Mark Hammond is the cause of all this).
* Much rewritten. Added Win32 registry stuff (from getpath_nt.c, whichGuido van Rossum1997-08-131-55/+222
| | | | | | | is now obsolete), and changed the default path calculations. $PYTHONPATH is now added as a prefix (like it's always been on Unix); $PYTHONHOME takes precedence over the program pathname; and only one landmark is needed.
* Some changes to make it work on NT; add the directory where the binaryGuido van Rossum1997-08-131-2/+9
| | | | | | | | lives to the end of the path. (Still to do: add $PYTHONPATH to the front instead of using it as is; add the Win32 registry paths as in getpath_nt.c (which can then retire).)
* Jim Ahlstrom's contributions for DOS, OS/2, WIN3.1.Guido van Rossum1997-05-191-0/+294
generated by cgit v0.12 at 2024-10-20 23:48:05 (GMT)