On Wed, Dec 31, 2008 at 02:30:21PM -0600, Shawn Walker wrote: > Or we could just "keep it simple" and deliver the pyc files as we are > now. All of these solutions sound technically neat, and at the same > time overly complicated.
My understanding was that two different versions of Python trying to import the same .py's will want to create competing .pyc's. That is a problem. And so is the fact that /usr is generally not writable by users. And then you need to get third parties to follow your lead. Yes, this only means that you lose the benefits of caching for some versions of Python. Not a big deal. I don't see how this is not a problem for Python, rather than for IPS. My suggestion was intended as a fix for Python, not for IPS. That said: if we continue to ship .pyc files and there's any chance that Python will overwrite them, then IPS does have a problem, one that perhaps should be fixed by ensuring that IPS has a notion of volatile files with initial contents. > The upside to creating these files on the fly would be a slight decrease > in bandwidth usage, etc. The downside would be the appearance that all > Python applications run slower on OpenSolaris (the first time) or always > (if run from the LiveCD). The other downside would be that OpenSolaris > would be the only one that does it differently than "everyone else" (as > far as I know). But perhaps everyone else should do this differently too. > I'd rather just deal with the timestamp in the pyc files and be done > with it. Are you sure that won't cause other problems? Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
