1. In the Settings/Preferences dialog (Ctrl+Alt+S), select Project | Project Interpreter.

2. Expand the list of the available interpreters and click the Show All link.

3. Select the target interpreter. When PyCharm stops supporting any of the outdated Python versions, the corresponding project interpreter is marked as unsupported.

4. The Python interpreter name specified in the Name field, becomes visible in the list of available interpreters. Click OK to apply the changes.

For more info please check here

1. Open the Settings/Preferences dialog, and under the node Tools, click the page Python Integrated Tools.

2. On this page, click the Default Test Runner field.

3. Choose the desired test runner:

For more info please see Enable Pytest for you project

1. open CMD

2. navigate to project directory, for example

cd C:\Users\superadmin\Desktop\Python\CodinGame

3. run following command:

pip install virtualenv

4. run following command:

virtualenv venv --python=python

1. Install pip first

    sudo apt-get install python3-pip

2. Then install virtualenv using pip3

    sudo pip3 install virtualenv

3. Now create a virtual environment (>you can use any name insted of venv)

    virtualenv venv

4. You can also use a Python interpreter of your choice:

    virtualenv -p /usr/bin/python2.7 venv

5. Active your virtual environment:

    source venv/bin/activate

6. Using fish shell:

    source venv/bin/activate.fish

7. To deactivate:

    deactivate

8. Create virtualenv using Python3:

    virtualenv -p python3 myenv

9. Instead of using virtualenv you can use this command in Python3:

    python3 -m venv myenv

Source

In a newly created virtualenv there will be a bin/activate shell script. For Windows systems, activation scripts are provided for CMD.exe and Powershell.

1. Open Terminal

2. Run: \path\to\env\Scripts\activate

Source

Any application typically has a set of dependencies that are required for that application to work. The requirements file is a way to specify and install specific set of package dependencies at once.
Use pip’s freeze command to generate a requirements.txt file for your project:

pip freeze > requirements.txt

If you save this in requirements.txt, you can follow this guide: PyCharm - Manage dependencies using requirements.txt, or you can:

pip install -r requirements.txt

Source

1. Open Git Bash

2. Run: "git config --global http.postBuffer 157286400"

Source

Even if you haven't tracked the files so far, Git seems to be able to "know" about them even after you add them to .gitignore

NOTE:

• First commit your current changes, or you will lose them.
• Then run the following commands from the top folder of your Git repository:

git rm -r --cached .
git add .
git commit -m "fixed untracked files"

Step by step:

1. Run tests from pytest using following arguments: -v --alluredir=allure-results

2. Copy '.\allure-report\history' folder into '.\allure-results\history'

3. Run: allure generate .\allure-results\ -o .\allure-report\ --clean

4. Following output should appear: Report successfully generated to .\allure-report

5. Run: allure open .\allure-report\

Source

Step by step:

1. Create docs directory

2. Open cmd > Go to docs directory

3. cmd > Run: sphinx-quickstart. Note: run with default answers

4. Go to docs/conf.py

5. Uncomment following lines:

    import os
    import sys
    sys.path.insert(0, os.path.abspath('.'))

6. Update extensions list as following:

extensions = ['sphinx.ext.todo', 'sphinx.ext.viewcode', 'sphinx.ext.autodoc']

7. Update template as following:

html_theme = 'sphinx_rtd_theme'

8. Update sys.path.insert as following:

sys.path.insert(0, os.path.abspath('..'))

9. Go to docs/index.rst > add modules, see example below:

.. toctree::
   :maxdepth: 2
   :caption: Contents:

   modules

10. Open cmd > run:

sphinx-apidoc -o . ..

11. cmd > Run: make html

12. Install html template:

pip install sphinx_rtd_theme

Video Tutorial Sphinx Documentation More Info

Step by step:

1. Open CMD
2. Go to docs directory
3. Run: make clean
4. Run: sphinx-apidoc -o . ..
5. Add doc files name into relevant doc rst file
6. Run: make html

Source

The fix is to wipe out the build environment as follows (this is taken from here):

• Log in to read-the-docs
• Go to Versions
• Click on the Edit button of the version you want to wipe on the right side of the page
• Go to the bottom of the page and click the wipe link, next to the “Save” button
• Now you can re-build the version with a fresh build environment!

This fix worked for me (but as of 26-Jan-2020 you have to wipe out the environment for every build -- see comment from Grimmy below).

Source