-> > Nonetheless, I don't see this as a problem related to my first set of
-> > questions -- is it?
-> It seems not, but sorry and better so, I was confused by your report, you are
-> not :)
-> > I can't figure out what makes some things work and others not; are there any
-> > hints that anyone can give me? (I'd compile jython myself and just put
-> > printlns in, but I can't compile it at the moment.)
-> The answer: don't expect jythonc to cope properly with program-driven
-> changes to sys.path and similar dynamic stuff.
-> jythonc is a *static* tool.
Ahh, but I have contraindications! In a more complicated piece of code,
dynamic modifications to sys.path result in jythonc finding and correctly
compiling (and including in the output .jar) files from other directories
that were specified only in sys.path.
So, if no dynamic modifications to sys.path should work for jythonc, then I
don't understand why it *does* work occasionally; and if dynamic modifications
*should* work, then I don't understand why it *isn't* for other projects.
If anyone wants to take a look to see what I mean, check out the latest
version of FamilyRelations:
cvs -d:pserver:anonymous@... login
cvs -d:pserver:anonymous@... co FamilyRelations
cd FamilyRelations && make
(you may need to modify the separator from : to ; in some of the classpaths).
This works. It's worked for a long time. I don't understand why doing what
is as far as I can tell the same sort of thing isn't working now!
But I gather that if there is a bug, it's not a well known one ;).