Windows-friendly project setup
Closed this issue · 4 comments
Summary
pipenv has been difficult to set up quickly, especially on Windows. Should try to be fixed using a fresh virtual machine.
What is the expected correct behavior?
A quick and seamless setup with pipenv readily available on the terminal.
Steps to reproduce
Following pip, Pipfiles, and Pipenv.
Tasks
People to setup:
- Setup @AyushJain2021
- Setup @jessed7
- Setup @jasonbm2
- Setup @luongp134
Steps:
- Uninstall Debian
- Ensure their Git credentials work
- Setup pipenv with Scripts in PATH
Relevant logs and/or screenshots
N/A
Operating System
Windows
Browser
Other
Need to add to PATH. To check where your installation is, run python on the terminal and type something like:
import pipenv
pipenv.__file__Copy the entire path up until /Python312/Scripts, and add this to PATH. After this, pipenv should work fine
Requirements:
- Install
pip - Install
pipenv - Add Python's Scripts file to PATH
- When you clone the repo, make sure to also have Python 3.11 installed
- Install the PyGObject dependencies
- Run
pipenv install
May 9 2024 Updates:
Windows users can now run pipenv from the terminal without having to prepend python -m, but when they run pipenv install, coverage and pytest do not work. pipenv install doesn't seem to do anything either. Will investigate soon.
Removing from milestone 1 as it is not a pressing issue as of now. Workaround is installing with pip:
pip install coverage pytest