summaryrefslogtreecommitdiffstats
path: root/PCbuild
Commit message (Collapse)AuthorAgeFilesLines
* pydoc changed overnight in such a way that it no longer worked from theTim Peters2001-03-231-3/+3
| | | | Windows start-menu item. This recovers from that.
* Add Jeremy's compiler to the Windows install.Tim Peters2001-03-231-0/+18
|
* Update Windows installer for 2.1b2.Tim Peters2001-03-213-4/+6
|
* When building the installer, prompt for the location of the system directoryTim Peters2001-03-191-3/+5
| | | | | on the current machine. Wise doesn't seem to know this itself, and it varies across Windows flavors.
* Windows: Fallout from renaming the pydoc file.Tim Peters2001-03-111-1/+1
|
* SF bug Win32: pydoc command isn't executable.Tim Peters2001-03-111-1/+1
| | | | | | As the bug report notes, the Windows installer creates a useless pydoc file in the base directory. Changed the installer to rename it pydoc.pyw instead.
* Magic strings in both Python and the Wise installer define the registry keyTim Peters2001-03-111-1/+4
| | | | | to be used in Windows. They got out of synch. Repaired that, and added comments to each one pointing at the other.
* Add a new item to the Python 2.1 start menu: "Module Docs".Guido van Rossum2001-03-021-0/+14
| | | | | | This brings up Ping's pydoc server. (XXX The icons for this and for IDLE seem screwed. Oh well.)
* Prepare Windows for 2.1 beta 1: installer dialogs and bump "build number".Tim Peters2001-03-013-5/+7
|
* Backing out nested scopes broke the Windows build. Repairing.Tim Peters2001-02-271-0/+2
|
* Teach Windows build about new future.c.Tim Peters2001-02-271-0/+15
|
* Windows: Remove soundex from pythoncore subproject.Tim Peters2001-02-221-15/+0
|
* Clean up the "docs".Tim Peters2001-02-191-7/+16
|
* Re-add DOS line-endings and mark the files binary.Thomas Wouters2001-02-143-1952/+1952
|
* Change Windows test to do a complete job of removing .pyc/.pyo filesTim Peters2001-02-112-4/+25
| | | | reachable from Lib/.
* Teach Windows build about new symtable.c.Tim Peters2001-02-091-0/+15
|
* Renamed _testXXX to _testcapiXXX. Jack is my hero -- good call!Tim Peters2001-02-044-23/+29
|
* Teach Windows build and installer about new _symtable module/DLL.Tim Peters2001-02-024-3/+126
|
* Teach the Windows installer about the _test module.Tim Peters2001-02-021-0/+10
|
* Patch derived from Trent's 101162: a Python/C API testing framework.Tim Peters2001-02-023-0/+114
| | | | STILL NEEDS UNIX BUILD CHANGES.
* Teach Windows build about the _weakref module.Tim Peters2001-02-021-0/+15
|
* Windows build: update for 2.1a2, + get ucnhash out of the installer.Tim Peters2001-02-014-15/+9
|
* Docs for new Windows zlib build procedure.Tim Peters2001-01-311-6/+11
|
* Fix [ Bug #129293 ] zlib library used for binary win32 distribution can crashMark Hammond2001-01-311-4/+14
| | | | This involves changing the zlib build process to build zlib itself from sources, then use that library. Also updated are the comments to reflect the new official home of zlib, and add Windows specific notes regarding the build process.
* Teach Windows build about new cellobject.c.Tim Peters2001-01-261-0/+15
|
* Windows: ucnhash subproject no longer exists (/F merged into unicodedata).Tim Peters2001-01-243-115/+1
|
* Added -O option (to run python or python_d w/ -O),Tim Peters2001-01-231-8/+14
|
* Remove unicodedatabase.c from the unicodedata subproject.Tim Peters2001-01-211-4/+0
|
* When running the tests twice, stuck a "Press any key to continue ..." pauseTim Peters2001-01-201-6/+5
| | | | | | between passes: Win9x DOS boxes are limited to 50 lines max, and the result of the first pass scrolls off irretrievably otherwise. Also simplified the goto-laden logic a bit.
* Run tests twice by default, first time deleting .pyc/.pyo files.Tim Peters2001-01-191-2/+20
| | | | New option "-q" to leave .pyc/.pyo alone.
* Delete the bytecode from the library and tests before running theGuido van Rossum2001-01-191-0/+4
| | | | | | tests for the first time -- like the Unix Makefile does. This avoids not catching problems in the bytecode generator and/or bytecode marshalling.
* Clarifications.Tim Peters2001-01-181-7/+7
|
* Windows: 2.1a1 changes so Python runs again. Note that the python20Tim Peters2001-01-176-1752/+1752
| | | | subproject is gone, replaced by the new pythoncore subproject.
* Windows installer: update dialogs, program groups, etc, to 2.1 alpha 1.Tim Peters2001-01-171-5/+5
|
* Export mmap's entry point under Windows (thanks, MarkH & Guido!).Tim Peters2001-01-111-2/+4
|
* Make Windows build compile new xreadlinesmodule.Tim Peters2001-01-091-0/+15
|
* Prep the Windows installer for 2.0 final:Tim Peters2000-10-143-8/+14
| | | | | | | + Bump the build number. + Changed app name in installer dialogs. + Fiddled dialogs to repair grammar and get rid of anachronisms (e.g., "ProgMan" and "Program Manager" haven't made sense since Windows 3.1!).
* Prep Windows installer for 2.0c1: title and build number.Tim Peters2000-10-073-4/+6
|
* Yet another new unique extension in the test directory.Tim Peters2000-09-261-0/+5
|
* Bump Windows "build number" to 6.Tim Peters2000-09-252-2/+4
| | | | | Note that somebody still needs to change the interpreter to say "2.0b2"; I'm assuming that's a normal part of somebody's Unix release checklist.
* Implemented new os.startfile function, unique to Windows, exposing aTim Peters2000-09-221-2/+2
| | | | | | | | | | | | | | | | subset of Win32 ShellExecute's functionality. Guido wants this because IDLE's Help -> Docs function currently crashes his machine because of a conflict between his version of Norton AntiVirus (6.10.20) and MS's _popen. Docs for startfile are being mailed to Fred (or just read the docstring -- it tells the whole story). Changed webbrowser.py to use os.startfile instead of os.popen on Windows. Changed IDLE's EditorWindow.py to pass an absolute path for the docs (hardcoding ShellExecute's "directory" arg to "." as used to be done let IDLE work, but made the startfile command exceedingly obscure for other uses -- the MS docs are terrible, of course, & still not sure I understand it). Note that Windows Python must link with shell32.lib now! That's where ShellExecute lives.
* Windows installer:Tim Peters2000-09-211-9/+159
| | | | | Don't ship debug .dll, .pyd or .lib files. Saves space. Bumped the title to beta 2.
* Added simple batch file to make running the test suite from the PCbuildTim Peters2000-09-151-0/+8
| | | | directory less tedious.
* Windows installer: In the Start menu IDLE shortcut, explictly invoke theTim Peters2000-09-111-1/+2
| | | | | | pythonw.exe we just installed. Making Windows key off the .pyw extension instead screws people with multiple Python installations (reported more than once on c.l.py).
* Boost Windows build # to 5 (see new BUILDno.txt).Tim Peters2000-09-071-2/+2
|
* Windows installer, reflecting changes that went into a replacement 2.0b1Tim Peters2000-09-071-5/+17
| | | | | | | | | | .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.
* Document new Windows build # scheme.Tim Peters2000-09-071-0/+45
|
* Windows build: install NEWS.txt; bump BUILD# to 3 in preparation for nextTim Peters2000-09-052-2/+7
| | | | installer.
* Now that I've got real docs, redirect _DOC_ out of the Python 1.6 tree andTim Peters2000-09-051-1/+2
| | | | | to the new docs. Added a description to the Tcl/Tk file copies.
* test_mmap wrote null bytes into its expected-output file; this caused me toTim Peters2000-09-041-0/+4
| | | | | | | | | | | 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).