On 13/12/2016 9:13 AM, Kyle Evans wrote: > On Mon, Dec 12, 2016 at 3:51 PM, Marcus von Appen <m...@freebsd.org> > wrote: >> Hi Kyle, >> >>> [snip] >> >> this is a python3 specific change in how python deals with >> optimized bytecode files. We ship .pyc/.pyo files for python2 ports >> and __pycache__ bits for python3, so there is no change in >> packaging behaviour except from "sticking to the default". > > Ahh, ok, that makes sense. > >>> [snip] >> >> Few years ago, we already had an idea about that. You can read it >> at https://wiki.freebsd.org/Python/CompiledPackages. If space is a >> major concern for you (but a small drawback in runtime performance >> is not), let us know, so we put it up on the agenda (again). > > In some of my environments, it definitely is a concern. In one or > two applications, I have limited disk size to work with but a lot of > memory to otherwise operate on -- so these things being created at > runtime isn't much issue, but having them on disk tends towards > problematic. > > Given that this is not a very 'black or white' problem (as evident > from the CompiledPackages wiki page), I will strip these entries > from the pkg-plist myself for the time being and maybe work on > finding time to assist in a better solution for the whole.
Note that they will be re-created on import unless one overrides the default for the interpreter to produce these optimization files. I'm not sure (or cant remember) if there is a good way to disable this on a global or system-wide basis. I second Marcus's comment that being able to not have to package optimized files and have them be created (optionally?) at package post-install time instead, would be a good thing overall TM. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
