| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
tailoring for universal builds by factoring out common OS X-specific
customizations from sysconfig, distutils.sysconfig, distutils.util,
and distutils.unixccompiler into a new module _osx_support that can
eventually also be used by packaging.
|
|
|
|
|
|
| |
- fix test_distutils and test_sysconfig test failures by
aligning sysconfig and distutils.sysconfig tailoring of
configure variables (as in 2.7)
|
|
|
|
|
|
| |
for host compiler.
Add NEWS entry, rename _PROJECT_BASE to _PYTHON_PROJECT_BASE.
|
|
|
|
| |
for host compiler.
|
|
|
|
| |
plain tuple to a collections.namedtuple.
|
|
|
|
|
|
|
| |
We need a discussion to define what should be customized how; this new
config file is premature. It was added to serve the needs of the
resources system in install_data / packaging.database, so it can be
removed alongside packaging for 3.3.
|
|
|
|
|
|
| |
Distutils2 will live on on PyPI and be included in the stdlib when it
is ready. See discussion starting at
http://mail.python.org/pipermail/python-dev/2012-June/120430.html
|
| |
|
|
|
|
| |
python-dev.
|
| |
|
|\
| |
| |
| | |
Solaris, distutils doesn't include bitness in the directory name
|
| |
| |
| |
| | |
distutils doesn't include bitness in the directory name
|
|\ \
| |/
| |
| | |
distutils doesn't include bitness in the directory name
|
| |
| |
| |
| | |
distutils doesn't include bitness in the directory name
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
when imported, instead doing it at build time. This makes importing
sysconfig faster and reduces Python startup time by 20%.
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Also remove outdated and unhelpful docstrings in test_sysconfig.
|
|\ \ \
| |/ /
|/| /
| |/ |
handle correctly references to "bogus variable" (e.g. "prefix=$/opt/python").
|
| |
| |
| |
| | |
correctly references to "bogus variable" (e.g. "prefix=$/opt/python").
|
|/ |
|
|
|
|
|
|
|
|
|
| |
in shell.
Without this patch python will fail to start properly when the environment
variable MACOSX_DEPLOYMENT_TARGET is set on MacOSX and has a value that is
not compatible with the value during Python's build. This is caused by code
in sysconfig that was only meant to be used in disutils.
|
|
|
|
|
| |
The other one is in a finally block not seen in the diff, which I added
in 3bf86785cd9c (for #10252).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
handler to parse the Makefile file. Avoid a UnicodeDecodeError if the source
code directory name contains a non-ASCII character and the locale encoding is
ASCII.
|
| |
|
|
|
|
| |
current directory was deleted.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is wrong when PY_LDFLAGS is not empty.
The bug was caused by LDSHARED getting expanded *before* sysconfig
renamed PY_LDSHARED (and simular values) to names without a PY_
prefix.
The patch tries to maintain the intended behaviour of allowing users
to set LDFLAGS in the environment and have that affect the build.
Without this patch a universal build on OSX cannot build universal
(fat binary) extensions.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
configure to append to Python's default values for those variables, and
similarly allow users to set $XXFLAGS on the make command line to append to the
values set by configure.
In the makefile, this renames the variables that used to be $XXFLAGS to
$PY_XXFLAGS, and renames the old $PY_CFLAGS to $PY_CORE_CFLAGS. To compensate,
sysconfig now aliases $XXFLAGS=$PY_XXFLAGS so that scripts using it keep
working. I see that as the right interface, not a backward-compatibility hack,
since these are logically the $XXFLAGS variables; we just use a different name
in the makefile to deal with make's semantics.
|
| |
|
|
|
|
|
|
| |
will fail when builddir != srcdir (that is, when you
run configure in a directory that is not the top of
the source tree).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
svn+ssh://pythondev@svn.python.org/python/trunk
........
r81371 | tarek.ziade | 2010-05-20 00:20:14 +0200 (Thu, 20 May 2010) | 1 line
#8759: Fixed user paths in sysconfig for posix and os2 schemes
........
|
|
|
|
|
|
|
|
|
|
|
|
| |
svn+ssh://pythondev@svn.python.org/python/trunk
........
r80967 | ronald.oussoren | 2010-05-08 12:29:06 +0200 (Sat, 08 May 2010) | 4 lines
Issue #8084: ensure that the --user directory
conforms to platforms standars on OSX when
using a python framework.
........
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
svn+ssh://pythondev@svn.python.org/python/trunk
........
r78835 | victor.stinner | 2010-03-11 13:34:39 +0100 (jeu., 11 mars 2010) | 7 lines
Issue #7774: Set sys.executable to an empty string if argv[0] has been
set to an non existent program name and Python is unable to retrieve the real
program name.
Fix also sysconfig: if sys.executable is an empty string, use the current
working directory.
........
r78836 | victor.stinner | 2010-03-11 14:27:35 +0100 (jeu., 11 mars 2010) | 4 lines
Fix test_executable introduce in previous commit (r78835): Windows is able to
retrieve the absolute Python path even if argv[0] has been set to a non
existent program name.
........
r78837 | victor.stinner | 2010-03-11 14:46:06 +0100 (jeu., 11 mars 2010) | 3 lines
Another fix to test_executable() of test_sys: set the current working to avoid
the #7774 bug.
........
|
|
|
|
|
|
|
|
|
|
| |
svn+ssh://pythondev@svn.python.org/python/trunk
........
r78833 | florent.xicluna | 2010-03-11 02:50:48 +0100 (jeu, 11 mar 2010) | 2 lines
Revert r78830: realpath() should really be applied to sys.executable.
........
|