11# Byte-compiled / optimized / DLL files
22__pycache__ /
3- * .py [codz ]
3+ * .py [cod ]
44* $py.class
55
66# C extensions
@@ -25,6 +25,7 @@ share/python-wheels/
2525.installed.cfg
2626* .egg
2727MANIFEST
28+ _version.py
2829
2930# PyInstaller
3031# Usually these files are written by a python script from a template
@@ -45,8 +46,9 @@ htmlcov/
4546.cache
4647nosetests.xml
4748coverage.xml
49+ coverage.txt
4850* .cover
49- * .py. cover
51+ * .py, cover
5052.hypothesis /
5153.pytest_cache /
5254cover /
@@ -94,35 +96,20 @@ ipython_config.py
9496# install all needed dependencies.
9597# Pipfile.lock
9698
97- # UV
98- # Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
99- # This is especially recommended for binary packages to ensure reproducibility, and is more
100- # commonly ignored for libraries.
101- # uv.lock
102-
10399# poetry
104100# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
105101# This is especially recommended for binary packages to ensure reproducibility, and is more
106102# commonly ignored for libraries.
107103# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
108104# poetry.lock
109- # poetry.toml
110105
111106# pdm
112107# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
113- # pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
114- # https://pdm-project.org/en/latest/usage/project/#working-with-version-control
115108# pdm.lock
116- # pdm.toml
117- .pdm-python
118- .pdm-build /
119-
120- # pixi
121- # Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
122- # pixi.lock
123- # Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
124- # in the .venv directory. It is recommended not to include this directory in version control.
125- .pixi
109+ # pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
110+ # in version control.
111+ # https://pdm.fming.dev/#use-with-ide
112+ .pdm.toml
126113
127114# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
128115__pypackages__ /
@@ -136,8 +123,9 @@ celerybeat.pid
136123
137124# Environments
138125.env
139- .envrc
140126.venv
127+ .pyenv
128+ .testenv
141129env /
142130venv /
143131ENV /
@@ -175,33 +163,17 @@ cython_debug/
175163# option (not recommended) you can uncomment the following to ignore the entire idea folder.
176164# .idea/
177165
178- # Abstra
179- # Abstra is an AI-powered process automation framework.
180- # Ignore directories containing user credentials, local state, and settings.
181- # Learn more at https://abstra.io/docs
182- .abstra /
183-
184- # Visual Studio Code
185- # Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
186- # that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
187- # and can be added to the global gitignore or merged into this file. However, if you prefer,
188- # you could uncomment the following to ignore the entire vscode folder
189- # .vscode/
190-
191- # Ruff stuff:
192- .ruff_cache /
193-
194- # PyPI configuration file
195- .pypirc
196-
197- # Cursor
198- # Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
199- # exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
200- # refer to https://docs.cursor.com/context/ignore-files
201- .cursorignore
202- .cursorindexingignore
203-
204- # Marimo
205- marimo /_static /
206- marimo /_lsp /
207- __marimo__ /
166+ # VSCode settings
167+ .vscode /launch.json
168+
169+ # Ruff
170+ .ruff_cache
171+
172+ # pytest coverage
173+ pytest.xml
174+ pytest-coverage.txt
175+
176+ # artifacts
177+ artifacts
178+ # and tmp files
179+ tmp /
0 commit comments