Speculative: `--require-venv` by default
See original GitHub issueThis is somewhat of an offshoot from #1668, PEP 668 and a bunch more issues around the way pip interacts with the system.
One somewhat disruptive way we can handle this, that is roughly in the same order of magnitude as #9140, is requiring a virtualenv to be active to install things.
This means that we’d need to add in --no-require-venv
(oh, I think we have that already).
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:15 (12 by maintainers)
Top Results From Across the Web
The U.S. Speculative-Grade Corporate Default Rate Could ...
We expect the U.S. trailing-12-month speculative-grade corporate default rate to reach 3.75% by September 2023, from 1.6% in September 2022.
Read more >Speculative Store Bypass explained: what it is, how it works
In this post, I'm going to explain the Speculative Store Bypass CVE. ... Thus the logic required to search the store buffer is...
Read more >Windows guidance to protect against speculative execution ...
Provides guidance for Windows Server to protect against an L1 terminal fault (LITF) attack.
Read more >pragma--speculative sections----+--------+-+ ... - IBM
The speculative sections directive instructs the compiler to speculatively ... Specifying default (none) requires that each data variable visible to the ...
Read more >Best Practices for Enabling Speculative Execution on Large ...
Apache Spark has the 'speculative execution' feature to handle the slow tasks in a stage due to environment issues like slow network, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Even on Linux there are many ways to install a standalone Python beyond Conda - from building Python from source to various distributions (e.g., Enthought Distribution Manager, ActiveState Python). And then Nix, Spack, etc.
Rather than try to detect a conda env, it’d be better to turn this around: refuse only when one sees a system Python.
OK, I don’t like how pressing enter on the phone submitted this issue.