summaryrefslogtreecommitdiffstats
path: root/PCbuild
Commit message (Collapse)AuthorAgeFilesLines
* Update Windows installer for 2.2c1.Tim Peters2001-11-171-4/+4
|
* Bump Windows buildno for 2.2b2.Tim Peters2001-11-152-2/+4
|
* SF bug #478949 Windows installer start menu registry.Tim Peters2001-11-071-5/+7
| | | | | | | | | | | I'm guessing at this, pending more info from the bug submitter. Wise changed how the %GROUP% vrbl got defined between versions 5.0a (used before Python 2.2) and 8.14, to hold the full path to Start Menu group instead of just the group name. If I'm guessing correctly, the info the bug report is complaining about is in one of the registry keys we set up that neither Windows nor Python cares about. We did store a full path there in 2.2b1 instead of just the group name; the patch cuts it back to just the name again.
* The usual post-release fiddling.Tim Peters2001-10-191-4/+4
|
* add structseq.c to projectGuido van Rossum2001-10-181-0/+15
|
* Bump Windows build # for 2.2b1.Tim Peters2001-10-182-2/+4
|
* Added new hotshot pkg to the Windows installer.Tim Peters2001-10-131-35/+43
| | | | Rearranged the growing number of Lib packages into alphabetical order.
* Get hotshot closer to compiling on Windows.Tim Peters2001-10-121-0/+15
| | | | | Still broken: GETTIMEOFDAY. This macro obviously isn't being defined on Windows, so there's logic errors here I'd rather Fred untangled.
* If all of Python, IDLE and Tcl/Tk are being installed, and the user hasTim Peters2001-10-091-0/+42
| | | | | | not disabled file-extension registration, arrange for .py and .pyw files to have an "Edit with IDLE" context (right-click) menu entry, selecting which executes IDLE w/ the -e switch followed by the selected file's path.
* Teach Windows how to build the new weakref module.Tim Peters2001-10-051-0/+15
|
* Post-release fiddling (prep for 2.2b1).Tim Peters2001-09-281-4/+4
|
* Bump Windows build numbers for 2.2a4; installer changes were done earlier.Tim Peters2001-09-272-2/+4
|
* Install the new Lib/email pkg.Tim Peters2001-09-231-0/+16
| | | | Create & populate the new Lib/test/data directory.
* Install the compiler package under Lib.Tim Peters2001-09-201-26/+8
|
* The usual post-release fiddling.Tim Peters2001-09-081-4/+4
|
* Bump Windows buildno (installer changes were made earlier).Tim Peters2001-09-062-2/+4
|
* First part of fix for bug #442142 - DLL base assignments need updateMark Hammond2001-09-067-14/+16
|
* Add pynche's top-level txt files to Windows installer -- I don't believeTim Peters2001-08-221-1/+7
| | | | we've *ever* installed them!
* "The usual" post-release fiddling.Tim Peters2001-08-222-5/+5
|
* Windows fiddling for 2.2a2: bump build number; update copyright andTim Peters2001-08-193-6/+8
| | | | | company info in resource files; change installer strings to match. This belongs in the release branch too, of course.
* Wise uninstallers never delete the Python DLL from the system directory.Tim Peters2001-08-161-0/+9
| | | | | They should. Added a line that's supposed to fix that -- it doesn't actually work on my box, but checking it in anyway.
* New, larger installer bitmap from Erik van Blokland. Added moreTim Peters2001-08-152-4/+6
| | | | | vertical whitespace to the acknowledgements portion of the "Installation Completed!" screen for easier reading.
* Now that the dialogs have some breathing room, split the combo of Tcl/Tk,Tim Peters2001-08-111-56/+130
| | | | | | | | | | IDLE and pydoc into a separate component. That's almost as big as the rest of Python (excl. docs and test suite) combined. Pop up a confimation box if they choose to install at least one of {Tcl/Tk/IDLE/pydoc, Tools, Test suite} but do not choose to install Python -- doesn't make much sense, so ask whether that's really what they want.
* Grow the dialogs 25%, to make room for a nicer bitmap (in progress; don'tTim Peters2001-08-111-83/+84
| | | | have it yet).
* In the acks, CamelCase InstallMaster the same way Wise does it.Tim Peters2001-08-091-1/+1
|
* Add a comma.Tim Peters2001-08-081-1/+1
|
* Give some special thanks on the final "Installation Completed!" screen.Tim Peters2001-08-081-1/+21
|
* Thanks toTim Peters2001-08-082-4/+4
| | | | | | | | | LettError, Erik van Blokland, http://www.letterror.com/ the Python Windows installer finally has an attractive Pythonic bitmap to delight the senses and dampen the fears of the millions and millions of eager new Windows users anticipating their first Python programming joy. Always knew Mac users secretly wanted to switch to Windows <wink>.
* Add the new Tools/compiler/README to the WIndows install, as README.txt.Tim Peters2001-08-082-4/+11
| | | | | | In the Wise installer's "Advanced Options" dialog, substitute in the actual name of "the system directory" -- this is clearer, and especially for people reading this dialog who aren't me <wink>.
* + Turn off patch creation (this isn't a patch release! got turned on byTim Peters2001-08-061-23/+45
| | | | | | | | | mistake). + Arrange for Win2K Add/Remove to show a Python icon. I think this "does it" -- a full install/uninstall can now be done on a Win2K box from an ordinary (not Admin, not Power User) user acct, incl. file extension registration, Start Menu entries, and full Add/Remove.
* + Made installer more reluctant to overwrite MS C runtime DLLs -- it'sTim Peters2001-08-051-44/+271
| | | | | | | | | | | | | | | | | been overwriting them even if they have the same version, not just if they're an older version (and our installers have always done this). + Added an "Advanced Options" subdialog to "Select Components". Allows to do a non-admin install even if you have Administrator rights, and to skip registering file extensions and/or creating Start Menu shortcuts. Since so far these installers have been tested only by me, and Win2K has been full of surprises, I want those options available out in the field. Lots of web searching turned up what should have been obvious: Because Windows Installer is a native Win2K service, it can run at a higher privilege level than the user invoking it. So MSI installs don't bash into these permission gotchas on Win2K, but Wise 8.1 does (it's just another app to Win2K, and we're not alone in wrestling with this; but, like changing int division in Python, Win2K is doing a right thing <wink>).
* Rename pydoc.pyw to pydocgui.pyw: Since we changed Python to allow .pywTim Peters2001-08-051-1/+1
| | | | files to satisfy imports, pydoc.pyw was just importing itself!
* + Redid file associations on Win2K in what I believe is "the right way".Tim Peters2001-08-051-171/+271
| | | | | | | | | | | | | | | Can't test it until getting to a Win2K box, because the non-Admin way of setting file associations on Win2K doesn't work on any other flavor of Windows (and other flavors of Windows never need Admin privs to do it the old way). + Consequently got rid of the "Register file associations" Component and associated GUI. + Added a line to the summary saying whether or not this is an Admin-level install (I fear that will be an important clue someday). + Minor fiddling to the summary to reduce the # of lines. Added a horizontal scrollbar in case the install path is very long. + Reworked the way the Main and Tools components share pydoc.pyw; cleaner and simpler.
* New runtime vrbl DOADMIN. When false, we never try to write under HKLM,Tim Peters2001-08-052-15/+38
| | | | | | | | | | | | and install the Python and MS runtime DLLs into the Python dir instead of a system dir. Initial value is taken from new compiler vrbl _DOADMIN_ (default true), and forced to false if the user doesn't have admin privs. This makes it possible to *test* non-admin installs on machines where the distinction doesn't exist (like my home box), via just changing _DOADMIN_. It may also be useful for users who don't *want* an installer to scribble into their system dir (for example, me(! most days)), but that would require adding more GUI to let them get at it.
* + Add version info to Win2K add/remove.Tim Peters2001-08-041-103/+142
| | | | | | | | | | | | | | | | | | | | | | + Fiddle vrbls so Win2K add/remove can display version w/o future manual script fiddling. + Break apart the mysterious wizard-generated Win2K "Edit 3 Registry Keys" script items by hand into 3 separate items, so you can see what the heck they're doing in the script view. + pydoc.pyw was a problem: it's installed by both the Main and Tools components. So when both were selected, the second time it got installed Wise figured it was overwriting a pre-existing version, and made a backup copy in BACKUP. A rollback-uninstall then restored that, leaving the Tools/Scripts/ directory non-empty, and so Wise couldn't remove that directory (or any above it). Fixed by installing pydoc.pyw at most once. + Rearranged and commented the "register file extensions" section, because it was confusing and needs more work: turns out it's not true that Win2K requires Admin privs to register file extensions, BUT, if you don't have Admin privs, Win2K requires a new way to register file extensions, and a way that doesn't blow up but doesn't do any good either on earlier Windows flavors. I think I know how to get this done, but am too depressed to do it right now <0.7 wink>.
* + Moved IDLE from the "tools" component to the main component.Tim Peters2001-08-031-99/+88
| | | | | | | | | | | + Ditto pydoc. (IMO, both should have been done long ago -- simply didn't occur to me before) + Build the summary text into a vrbl instead of a temp file. Doh! Less fiddling, and should avoid another class of Win2K permission problems. Bug: the "auto vertical scrollbar" control on the summary page doesn't work (never creates a scrollbar, no matter how much text). So forced a vertical scrollbar there.
* No more Inno Envy: the "Start Installation" dialog now displays a niceTim Peters2001-08-031-7/+152
| | | | | | summary of the preceding choices. No idea if this is "the right way" to do it, but it's exactly painful enough to make me suspect it's the only way <wink>.
* Merge of descr-branch back into trunk.Tim Peters2001-08-021-0/+30
|
* Just changes to comments.Tim Peters2001-08-012-3/+3
|
* Repair more ways in which the "backup files" dialog differed from all theTim Peters2001-08-011-29/+28
| | | | | others (wrong title, inconsistent layout). Also tried to make the dialog text clearer, and spelled out what the "yes" and "no" buttons *mean*.
* We always wrote a pair of lines to the Wise install.log telling it toTim Peters2001-08-011-16/+19
| | | | | | | | | | | | delete the Tools and Lib directories at uninstall time. However, under the old version of Wise, they didn't actually do anything. Under the new version, they work as advertised, and even delete files users added. Got rid of those, and replaced them with similar uninstall cmds that get rid of all .pyc and .pyo files (whether or not the installer created them). This works nicely! It still tears down the directory structure, except for those directories needed to get to any non-.pyc/o file(s) the user may have added.
* Hmm. The Backup/Replace dialog also had back/next buttons three pixelsTim Peters2001-08-011-5/+5
| | | | | | narrower than all the other Wise dialogs, and offset by a few pixels in the vertical direction too. Made these things consistent across dialogs too.
* Aha! Finally figured out something else that's been driving me nuts:Tim Peters2001-08-011-2/+2
| | | | | | | | | turns out the canned new "backup directory" dialog put its "back" and "next" buttons at a different relative horizontal position than all the other canned dialogs. This explains why you had to keep moving the mouse around if you wanted to do a straight all-default install -- the Next button kept moving around. Now the back/next buttons are in exactly the same place on all dialogs, and you can click straight thru to the end.
* The "Select Destination Directory" dialog didn't ask for confirmationTim Peters2001-08-011-45/+12
| | | | | | | | | | | | | about installing into a pre-existing directory *unless* you hit the Browse button first. At least while testing, this screwed me repeatedly. Plus I really liked the Inno Setup scheme of giving you a list box in its "select directory" dialog without needing a distinct browse button to ask for that. So I redid this dialog from scratch: now gives a list box at once, the browse button is gone, it asks for confirmation if the directory already exists, and, since this is the first dialog in the set now, also removed its "Back" button.
* Remove useless Back button from Finished dialog.Tim Peters2001-08-011-16/+5
|
* Add mysnprintf.c to Windows build, + squash compiler wngs in mysnprintf.c.Tim Peters2001-07-311-0/+15
|
* I hope this irons out the Add/Remove kinks on Win2K for users w/o AdminTim Peters2001-07-312-9/+57
| | | | privs, but haven't tested that yet. Doesn't hurt on Win98SE, anyway.
* Remove oodles of pointless file date and size stamps. I caught the WiseTim Peters2001-07-301-112/+0
| | | | | | GUI inserting those once before shortly after I started using it, but don't know what triggers it -- presumably something in the "expert" view (which is, suitably enough, unsuited to experts <wink>).
* Massive fiddling to get the install to work at all on a Win2K box under aTim Peters2001-07-302-3/+681
| | | | | | | | | | | | | | | | | | | | | | | plain unprivileged User acct: + Had to duplicate Wise's Uninstal.wse script, in order to change the line at its end that unconditionally tries to write uninstall info under HKLM. This is our new file Uninstal.wse, which must be included by python20.wse instead of using Wise's version. + In every other case we write to HKLM, also write to HKCU instead (we were already doing that in *most* places, but not quite all). + If the user doesn't have admin privs, the DLLs we usually write to the system dir are written to the root of the Python installation instead. That's python22.dll, plus the two MSVC runtime DLLs. + Added a new component "Register file extensions". Registering .py etc is done under HKEY_CLASSES_ROOT, and that also requires admin privs; i.e., AFAICT it's impossible for an unprivileged user to accomplish this. In the component selection dialog, if the user doesn't have admin privs I gray out this new component so the user knows they aren't getting file extensions. After all that, Python installs, the Start Menu entries are OK, it runs its test suite to completion, and the uninstaller works too. Only known problem so far is that the integration with Win2K's Add/Remove subsystem isn't quite right yet in this irritating case.
* Add a dialog for the backup directory (default "yes I want one, andTim Peters2001-07-301-6/+289
| | | | make it MyPythonDirectory\BACKUP\").