Fred Drake [Thu, 7 Sep 2000 18:55:08 +0000 (18:55 +0000)]
\file is not allowed in section titles -- converting to PDF fails due to
weird macro-expansion issues. A better solution may be available in the
future, but this will do for now.
Add an index entry. More should probably be added as well.
Thomas Heller [Thu, 7 Sep 2000 15:59:22 +0000 (15:59 +0000)]
Changes:
distutils/command/bdist_wininst.py:
- the windows installer is again able to compile after installing
the files. Note: The default has changed, the packager has to
give --no-target-compile/--no-target-optimize to NOT compile
on the target system. (Another note: install_lib's --compile
--optimize options have the same semantics to switch off
the compilation. Shouldn't the names change?)
- All references to specific python versions are gone.
- A small bug:
raise DistutilsPlatformError ("...")
instead of
raise DistutilsPlatformError, ("...")
- When bdist_wininst creates an installer for one specific python
version, this is reflected in the name:
Distutils-0.9.2.win32-py15.exe instead of
Distutils-0.9.2.win32.exe
- bdist_wininst, when run as script, reads the wininst.exe file
and rewrites itself. Previously this was done by hand.
misc/install.c
- All the changes needed for compilation
- Deleted a lot of debug/dead code
Tim Peters [Thu, 7 Sep 2000 08:34:01 +0000 (08:34 +0000)]
Windows installer, reflecting changes that went into a replacement 2.0b1
.exe that will show up on PythonLabs.com later today:
Include the Lib\xml\ package (directory + subdirectories).
Include the Lib\lib-old\ directory.
Include the Lib\test\*.xml test cases (well, just one now).
Remove the redundant install of Lib\*.py (looks like a stray duplicate
line that's been there a long time). Because of this, the new
installer is a little smaller despite having more stuff in it.
Bullet-proofing of 'make_release_tree()':
- 'mkpath()' the distribution dir in case of empty manifest
- warn if empty manifest
- detect, warn about, and skip non-regular files in manifest
Reorganized logic in 'get_file_list()' so it's easier to read, and fixed a
bug to boot: now works even if both MANIFEST and MANIFEST.in don't exist.
Don't hardcode setup.py, use 'self.distribution.script_name'.
Tim Peters [Tue, 5 Sep 2000 20:15:25 +0000 (20:15 +0000)]
Added Windows news. Also repeated 1.6 Windows news since most people getting
2.0b1 for Windows will not have bothered getting 1.6. Also changed
"Changed, New, Obsolete Tools" to say "None" since nobody had put an entry
there.
Jeremy Hylton [Tue, 5 Sep 2000 19:36:26 +0000 (19:36 +0000)]
All the NEWS that I could finish in 15 minutes (and then some)
Removed some attributions from the shorter entries in Changed Modules,
because that section is so long.
Many changes suggested by Bob Weiner, mostly small grammatical fixes
or other clarifications, with the occasional plug for BeOpen
PythonLabs thrown in. Also added a trademarks disclaimer.
Fred Drake [Tue, 5 Sep 2000 15:19:56 +0000 (15:19 +0000)]
Fix PDF generation.
The \\ introduced in the \author in boilerplate.tex broke the PDF
generation because line breaks are not allowed in the "Document Info"
metadata stored in the PDF file. This changes the line break to
a ", " (comma-space) in that context.
Since it looks like the dual license clause may be neither necessary
nor sufficient to make Python 2.0 compatible with the GPL, we won't
bother with it now.
In other words, we're still where we were weeks ago -- CNRI believes
that its license is GPL-compatible, Stallman says it's not. I'm
trying to arrange a meeting between their lawyers so they can work it
out. Whether dual licensing is the solution is open at this point.
If it is the (only!) solution, we'll add that to the BeOpen license
for 2.0 final.
Tim Peters: "Audun S. Runde mailto:audun@mindspring.com wins a
Fabulous Prize for being our first Windows ME tester! Also our only,
and I think he should get another prize just for that."
Tim Peters [Mon, 4 Sep 2000 07:34:06 +0000 (07:34 +0000)]
test_mmap wrote null bytes into its expected-output file; this caused me to
waste an hour tracking down an illusion; repaired it; writing/reading non-
printable characters (except \t\r\n) into/outof text-mode files ain't
defined x-platform, and at least some Windows text editors do surprising
things in their presence.
Also added a by-hand "build humber" to the Windows build, in an approximation
of Python's inexplicable BUILD-number Unix scheme. I'll try to remember to
increment it each time I make a Windows installer available. It's starting
at 2, cuz I've put 2 installers out so far (both with BUILD #0).
Fixes bug in --with-libdb. If --with-libdb was not specified (default is to
enable it), but db.h was not found, the WITH_LIBDB macros was still being
defined, resulting in compilation errors. Also added a short explain when
bsddb support wasn't enabled (because db.h wasn't found) when the user
explicitly used --with-libdb on the configure command line.
Move down the INT_MAX logic, because HAVE_LIMITS_H was always undefined
and this breaks the AIX build with an INT_MAX redefinition error.
"config.h" is included in pgenheaders.h, so moving this down fixes the
problem.
Properly name and number the BEOPEN OPEN SOURCE PYTHON LICENSE
AGREEMENT VERSION 1.
trade name -> trade names.
Note: depending on community feedback, we may end up taking the dual
licensing clause out for 2.0b1, and put it back into 2.0final, if
there's no other solution for assuring GPL compatibility by then.
Tim Peters [Sun, 3 Sep 2000 08:15:19 +0000 (08:15 +0000)]
Repair failing test_sre.py.
This was a funny one! The test very subtly relied on 1.5.2's
behavior of treating "\x%" as "\x%", i.e. ignoring that was an
\x escape that didn't make sense. But /F implemented PEP 223,
which causes 2.0 to raise an exception on the bad escape.
Fixed by merely making the 3 such strings of this kind into
raw strings.
Tim Peters [Sat, 2 Sep 2000 09:16:15 +0000 (09:16 +0000)]
PyInterpreterState_New is not thread-safe, and the recent fix to _PyPclose
can cause it to get called by multiple threads simultaneously.
Ditto for PyInterpreterState_Delete.
Of the former, the docs say "The interpreter lock need not be held, but may
be held if it is necessary to serialize calls to this function". This
kinda implies it both is and isn't thread-safe.
Of the latter, the docs merely say "The interpreter lock need not be
held.", and the clause about serializing is absent.
I expect it was *believed* these are both thread-safe, and the bit about
serializing via the global lock was meant as a permission rather than a
caution.
I also expect we've never seen a problem here because the Python core
(prior to the _PyPclose fix) only calls these functions once per run.
The Py_NewInterpreter subsystem exposed by the C API (but not used by
Python itself) also calls them, but that subsystem appears to be very
rarely used.