On 12/13/2016 12:55:40 PM, "Vlad K." <vlad-f...@acheronmedia.com> wrote:
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?
Some systems require very strong audit rules, while stuff is run with
privileged permissions. In reality, this does not
matter that much in most of the cases (read-only mounts), but
nevertheless, it'd be a nice thing to have.
Cheers
Marcus
_______________________________________________
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"
