[EMAIL PROTECTED] wrote:
> Distutils is pretty much an expectation nowadays for Python packages.
> If not by 1.0, then soon after.  If we combine that with a test 
> suite, people will be able to install, test and uninstall Webware
> with the standard Python package tools.  (Although distutils 
> doesn't seem to have ai built-in uninstall support yet.)  Plus Webware
> will then be ready for when a CPAN-stype
> package-finder-downloader-installer becomes available.

Anyone want to volunteer to work on this?  I'm personally much more
interested in working on the testing framework than working on distutils
support.  And I know zero about distutils.

> 
> What about removing the ability to run Webware directly from
> the install directory?  It seems cleaner to force people to run
> MakeAppWorkDir and keep their configuration files separate from
> the installation.  That would also make for a cleaner upgrade.
> Or is it too draconian?

I wouldn't go through extra effort to prevent running out of the install
dir.  But if it makes things cleaner and easier, why not.

Perhaps a compromise is that "install.py" (and later, distutils?) could
itself create a working dir, removing the need for 2 steps -- install.py AND
MakeAppWorkDir.py.

- Geoff

_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to