Switch to Mercurial - Feedback on ideas for next version - need compiling help
Dr.Leo
1. I have switched the googlecode project to hg. The svn repository is
still accessible but frozen.
2. The next release will bring major changes:
- upgrade of the C library to v2.7
- There is now a single setup script that does everything both on Python
2.x and 3.x, including configuration. So some helper scripts are gone.
Everything is much cleaner.
- the en_US dictionary is gone. Rather, it is downloaded and installed
by the setup script. Also, setup will try to install the dictionary
according to the locale. It works, but needs some error handling.
Downloading the dictionaries is clearly more convenient for non-English
users. But it may be less robust as an internet connection is needed at
installation time. Also I don't know how Debian packages etc. will cope
with this.
Do you think this installation method is ok, or would you suggest to go
back to the old stuff?
3. Some further ideas
- I am thinking about banning the win32 binaries from the source
distribution and make them available for download on googlecode. The
setup script would try and download the binary if needed. Any views?
- As requested by someone on this list, I am planning to beef up
dictools to use the mapping from locales to dictionaries (Austria
(de_AU) uses de_DE etc.) to improve the installation of dictionaries.
But this is further down the road. And I have very little time. So any
help would be apreciated.
4. Help with compiling and testing
I would be grateful if someone could send me win32 binaries for Python
2.4 and 2.5. I don't have MSVC 2003 installed and don't want mingw so I
cannot do this myself.
Also, please grab the latest revision from the repository and test the
new installation method.
I intend to publish the new release shortly after Python 3.2 is out.
Leo