| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
English output.
|
|
|
|
| |
being printed
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
41667, 41668 - initial switch to xmlcore
47044 - mention of xmlcore in What's New
50687 - mention of xmlcore in the library reference
re-apply xmlcore changes to xml:
41674 - line ending changes (re-applied manually), directory props
41677 - add cElementTree wrapper
41678 - PSF licensing for etree
41812 - whitespace normalization
42724 - fix svn:eol-style settings
43681, 43682 - remove Python version-compatibility cruft from minidom
46773 - fix encoding of \r\n\t in attr values in saxutils
47269 - added XMLParser alias for cElementTree compatibility
additional tests were added in Lib/test/test_sax.py that failed with
the xmlcore changes; these relate to SF bugs #1511497, #1513611
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
inspect.py, and pydoc.py. Specifically, this allows for querying the type of
an object against these built-in C types and more importantly, for getting
their docstrings printed in the interactive interpreter's help() function.
This patch includes a new built-in module called _types which provides
definitions of getset and member descriptors for use by the types.py module.
These types are exposed as types.GetSetDescriptorType and
types.MemberDescriptorType. Query functions are provided as
inspect.isgetsetdescriptor() and inspect.ismemberdescriptor(). The
implementations of these are robust enough to work with Python implementations
other than CPython, which may not have these fundamental types.
The patch also includes documentation and test suite updates.
I commit these changes now under these guiding principles:
1. Silence is assent. The release manager has not said "no", and of the few
people that cared enough to respond to the thread, the worst vote was "0".
2. It's easier to ask for forgiveness than permission.
3. It's so dang easy to revert stuff in svn, that you could view this as a
forcing function. :)
Windows build patches will follow.
|
|
|
|
| |
of 'ln -s', this avoid problems when reinstalling python.
|
|
|
|
|
|
| |
Also don't install "python-config" when doing altinstall, but
always install "python-config2.x" and make a link to it like
with the main executable.
|
|
|
|
|
|
| |
dylib at the root of the framework, that way tools that expect a unix-like
install (python-config, but more importantly external products like
mod_python) work correctly.
|
|
|
|
| |
change to Makefile.pre.in)
|
|
|
|
| |
No need to install lib-old, it's empty in 2.5.
|
|
|
|
| |
be installed.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
with --enable-framework
* Also for --enable-framework: allow users to use --prefix to specify
the location of the compatibility symlinks (such as /usr/local/bin/python)
|
| |
|
|
|
|
|
|
| |
I'm not sure this is the best approach, but I can't think of anything better.
If this creates problems, feel free to revert, but I think it's safe and
should make things a little better.
|
| |
|
|
|
|
|
|
|
| |
target. Until now users had to use 'make frameworkinstall'
to install python when it is configured with '--enable-framework'.
This tends to confuse users that don't hunt for readme files
hidden in platform specific directories :-)
|
|
|
|
|
|
|
|
|
|
|
| |
* Don't use xcodebuild for building PythonLauncher, but use a normal unix
makefile. This makes it a lot easier to use the same build flags as for the
rest of python (e.g. make a universal version of python launcher)
* Convert the mac makefile-s to makefile.in-s and use configure to set makefile
variables instead of forwarding them as command-line arguments
* Add a C version of pythonw, that we you can use '#!/usr/local/bin/pythonw'
* Build IDLE.app using bundlebuilder instead of BuildApplet, that will allow
easier modification of the bundle contents later on.
|
| |
|
|
|
|
|
| |
Handy to have as a separate rule from clean when mucking around with bytecode
generation.
|
| |
|
| |
|
| |
|
|
|
|
| |
independently. Fixes #1355883.
|
| |
|
| |
|
| |
|
|
|
|
| |
otherwise, test/test_ctypes.py fails. What about ctypes.macholib?
|
| |
|
|
|
|
|
| |
BSD make stops the build when it tries to expand wild cards on empty
directories.
|
| |
|
| |
|
|
|
|
| |
configure step.
|
| |
|
|
|
|
| |
Based on a patch from Hye-Shik Chang.
|
|
|
|
| |
the environment.
|
| |
|
|
|
|
| |
Also, stop determining Unicode sizes with PyString_GET_SIZE.
|
| |
|
|
|
|
| |
calculate the build number.
|
|
|
|
|
| |
even though they are generated. Since these files require Python 2.2+,
it's possible they can't be created on a fresh system.
|
|
|
|
|
| |
use of $(srcdir) in Makefile.pre.in so builds outside the source dir still
work.
|
|
|
|
|
|
|
|
|
|
| |
Subversion revision number.
First, in an svn export, there will be no .svn directory, so use an in-file
$Revision$ keyword string with the keyword chrome stripped off.
Also, use $(srcdir) in the Makefile.pre.in to handle the case where Python is
build outside the source tree.
|
|
|
|
|
|
|
| |
Add C API function Py_GetBuildNumber(), add it to the interactive prompt
banner (i.e. Py_GetBuildInfo()), and add it as the sys.build_number
attribute. The build number is a string instead of an int because it may
contain a trailing 'M' if there are local modifications.
|
|
|
|
| |
simplifies a lot of error handling code, and fixes many memory leaks.
|
| |
|