pipxclip 4.1.1__tar.gz

pipxclip-4.1.1/.gitattributes

@@ -0,0 +1,2 @@
+*.gif filter=lfs diff=lfs merge=lfs -text
+*.webp filter=lfs diff=lfs merge=lfs -text

pipxclip-4.1.1/.gitignore

@@ -0,0 +1,220 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   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
+
+# Installer logs
+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
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   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:
+# .python-version
+
+# pipenv
+#   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.
+# Pipfile.lock
+
+# UV
+#   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.
+# uv.lock
+
+# poetry
+#   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.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   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.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   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/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   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.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/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
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

pipxclip-4.1.1/AGENTS.md

@@ -0,0 +1 @@
+Do not make mistakes.

pipxclip-4.1.1/CONTRIBUTING.md

@@ -0,0 +1,132 @@
+# Contributing
+
+Thanks for considering contributing! We welcome all quality contributions, including AI-generated PRs.
+
+## Quick Guidelines
+
+- **New Features:** Please submit an Issue tagged with the `enhancement` label before opening a Pull Request so we can discuss it first.
+- **Small Fixes & Bugs:** Feel free to open a Pull Request directly!
+
+Welcome! This guide will walk you through setting up your environment, running tests, making code changes, and contributing to the project step-by-step.
+
+## Prerequisites
+
+Make sure you have **Python 3.8+** and `pip` installed on your system.
+
+## Step 1: Set Up Your Environment
+
+Using a virtual environment keeps this project's dependencies isolated from the rest of your system.
+
+### Linux & macOS (Bash / Zsh)
+
+Open your terminal in the root directory of the project and run:
+
+```bash
+# 1. Create a virtual environment named 'venv'
+python3 -m venv venv
+
+# 2. Activate the environment
+source venv/bin/activate
+```
+
+### Windows
+
+Open your terminal in the root directory of the project and run the commands for your shell:
+
+#### Option A: PowerShell
+
+```powershell
+# 1. Create the virtual environment
+python -m venv venv
+
+# 2. Activate the environment
+.\venv\Scripts\Activate.ps1
+```
+
+> **PowerShell Script Error?** If you receive a script execution policy error when activating, run `Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process` in your session, then try activating again.
+
+#### Option B: Command Prompt (CMD)
+
+```cmd
+:: 1. Create the virtual environment
+python -m venv venv
+
+:: 2. Activate the environment
+venv\Scripts\activate.bat
+```
+
+---
+
+- **Verify activation:** Your terminal prompt will display `(venv)` at the start of the line.
+- **Exit the environment:** Type `deactivate` in your terminal when you are finished.
+
+## Step 2: Install the Package & Development Dependencies
+
+To contribute code, you need to install the project in **editable mode** alongside development tools (like `pytest`).
+
+Run the following command in your activated environment:
+
+```bash
+pip install -e ".[dev]"
+```
+
+> **Note:** The `-e` flag ("editable") ensures that any code changes you make locally are reflected immediately without needing to reinstall the package.
+
+## Step 3: Making Changes & Development Workflow
+
+Follow this general workflow when adding features or fixing bugs:
+
+### 1. Create a New Branch
+
+Keep your work organized by creating a dedicated git branch for your feature or fix:
+
+```bash
+git checkout -b feature/my-new-feature
+```
+
+### 2. Make Your Code Edits
+
+Modify or add files inside the project repository using your preferred code editor.
+
+### 3. Add Tests for Your Changes
+
+If you are adding a feature or fixing a bug, add corresponding tests inside the `tests/` directory to ensure long-term stability.
+
+## Step 4: Run the Tests
+
+Before committing your changes, run the test suite to make sure everything passes without breaking existing functionality.
+
+```bash
+pytest
+```
+
+### Useful Pytest Options:
+
+- Run a specific test file: `pytest tests/test_filename.py`
+- Stop on the first failure: `pytest -x`
+- Show verbose output: `pytest -v`
+
+## Step 5: Submitting Your Contribution
+
+1. **Stage and commit your changes:**
+
+   ```bash
+   git add .
+   git commit -m "Add short, descriptive summary of changes"
+   ```
+
+2. **Push your branch to GitHub:**
+
+   ```bash
+   git push origin feature/my-new-feature
+   ```
+
+3. **Open a Pull Request (PR):** Navigate to the project's repository on GitHub and click **Compare & pull request** to submit your changes for code review!
+
+## Troubleshooting & FAQ
+
+| Issue                          | Solution                                                                                  |
+| :----------------------------- | :---------------------------------------------------------------------------------------- |
+| **`pytest` is not recognized** | Ensure your virtual environment `(venv)` is active and you ran `pip install -e ".[dev]"`. |
+| **`python` command not found** | Try using `python3` instead, or verify Python is added to your system `PATH`.             |
+| **Changes not showing up**     | Verify that `(venv)` is active and that the package was installed with the `-e` flag.     |