lang/python3* ports, __pycache__ included

Shane Ambler FreeBSD at ShaneWare.Biz
Wed Dec 14 06:30:19 UTC 2016


On 14/12/2016 00:42, Kyle Evans wrote:
> On Tue, Dec 13, 2016 at 4:59 AM, Kubilay Kocak <koobs at freebsd.org> wrote:
>>
>> 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.
>
> Yeah, I was aware of this -- my response to mva@ mentioned that
> runtime creation is ok. =) What I'm really trying to go for (and still
> working out the details -- still planning, decent amount of time
> before implementation), is going to have a small-disk constraint
> (Think < 1GB), but a decent amount of memory. What I *really* want to
> do that I haven't even started to work out the logistics on is
> effectively overlay this disk into memory with no writing back to
> disk. Something similar to a nullfs with copy-on-write semantics is
> what I was hoping for, but that doesn't seem to be easy to accomplish.

Sounds like you could use mdconfig to create a ram disk that is
writeable by the user and unionfs it over the non-writable fs

I haven't used it but man mount_unionfs says it is not fully supported
- there is sysutils/fusefs-unionfs that could be an option.

-- 
FreeBSD - the place to B...Software Developing

Shane Ambler



More information about the freebsd-python mailing list