On Fri, Sep 25, 2009 at 6:05 PM, Ben Walton <[email protected]> wrote: > Excerpts from Maciej (Matchek) Blizinski's message of Fri Sep 25 09:43:34 > -0400 2009: >> > To trigger this bug then, you'd need to update a package that uses >> > cswpycompile and any another python package regardless of cswpycompile >> > use? >> >> Yes. In other words, to reproduce: >> >> echo '"' > /opt/csw/lib/python/site-packages/broken.py >> pkgutil -i py_fpconst | less > > Ok, looking at the script, this is exactly what happens. It would > only get tripped when there is a package supplying bad files though, > which is why it didn't show up until now.
Perhaps Python update? There were things that Python 2.5 would turn a blind eye to, but Python 2.6 would not. It'd be nice to have a check for this problem. I'm sure it can be caught during package creation stage. Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
