M.-A. Lemburg wrote:
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.
Nope, not at all...
Quite often shows up early in the development cycle...
1. create myfoo.py
2.
Charlie Clark wrote:
Technically you should actually use $INSTANCE_HOME/modules at least for
Never heard of 'modules' before, where did you read about this?
newer versions of Zope and I think this is also the way to go in the
future. We've stuck with $INSTANCE_HOME/lib as this works with so
Am 16.10.2006, 15:10 Uhr, schrieb Chris Withers [EMAIL PROTECTED]:
Charlie Clark wrote:
Technically you should actually use $INSTANCE_HOME/modules at least for
Never heard of 'modules' before, where did you read about this?
My bad - I'm sure I saw it on one of the more recent Zope versions
Paul Winkler wrote:
If you have mxODBCZopeDA and are using it with zope 2.9 or higher,
a word of warning:
You *must* use the -k option to the test runner when running
tests in your INSTANCE_HOME.
Example:
./bin/zopectl test -k
If you fail to use -k, the zope test runner will
M.-A. Lemburg wrote:
If you fail to use -k, the zope test runner will delete bytecode for all
your products - including mxODBCZopeDA, which has no .py files to fall
back on. Ouch. I'll investigate further - there might be a bug to file
against zope.testing.
Why does the test runner delete
On Oct 13, 2006, at 5:14 AM, Chris Withers wrote:
I have to echo Jens' sentiments though: why not just ship .py files
and be done with it?
If I had to make a wild-ass guess, its because there's an indication
that the mxodbc code would be misappropriated and proliferated
outside of
Chris Withers wrote:
M.-A. Lemburg wrote:
If you fail to use -k, the zope test runner will delete bytecode for all
your products - including mxODBCZopeDA, which has no .py files to fall
back on. Ouch. I'll investigate further - there might be a bug to file
against zope.testing.
Why does
Am 10.10.2006, 23:35 Uhr, schrieb Paul Winkler [EMAIL PROTECTED]:
If you have mxODBCZopeDA and are using it with zope 2.9 or higher,
a word of warning:
You *must* use the -k option to the test runner when running
tests in your INSTANCE_HOME.
Example:
./bin/zopectl test -k
If you fail to use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Oct 2006, at 17:57, Charlie Clark wrote:
Am 10.10.2006, 23:35 Uhr, schrieb Paul Winkler [EMAIL PROTECTED]:
If you fail to use -k, the zope test runner will delete bytecode
for all
your products - including mxODBCZopeDA, which has no .py
