Virtualenvs have `sys.base_prefix`, so perhaps they could just check whether the key exists for their parent environment?
-Robert On Tue, Jan 26, 2016 at 1:37 PM, Nathaniel Smith <[email protected]> wrote: > On Jan 26, 2016 1:04 PM, "Robert T. McGibbon" <[email protected]> wrote: > > > > The file pip uses to record its latest check for being out of date (on > linux ~/.cache/pip/selfcheck.json) is a json file that maps the path to the > interpreter's sys.prefix to some metadata about the installation > > > > e.g. > > > > {"/home/rmcgibbo/opt/python-3.5/": > {"last_check":"2016-01-12T00:09:02Z","pypi_version":"7.1.2"}, ...} > > > > Perhaps a similar model should be used for > /etc/python/compatibility.cfg. That is, the configuration option should be > keyed on a per-interpreter basis. > > > > [/usr] > > manylinux1 compatible = true > > > > [/path/to/armv7l/python] > > manylinux1 compatible = false > > Interesting idea. Any thoughts on how to propagate this information from > parent envs into virtualenvs? > > -n > -- -Robert
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
