> After last update, python32 port started byte-compiling foo.py into
> foo.cpython-32.pyc instead of predictable foo.pyc. This broke a
> non-trivial number of ports on plists.
>
> How do you propose we proceed fixing this?
>
> --
> --
> Pav Lucistnik
>
Are this problem solved?
After last update, python32 port started byte-compiling foo.py into
foo.cpython-32.pyc instead of predictable foo.pyc. This broke a
non-trivial number of ports on plists.
How do you propose we proceed fixing this?
--
--
Pav Lucistnik
Pilot to Co-Pilot: Boo.
signature.asc
Descr