Byte-compiled / optimized / DLL files
pycache /
*.py[codz]
*$py.class
*.so
.Python
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST
Usually these files are written by a python script from a template
before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec
pip-log.txt
pip-delete-this-directory.txt
Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py.cover
.hypothesis/
.pytest_cache/
cover/
*.mo
*.pot
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal
instance/
.webassets-cache
.scrapy
docs/_build/
.pybuilder/
target/
.ipynb_checkpoints
profile_default/
ipython_config.py
For a library or package, you might want to ignore these files since the code is
intended to run in multiple environments; otherwise, check them in:
According to pypa/pipenv#598 , it is recommended to include Pipfile.lock in version control.
However, in case of collaboration, if having platform-specific dependencies or dependencies
having no cross-platform support, pipenv may install dependencies that don't work, or not
install all needed dependencies.
Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
This is especially recommended for binary packages to ensure reproducibility, and is more
commonly ignored for libraries.
Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
This is especially recommended for binary packages to ensure reproducibility, and is more
commonly ignored for libraries.
Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
.pdm-python
.pdm-build/
Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
in the .venv directory. It is recommended not to include this directory in version control.
.pixi
PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
pypackages /
celerybeat-schedule
celerybeat.pid
*.rdb
*.aof
*.pid
mnesia/
rabbitmq/
rabbitmq-data/
activemq-data/
*.sage.py
.env
.envrc
.venv
env/
venv/
ENV/
env.bak/
venv.bak/
.spyderproject
.spyproject
.ropeproject
/site
.mypy_cache/
.dmypy.json
dmypy.json
.pyre/
pytype static type analyzer
.pytype/
cython_debug/
JetBrains specific template is maintained in a separate JetBrains.gitignore that can
and can be added to the global gitignore or merged into this file. For a more nuclear
option (not recommended) you can uncomment the following to ignore the entire idea folder.
Abstra is an AI-powered process automation framework.
Ignore directories containing user credentials, local state, and settings.
.abstra/
Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
and can be added to the global gitignore or merged into this file. However, if you prefer,
you could uncomment the following to ignore the entire vscode folder
Temporary file for partial code execution
tempCodeRunnerFile.py
.ruff_cache/
.pypirc
marimo/_static/
marimo/_lsp/
marimo /
.streamlit/secrets.toml