Filipe Laíns <la...@riseup.net> added the comment:
> My biggest concern is with the bare "import _vendor_config", which I'd prefer
> to have restricted to a fixed location, rather than being influenced by
> environment variables and other options. We already have an issue with
> readline being imported from anywhere it can be found.
Oh, I share the same concern! Though users could already mess up Python pretty
badly by shadowing/overwriting parts of it, so I didn't thought it would be
that big of an issue. Is there a way to achieve this while still allowing us to
do everything we want?
> Sorry for not getting to this sooner, but 5 days is really tight for such a
> change.
No worries. It was my fault, I should have been more attentive to the Python
release timeline.
> With -S/-I, It would be great if sys.path only included packages installed as
> part of the OS, and not those installed by `sudo pip`. (Or `pip --user`, but
> that's covered).
Perhaps we could add an option to enable only vendor site schemes?
> It seems that with the current patch, pip will install into site-packages and
> there's no way to disable/change site-packages. Is that the case?
I mean, there is, though not as straightforward as -S/-I. I was planning on
using it to build the distro entrypoint scripts, so that they only include the
distro packages.
$ python -S
> site.addsitedir(sysconfig.get_path('purelib', 'vendor'))
> site.addsitedir(sysconfig.get_path('platlib', 'vendor'))
As I mentioned above, we could add a cli flag to do essentially the same.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue43976>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
