On Fri, Jan 02, 2009 at 01:39:39PM -0500, Mike Meyer wrote: > Are you going to be the only group providing python modules, or in some > way do something to insure the quality of package so that you can make > sure that all python files are either 1) modules with a version-specific > path or 2) a script?
That's a rule that the ARC should enforce. We ought to formalize the rule, though. > Oh, and someone ought to check to see if a minor version upgrade > (i.e. - 2.4.2 to 2.4.5) might cause modules to be recompiled. Such > versions share libraries, and hence paths. Looks like the .pyc magic number is stable across micro (what you called minor) releases. It changed between 2.4 and 2.5, and again between 2.5 and 2.6, but only during development. (As determined by looking at the comment at the top of Python/import.c.) > It'd be nice if you delivered .pyo files as well. Is there any real advantage? As far as I can tell, it just eliminates assert statement and removes docstrings, neither of which seems all that useful. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
