| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
I have a different WISE version, and it's installed in a different directory.
My sytem directory is somewhere else.
|
|
|
|
|
|
|
|
| |
The fix is confined to the Windows installer.
Not a bugfix candidate: the need for the new -n switch added here was
introduced by moving to the idlefork IDLE (so this change isn't needed
or helpful before 2.3).
|
| |
|
|
|
|
| |
during the day tomorrow, so doing it earlier than I'd like.
|
|
|
|
| |
choice to the list of places MS redistributables might be found.
|
| |
|
|
|
|
| |
"Support IDLE Edit of .py/.pyw from idlelib"
|
| |
|
|
|
|
|
| |
Also install the start script from Tools/script/idle. (This may
change again.)
|
|
|
|
|
|
| |
Tools/idle, in both source and destination. (There are still problems
when running the IDLE icon, but they don't seem to have to do with the
installer.)
|
|
|
|
|
|
|
|
|
| |
This file isn't meant to be executed, it's data input for test_tokenize.py.
The problem with the .py extension is that it uses "non-standard"
indentation, and it's good to test that, but reindent.py keeps wanting
to fix it. But fixing the indentation causes the expected-output file to
change, since exact line and column numbers are part of the
tokenize.tokenize() output getting tested.
|
|
|
|
|
|
| |
After removing that, two testers on machines where C: is not the system
drive reported that the installer suggested their system drive instead
of C:, and that's what they wanted it to do.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
In the Windows installer, continued the endless battle to copy over files
with new one-shot extensions.
|
| |
|
|
|
|
| |
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.
|
|
|
|
|
| |
to others to argue about how to build it on other platforms (on Windows
it's in its own DLL).
|
|
|
|
| |
Barry agreed, and I see no reason not to.
|
|
|
|
| |
DLL and lib sections.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
package, and the loss of the test/data directory.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Expat installer from SF anymore, and the installer shouldn't install
expat.dll anymore.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Rearranged the growing number of Lib packages into alphabetical order.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Create & populate the new Lib/test/data directory.
|
| |
|
| |
|
|
|
|
| |
we've *ever* installed them!
|
| |
|
|
|
|
|
| |
company info in resource files; change installer strings to match.
This belongs in the release branch too, of course.
|