Snapshot win32all builds of interest?
I'm wondering if there is any interest in me making regular, basically untested win32all builds against the current Python CVS tree?
It would be fairly simple for me to do - I run against CVS Python, so it is really just bundling up my latest built files into an installer .EXE. I would only do it for the current CVS trunk - ie, no Python 2.2 or earlier builds in this form. However, I would only bother if there were people willing to use it. I figure that if there aren't people in this forum who would use it, I won't find them anywhere ;)
OTOH, people in this forum using CVS Python on Windows may prefer to use CVS and build their own win32all - I really have no clue ;)
Thoughts?
Mark.
I'm wondering if there is any interest in me making regular, basically untested win32all builds against the current Python CVS tree?
It would be fairly simple for me to do - I run against CVS Python, so it is really just bundling up my latest built files into an installer .EXE. I would only do it for the current CVS trunk - ie, no Python 2.2 or earlier builds in this form. However, I would only bother if there were people willing to use it. I figure that if there aren't people in this forum who would use it, I won't find them anywhere ;)
I think that would be useful, especially if the current 2.2-compatible win32all does not work with 2.3, or if you have added features since that was last released.
OTOH, people in this forum using CVS Python on Windows may prefer to use CVS and build their own win32all - I really have no clue ;)
Not me. I know how to build and install Python from source on Windows, but setting up another project is a major pain for a Unix weenie like me, so I'd much prefer a binary distribution.
--Guido van Rossum (home page: http://www.python.org/~guido/)
[Me]
I'm wondering if there is any interest in me making regular, basically untested win32all builds against the current Python CVS tree?
[Guido]
I think that would be useful, especially if the current 2.2-compatible win32all does not work with 2.3, or if you have added features since that was last released.
OK - first such snapshot done. See the link from starship.python.net/crew/mhammond
This version installs no shortcuts, does not compile .pyc files etc - you are pretty much on your own. Pythonwin\start_pythonwin.pyw is installed to start Pythonwin, but you must do so manually.
Please let me know if you try it.
Mark.
[Mark Hammond]
OK - first such snapshot done. See the link from starship.python.net/crew/mhammond
This version installs no shortcuts, does not compile .pyc files etc - you are pretty much on your own. Pythonwin\start_pythonwin.pyw is installed to start Pythonwin, but you must do so manually.
Please let me know if you try it.
I tried it. I'd say something useful, except as far as I could tell, it worked <wink>. Thanks! Have you talked w/ the PBF about getting builds tested?
FYI, the current PLabs Python uninstaller arranges to delete .pyc and .pyo files via these WISE lines in the installer:
Add "File Tree: %MAINDIR%*.pyc" to INSTALL.LOG Add "File Tree: %MAINDIR%*.pyo" to INSTALL.LOG
These arrange to (recursively) delete all .pyc and .pyo files at uninstall time, and "do the right thing": any directories left empty at the end are magically removed.
From: "Tim Peters" tim@zope.com
[Mark Hammond]
OK - first such snapshot done. See the link from starship.python.net/crew/mhammond
This version installs no shortcuts, does not compile .pyc files etc - you are pretty much on your own. Pythonwin\start_pythonwin.pyw is installed to start Pythonwin, but you must do so manually.
Please let me know if you try it.
I tried it. I'd say something useful, except as far as I could tell, it worked <wink>. Thanks! Have you talked w/ the PBF about getting builds tested?
Same for me (except that I see a lot of these FutureWarnings about hex constants > sys.maxint, but you already knew this).
Thomas
"Tim Peters" tim@zope.com writes:
I tried it. I'd say something useful, except as far as I could tell, it worked <wink>. Thanks!
I've had a few problems. Running it in a console gives the messages
Failed to connect to Pythonwin|System. Error 0
mh\Pythonwin\pywin\scintilla\view.py:18: DeprecationWarning: the regex module is deprecated; please use the re module import regex E:\Pyinst\python\lib\regsub.py:15: DeprecationWarning: the regsub module is deprecated; please use re.sub() DeprecationWarning)
which appear to be harmless; I'll report them anyway in case you are unaware of them.
More troubling is that Find (Ctrl-F) does not work: I get
Traceback (most recent call last): File "mh\Pythonwin\pywin\scintilla\view.py", line 349, in OnCmdEditFind ImportError: No module named find
Any suggestions?
Regards, Martin
participants (5)
-
Guido van Rossum -
Mark Hammond -
martin＠v.loewis.de -
Thomas Heller -
Tim Peters