| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Also move all _PyMalloc_XXX entry points into obmalloc.c.
The Windows build works fine.
The Unix build is changed here (Makefile.pre.in), but not tested.
No other platform's build process has been fiddled.
|
|
|
|
|
|
| |
Use posixly correct sort args.
Bugfix candidate.
|
|
|
|
|
| |
- Create the Python.framework/Versions/$(VERSION) dir if it doesn't exist
- Override existing symlinks in the framework.
|
|
|
|
| |
2.2.1 candidate.
|
|
|
|
|
| |
extension, not the EXT one, as regen uses the python binary in the build
directory. Fixes #493959.
|
|
|
|
|
| |
as OSX HFS+) and if so add an extension to the python executable, but
only in the build directory, not on the installed python.
|
| |
|
|
|
|
| |
own interfered with including Python.h. Remove Python's assert.h.
|
|
|
|
| |
pass. Closes SF # 485080
|
|
|
|
| |
Fixes #485679.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
1. configure doesn't handle HP-UX release numbers
(e.g., B.11.00), resulting in MACHDEP = "hpuxB".
2. After checking for wchar.h, configure doesn't
include it when checking the size of wchar_t.
(Python 2.2b1 on HP-UX 11.00)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a big one, touching lots of files. Some of the platforms
aren't tested yet. Briefly, this changes the return value of the
os/posix functions stat(), fstat(), statvfs(), fstatvfs(), and the
time functions localtime(), gmtime(), and strptime() from tuples into
pseudo-sequences. When accessed as a sequence, they behave exactly as
before. But they also have attributes like st_mtime or tm_year. The
stat return value, moreover, has a few platform-specific attributes
that are not available through the sequence interface (because
everybody expects the sequence to have a fixed length, these couldn't
be added there). If your platform's struct stat doesn't define
st_blksize, st_blocks or st_rdev, they won't be accessible from Python
either.
(Still missing is a documentation update.)
|
|
|
|
|
| |
Add --install-scripts=$(BINDIR) argument to "setup.py install"
invocation.
|
| |
|
|
|
|
|
| |
Jeremy had seen the warning but not realized what he should do about
it. Add the hint "Usually, copying Setup.dist to Setup will work."
|
| |
|
|
|
|
|
|
| |
structmember.h, which was missing (and caused me a snide comment by
Tim when he fixed something I missed because of the missed dependency
:-).
|
|
|
|
|
|
|
| |
its normally chatty nature.
(This completes a side project to make "make -s" truly silent unless
errors occur.)
|
|
|
|
| |
Older make's can apparently choke on this.
|
| |
|
|
|
|
|
|
|
|
| |
it may depend on. It's really annoying that thread.o doesn't get
rebuilt when the .h file is changed! :-)
The dependency is on *all* the Python/thread_*.h files -- that should
be sufficient and rarely cause unneeded recompilations.
|
|
|
|
| |
Bill Fancher found this one.
|
|
|
|
|
|
|
|
| |
- Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled
- check for Py_USING_UNICODE in all places that use Unicode functions
- disables unicode literals, and the builtin functions
- add the types.StringTypes list
- remove Unicode literals from most tests.
|
|
|
|
| |
more tabs that XEmacs Makefile mode found suspicious.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Made framework builds work for MacOSX. The configure arg is now
"--enable-framework".
- Added an install target frameworkinstall which installs the framework.
- Ripped out Next/OpenStep support, which was broken anyway.
- Made the MacOSX toolbox glue dependant on a --enable-toolbox-glue
configure arg. This should make naked darwin build work again (untested).
A few targets have been added to Makefile.pre.in, and on inspection they
look harmless to non-MacOSX machines, but it is worth checking.
Closes bug #420601 and patch #450350.
|
|
|
|
| |
This fixes the problem reported in bug report #438786.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Python warning which can be catched by means of the Python warning
framework.
It also adds two new APIs which hopefully make it easier for Python
to switch to buffer overflow safe [v]snprintf() APIs for error
reporting et al. The two new APIs are PyOS_snprintf() and
PyOS_vsnprintf() and work just like the standard ones in many
C libs. On platforms which have snprintf(), the native APIs are used,
on all other an emulation with snprintf() tries to do its best.
|
| |
|
|
|
|
| |
and PYTHONPATH).
|
|
|
|
|
|
|
| |
doesn't work -- it actually prevents the extensions from being built
properly. So I'm changing the "sharedmods" target to what I presume
it was before:
PYTHONPATH= ./$(PYTHON) $(srcdir)/setup.py build
|
|
|
|
|
|
| |
back-out 1.215 of configure.in and 1.34 of Makefile.pre.in
Check for -Kpthread compiler support, and use this as the sole option
for MT if available.
|
|
|
|
| |
bug #442627.
|
|
|
|
|
|
|
| |
Mac/macglue.c into the core interpreter. This file contains the glue code that
allows extension modules for Mac toolboxes to live in different shared libraries
but still communicate with each other. The glue code is controlled by the
USE_MAC_TOOLBOX_GLUE define.
|
|
|
|
|
| |
Makefile and used by the setup.py script. Ignore it in .cvsignore;
remove it in "make clobber".
|
|
|
|
| |
directives, which is the role of CPPFLAGS. Closes SF patch #414991.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
new slot tp_iter in type object, plus new flag Py_TPFLAGS_HAVE_ITER
new C API PyObject_GetIter(), calls tp_iter
new builtin iter(), with two forms: iter(obj), and iter(function, sentinel)
new internal object types iterobject and calliterobject
new exception StopIteration
new opcodes for "for" loops, GET_ITER and FOR_ITER (also supported by dis.py)
new magic number for .pyc files
new special method for instances: __iter__() returns an iterator
iteration over dictionaries: "for x in dict" iterates over the keys
iteration over files: "for x in file" iterates over lines
TODO:
documentation
test suite
decide whether to use a different way to spell iter(function, sentinal)
decide whether "for key in dict" is a good idea
use iterators in map/filter/reduce, min/max, and elsewhere (in/not in?)
speed tuning (make next() a slot tp_next???)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The changes cause compilation failures in any file in the Python
installation lib directory to cause the install to fail. It looks
like compileall.py intended to behave this way, but a change to
py_compile.py and a separate bug defeated it.
Fixes SF bug #412436
This change affects the test suite, which contains several files that
contain intentional errors. The solution is to extend compileall.py
with the ability to skip compilation of selected files.
NB compileall.py is changed so that compile_dir() returns success only
if all recursive calls to compile_dir() also check success.
|
|
|
|
|
| |
clobber". This is done so that after a "make clean", setup.py will
also recompile all extensions.
|
| |
|
|
|
|
| |
strip them. Closes patch #406287.
|
|
|
|
|
|
| |
think that a command starting with '#' is a comment, so move the one
comment in such a position (in the rule for building $(LIBRARY)) to a
harmless position.
|
|
|
|
|
|
| |
- Add CONFIG_ARGS variable and use it to re-run configure rather than
using config.status. This prevents an infinite loop if configure
dies while re-configuring.
|
|
|
|
|
| |
Cygwin Python to startup correctly when in ntsec mode. Cygwin operating in
this mode is probably not the only system with this requirement.
|
|
|
|
|
|
|
|
| |
into Makefile.pre.in; the configure script will only determine the basename
of the file.
This fixes installation of a Python built using C++, reported by Greg
Wilson.
|
|
|
|
|
| |
test_dl, test___all__, test_fork1, and test_longexp. All these either
take way too long with Insure or crash it.
|