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
run (import is enough as you
say) those modules as root, because the cache is written in the module
package directory.
So pre-packaging the bytecode is a form of optimization, as the bytecode
will be there when you run it as an unprivileged user.
--
Vlad K
that
still, in 2016, required PHP <5.3
--
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"
an
go py3 to go py3, and build py2 in support for rdeps that require 2.
Because right now it's a bit of a mess when you have such conflicting
requirements.
--
Vlad K.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailma
that fail, to have a list of ports that:
a) Have USE= python but fail on 3
b) Have USE= python:2 but are actually supported on 3
But I need to get that poudriere running with a public status page for
that.
--
Vlad K.
___
freebsd-python@freebsd.org
admittedly limited) use case supports it
just fine. Python, uwsgi, nginx, PostgreSQL, Sphinx, etc...
I'm hoping this will help speed up bringing Python 3.x default to
FreeBSD.
--
Vlad K.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.o
