[Zope-CMF] Bug#143449 zope-cmfdefault: errors when upgrading zope

Tres Seaver tseaver@zope.com
19 Apr 2002 12:05:56 -0400

On Fri, 2002-04-19 at 10:49, Luca - De Whiskey's - De Vitis wrote:
> On Fri, Apr 19, 2002 at 09:26:52AM -0400, Tres Seaver wrote:
> > The downside to changing the extension is that tools which use the
> > extension to do syntax highlighting won't be able to figure out that
> > the files are Python.
> Is this the only downside?
> Come on guys, there are many editors out there :)
> Most of them can associate an extension to a syntax, and many other can guess the
> file type with some euristics (VIM and emacs for example).
> Why don't we try to find a solution?
> Try to guess if the file if a valid python script is somewhat more diffult
> than changing the extension.

The packaging / installation software is not without fault here;
blindly byte-compiling every ".py" file in a tree during packaging
/ installation is inherently flakey; why doesn't the packaging simply
allow the modules to be compiled on import (or at least swallow any
exceptions generated by the eager compile)?

Tres Seaver                                tseaver@zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com