| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Update Windows command line.
|
|
|
|
| |
latest bsddb release without strong cryptography).
|
|
|
|
| |
Not anymore it ain't.
|
|
|
|
|
|
|
|
|
| |
PC/python_nt.rc sets up the DLL version resource (displayed when you
right-click on the DLL and select Properties).
PCbuld/python20.wse sets up the installer version resource (displayed
when you right-click on the installer .exe and select Properties). Turns
out this one hadn't been updated since 2001 <frown>!
|
|
|
|
|
|
| |
Added the logging package. In the meantime, Neal Norwitz added a
test_logging.py to the std test suite, which would have caught this
oversight in the Windows installer.
|
|
|
|
| |
I leave to Fred to sort out.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- new import hooks in import.c, exposed in the sys module
- new module called 'zipimport'
- various changes to allow bootstrapping from zip files
I hope I didn't break the Windows build (or anything else for that
matter), but then again, it's been sitting on sf long enough...
Regarding the latest discussions on python-dev: zipimport sets
pkg.__path__ as specified in PEP 273, and likewise, sys.path item such as
/path/to/Archive.zip/subdir/ are supported again.
|
| |
|
| |
|
|
|
|
|
| |
into the core DLL, since it's not much code and lots of stuff uses
it (e.g., try getting a tempfile name without it).
|
|
|
|
|
| |
to others to argue about how to build it on other platforms (on Windows
it's in its own DLL).
|
|
|
|
| |
build_ssl.py requires os.popen().
|
|
|
|
| |
Barry agreed, and I see no reason not to.
|
|
|
|
| |
DLL and lib sections.
|
| |
|
| |
|
|
|
|
| |
Contributed by David Bolen.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
this before I add the _ssl project, so that checkin is cleaner.
|
|
|
|
|
|
|
|
|
|
|
|
| |
whether this is a correct thing to do:
+ There are linker warnings (see PCbuild\readme.txt).
+ test_bsddb passes, in both release and debug builds now.
+ test_bsddb3 has several failures, but it did before too.
Also made pythoncore a dependency of the _bsddb project, updated
build instructions, added database conversion XXX to NEWS, and fiddled
the Windows installer accordingly.
|
|
|
|
|
|
|
|
| |
+ News blurb, but as much XXX as news.
+ Updated installer (install the new bsddb package, and the Berkeley DLL;
still don't know how to fold that into _bsddb.pyd).
+ Fleshed out build instructions.
+ Debug Python still blows up.
|
|
|
|
|
|
|
| |
The bsddb subproject is gone.
The _bsddb subproject is new.
There are problems here, but I'm out of time to work on this now. If
anyone can address an XXX comment or two in readme.txt, please do!
|
|
|
|
|
| |
dependence on the Tcl/Tk version number. Now you point it at the
Tcl/Tk install you want to ship, and that's what it ships.
|
|
|
|
| |
work on Win98SE too (yay!).
|
|
|
|
|
|
|
| |
running IDLE, and since I'm not a Tcl Guy I'm not sure what else to do.
Up to you! See XXX comments in PCbuild\readme.txt for cautions.
Also repaired typos in the new bz2-for-Windows instructions.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
CAUTION: The Python test still has many failures, but I'm out of time
for this now (already took much longer than hoped to get this far).
The base bz2 library does pass its own tests (see next).
CAUTION: People building on Windows have to download and build tne
bz2 compression libraries now. See PCbuild\readme.txt for complete
instructions.
|
| |
|
|
|
|
|
|
| |
correctly. So field3.py is a Python program that can. This injects
another manual step into the Python release process for Windows; so
it goes.
|
| |
|
|
|
|
|
| |
The -tt means modules that mix tabs and spaces will be rejected.
The -E refuses to believe Python options in the environment.
|
|
|
|
| |
package, and the loss of the test/data directory.
|
|
|
|
|
| |
command line for Windows builds. This should allow MSVC to import and
build the Python MSVC6 project files without error.
|
| |
|
| |
|
|
|
|
| |
the Windowish builds.
|
|
|
|
| |
Python on Windows without it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These built-in functions are replaced by their (now callable) type:
slice()
buffer()
and these types can also be called (but have no built-in named
function named after them)
classobj (type name used to be "class")
code
function
instance
instancemethod (type name used to be "instance method")
The module "new" has been replaced with a small backward compatibility
placeholder in Python.
A large portion of the patch simply removes the new module from
various platform-specific build recipes. The following binary Mac
project files still have references to it:
Mac/Build/PythonCore.mcp
Mac/Build/PythonStandSmall.mcp
Mac/Build/PythonStandalone.mcp
[I've tweaked the code layout and the doc strings here and there, and
added a comment to types.py about StringTypes vs. basestring. --Guido]
|
| |
|
|
|
|
|
|
|
|
| |
option. It was the cause of at least one way UNWISE.EXE could vanish
(install a python; uninstall it; install it again; reboot the machine;
abracadabra the uinstaller is gone).
Bugfix candidate, but I'll backport it myself.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Fix Windows-specific install glitch. Tested on Win2K, but I can't test
on XP.
Already checked in to the release22-maint branch.
|
|
|
|
|
| |
permission from Paul Everitt). Also removed a few other references to
Digital Creations and changed the remaining ones to Zope Corporation.
|