Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] The documentation is missing important commands and specific steps needed to run the necessary commands correctly. #820

Open
1 task done
Dev-JoyA opened this issue Oct 6, 2024 · 3 comments · May be fixed by #834
Assignees
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@Dev-JoyA
Copy link
Contributor

Dev-JoyA commented Oct 6, 2024

Description

The documentation states that a Python environment must be created, but it lacks specific commands to guide users through this process. This absence of information can impede the development workflow, as users may struggle to set up their environment correctly.

Additionally, if Python 3.11 is not installed on a user's system (or if pipenv is unable to locate it), they might need to specify the Python path. However, the documentation does not currently address the necessary steps or alternatives if Python 3.11 is present instead.

Reproduction

  1. Open the open source repository.
  2. Go to the README file , find the Installing Project Requirements sub heading.
  3. There is a requirement to create python virtual environment, but the command is missing.

Expectation

I expected the documentation to provide clear and detailed commands for creating a Python environment, ensuring users could easily set it up. This clarity would help prevent confusion and ensure a smooth development process, allowing all team members to quickly get started with the project without facing setup issues.

Resolution

  • I would be interested in resolving this bug.
@Dev-JoyA Dev-JoyA added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Oct 6, 2024
@TimidRobot TimidRobot self-assigned this Oct 7, 2024
@TimidRobot TimidRobot added 🟩 priority: low Low priority and doesn't need to be rushed ⛔️ status: discarded Will not be worked on and removed 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 7, 2024
@TimidRobot
Copy link
Member

TimidRobot commented Oct 7, 2024

⛔️ status: discarded Will not be worked on :

@Dev-JoyA
Copy link
Contributor Author

Dev-JoyA commented Oct 7, 2024

@TimidRobot the command to create a virtual environment is this
pipenv --python 3.12

Also there is need to know the version of python the user uses by running
python --version

This two command is not included in the documentation and its a necessary step for installation

This command is for installing requirement for the project
pipenv install --dev

and without this
pipenv --python 3.12
it wont work

@TimidRobot TimidRobot added help wanted Open to participation from the community 🏁 status: ready for work Ready for work and removed ⛔️ status: discarded Will not be worked on labels Oct 7, 2024
@TimidRobot
Copy link
Member

@Dev-JoyA thank you for the additional information.

The Python version (3.11) is defined in the Pipefile.

If there's no Python 3.11 on your system (or if pipenv can't find it), you may need to specify the Python location. For example:

 pipenv install --dev --python /opt/homebrew/bin/python3.11

Adding a sub-bullet to the README might be helpful. Please update this issue description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Archived in project
2 participants