Possible to `pip install .`?
See original GitHub issueI see the changes in https://github.com/python-versioneer/python-versioneer/commit/7776ee06b669b85c52a1fd0f6ad9c5a6a79c3904
which imply that it is still not possible to get a version from git when running pip install .
. Is this true? Is there a workaround / known solution to this issue? I guess the core of the issue is that pip
doesn’t copy over the .git
folder to the temporary directory, and so maybe this is simply impossible?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Installing Packages - Python Packaging User Guide - Python.org
Requirements for Installing Packages. Ensure you can run Python from the command line. Ensure you can run pip from the command line ·...
Read more >How to Install a Package in Python using PIP - Data to Fish
If you're using Windows, you'll be able to install a Python package by opening the Windows Command Prompt, and then typing this command:...
Read more >Installation - pip documentation v22.3.1
If your Python environment does not have pip installed, there are 2 mechanisms to install pip supported directly by pip's maintainers: ensurepip. get-pip.py ......
Read more >How to Install Pip on Windows - ActiveState
How to Install Pip on Windows · Check if pip is already installed by running the following on the command line: · Verify...
Read more >Pip Install: Install and Remove Python Packages
Python : Install Pip · Pip Install Python packages · Pip install requirements.txt file · Custom repository with pip install -i · Editable...
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
I’m having this problem with both
pip install .
andpip install -e .
This should be fixed.
For vendored builds, using
build-backend = "setuptools.build_meta:__legacy__"
should work, or addingsys.path.append(".")
in yoursetup.py
. For non-vendored builds, addingversioneer >= 0.24
to yourrequires
list should work.