Wouter Vanden Hove

Pillow is the only exception I've come across so far where that was intentionally violating this rule. Pillow is indeed was fully compatible drop-in replacement for PIL. On the other...

Give my example above, I would indeed like to see corrections in new releases: ``` >>> import dotenv >>> import django_dotenv >>> import python_dotenv ``` Semantic versioning can flag the...

I guess there are no Pypi-classifiers to indicate a package is a compatible drop-in replacement for another package?

I wonder why any hardcoding names are needed. Just because a random folder is called ".venv" it is assumed a python virtualenv? Why not checking on the presence of "pyvenv.cfg"...

@zanieb how are you supposed to install a package when using a non-standard venv-name? .venv is only used in an actual development-project. ``` uv venv foo cd foo ? ```

> We don't want to scan every directory in your current directory on every invocation, . That is a small performance-hit i'm very happy to endure, compared to setting an...

from https://github.com/astral-sh/uv/issues/1495#issuecomment-1950793228 I have a solution for my use-case: symlink the foo-folder to a .venv-subfolder ``` uv venv foo cd foo ln -s . .venv uv pip install ``` @jkomalley...

> I have a solution for my use-case: symlink the foo-folder to a .venv-subfolder > uv venv foo > cd foo > ln -s . .venv > uv pip install...

@henryiii , Yes, corrected.

There is no version info in the pip-entrypoint. ``` > cat pip | pip3 | pip3.10 #!/tmp/foo/bin/python # -*- coding: utf-8 -*- import re import sys from pip._internal.cli.main import main...