On 2016-12-13 12:36, Kubilay Kocak wrote:
My main point was that if disk utilisation is something one wants to minimise (at deployment), that one would need to be able to turn the optimization knob off each time (or system-wide) and that that would be a handy thing to know and do.
Personally, I'd love if Python could specify a base dir for bytecode cache, but it seems that's not gonna happen:
https://www.python.org/dev/peps/pep-0304/
Said another way, even if we (FreeBSD) de-packaged optimization files which we want to do, that that *by itself* that would only save package repository size and bandwidth, not deployment size.
But in reality, what kind of gain/loss are we talking about here? I'm guessing it's pretty insignificant in this day and age, even for embedded?
-- Vlad K. _______________________________________________ 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"
