Dieter Maurer wrote:
> M.-A. Lemburg wrote at 2006-10-18 12:02 +0200:
>> ...
>> As I understand it, the only case that the PYC cleaner is trying
>> to work around here is a local configuration problem which only
>> occurs if some PY file was removed upstream.
>> In such a case, checking in the PYC files seems like the
>> proper fix, since then Subversion or CVS will automatically
>> and correctly remove the PYC file as well.
> We should not manage "*.pyc" file in the repository: they
> carry the source path as of their creation -- which is likely to be wrong for
> the working directory. This makes tracebacks and debugging much more
> difficult....

We've been using such a setup for years and have never run into
any serious problems with the traceback sometimes mentioning
source file paths don't exist on the target machine.

BTW: I was talking about a setup where the developer puts the
code under version control. I'm not suggesting to do this for
the Zope repository (or any other upstream repository).

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, Oct 18 2006)
>>> Python/Zope Consulting and Support ...
>>> mxODBC.Zope.Database.Adapter ...   
>>> mxODBC, mxDateTime, mxTextTools ...

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
Zope-DB mailing list

Reply via email to