-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Krishvsoni patch 1 #486
Krishvsoni patch 1 #486
Conversation
@krishvsoni is attempting to deploy a commit to the Arc53 Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thank you for your contribution. If this change eventually will be accepted, please also add link to official Python documentation somewhere in your changes or aroud (https://docs.python.org/3/tutorial/venv.html) |
Official documentation added for virtual env |
From this I added the documentation link with the commands |
@holopin-bot @krishvsoni Thank you! |
Congratulations @krishvsoni, you just earned a badge! Here it is: https://holopin.io/claim/clngnlzq4134050fmnfdbtwk66 This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Codecov Report
@@ Coverage Diff @@
## main #486 +/- ##
=======================================
Coverage 17.50% 17.50%
=======================================
Files 59 59
Lines 2719 2719
=======================================
Hits 476 476
Misses 2243 2243 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
What kind of change does this PR introduce? - Docs Update
Why was this change needed? - Adding both activation commands (venv/Scripts/activate and . venv/bin/activate) is necessary to accommodate users on different operating systems (Windows, Unix-based) and provide clear, error-free instructions in the Readme markdown file.
Other information:
I initially attempted to use the default command . venv/bin/activate, but it didn't work for me. This prompted me to include the alternative venv/Scripts/activate command in the README for Windows users like me.