%global _empty_manifest_terminate_build 0 Name: python-tox-envfile Version: 0.0.5 Release: 1 Summary: Load env files in your tox envs. License: BSD License URL: https://github.com/hypothesis/tox-envfile Source0: https://mirrors.aliyun.com/pypi/web/packages/e7/2f/a00140054f4503daa4511d4522783d575d7dba66d4b2f2a27147b651266d/tox-envfile-0.0.5.tar.gz BuildArch: noarch Requires: python3-dotenv %description [python-dotenv](https://saurabh-kumar.com/python-dotenv/) is used for the env file parsing. The `.devdata.env` file should be an env file with contents that look like this: ```shell # a comment that will be ignored. REDIS_ADDRESS=localhost:6379 MEANING_OF_LIFE=42 MULTILINE_VAR="hello\nworld" ``` Or like this: ```shell export S3_BUCKET=YOURS3BUCKET export SECRET_KEY=YOURSECRETKEYGOESHERE ``` POSIX variable expansion works, using variables from the environment or from earlier lines in the env file: ```shell CONFIG_PATH=${HOME}/.config/foo DOMAIN=example.org EMAIL=admin@${DOMAIN} ``` ## Setting up Your tox-envfile Development Environment First you'll need to install: * [Git](https://git-scm.com/). On Ubuntu: `sudo apt install git`, on macOS: `brew install git`. * [GNU Make](https://www.gnu.org/software/make/). This is probably already installed, run `make --version` to check. * [pyenv](https://github.com/pyenv/pyenv). Follow the instructions in pyenv's README to install it. The **Homebrew** method works best on macOS. The **Basic GitHub Checkout** method works best on Ubuntu. You _don't_ need to set up pyenv's shell integration ("shims"), you can [use pyenv without shims](https://github.com/pyenv/pyenv#using-pyenv-without-shims). Then to set up your development environment: ```terminal git clone https://github.com/hypothesis/tox-envfile.git cd tox_envfile make help ``` ## Releasing a New Version of the Project 1. First, to get PyPI publishing working you need to go to: and add tox-envfile to the `PYPI_TOKEN` secret's selected repositories. 2. Now that the tox-envfile project has access to the `PYPI_TOKEN` secret you can release a new version by just [creating a new GitHub release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository). Publishing a new GitHub release will automatically trigger [a GitHub Actions workflow](.github/workflows/pypi.yml) that will build the new version of your Python package and upload it to . ## Changing the Project's Python Versions To change what versions of Python the project uses: 1. Change the Python versions in the [cookiecutter.json](.cookiecutter/cookiecutter.json) file. For example: ```json "python_versions": "3.10.4, 3.9.12", ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request ## Changing the Project's Python Dependencies To change the production dependencies in the `setup.cfg` file: 1. Change the dependencies in the [`.cookiecutter/includes/setuptools/install_requires`](.cookiecutter/includes/setuptools/install_requires) file. If this file doesn't exist yet create it and add some dependencies to it. For example: ``` pyramid sqlalchemy celery ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request To change the project's formatting, linting and test dependencies: 1. Change the dependencies in the [`.cookiecutter/includes/tox/deps`](.cookiecutter/includes/tox/deps) file. If this file doesn't exist yet create it and add some dependencies to it. Use tox's [factor-conditional settings](https://tox.wiki/en/latest/config.html#factors-and-factor-conditional-settings) to limit which environment(s) each dependency is used in. For example: ``` lint: flake8, format: autopep8, lint,tests: pytest-faker, ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request %package -n python3-tox-envfile Summary: Load env files in your tox envs. Provides: python-tox-envfile BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-tox-envfile [python-dotenv](https://saurabh-kumar.com/python-dotenv/) is used for the env file parsing. The `.devdata.env` file should be an env file with contents that look like this: ```shell # a comment that will be ignored. REDIS_ADDRESS=localhost:6379 MEANING_OF_LIFE=42 MULTILINE_VAR="hello\nworld" ``` Or like this: ```shell export S3_BUCKET=YOURS3BUCKET export SECRET_KEY=YOURSECRETKEYGOESHERE ``` POSIX variable expansion works, using variables from the environment or from earlier lines in the env file: ```shell CONFIG_PATH=${HOME}/.config/foo DOMAIN=example.org EMAIL=admin@${DOMAIN} ``` ## Setting up Your tox-envfile Development Environment First you'll need to install: * [Git](https://git-scm.com/). On Ubuntu: `sudo apt install git`, on macOS: `brew install git`. * [GNU Make](https://www.gnu.org/software/make/). This is probably already installed, run `make --version` to check. * [pyenv](https://github.com/pyenv/pyenv). Follow the instructions in pyenv's README to install it. The **Homebrew** method works best on macOS. The **Basic GitHub Checkout** method works best on Ubuntu. You _don't_ need to set up pyenv's shell integration ("shims"), you can [use pyenv without shims](https://github.com/pyenv/pyenv#using-pyenv-without-shims). Then to set up your development environment: ```terminal git clone https://github.com/hypothesis/tox-envfile.git cd tox_envfile make help ``` ## Releasing a New Version of the Project 1. First, to get PyPI publishing working you need to go to: and add tox-envfile to the `PYPI_TOKEN` secret's selected repositories. 2. Now that the tox-envfile project has access to the `PYPI_TOKEN` secret you can release a new version by just [creating a new GitHub release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository). Publishing a new GitHub release will automatically trigger [a GitHub Actions workflow](.github/workflows/pypi.yml) that will build the new version of your Python package and upload it to . ## Changing the Project's Python Versions To change what versions of Python the project uses: 1. Change the Python versions in the [cookiecutter.json](.cookiecutter/cookiecutter.json) file. For example: ```json "python_versions": "3.10.4, 3.9.12", ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request ## Changing the Project's Python Dependencies To change the production dependencies in the `setup.cfg` file: 1. Change the dependencies in the [`.cookiecutter/includes/setuptools/install_requires`](.cookiecutter/includes/setuptools/install_requires) file. If this file doesn't exist yet create it and add some dependencies to it. For example: ``` pyramid sqlalchemy celery ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request To change the project's formatting, linting and test dependencies: 1. Change the dependencies in the [`.cookiecutter/includes/tox/deps`](.cookiecutter/includes/tox/deps) file. If this file doesn't exist yet create it and add some dependencies to it. Use tox's [factor-conditional settings](https://tox.wiki/en/latest/config.html#factors-and-factor-conditional-settings) to limit which environment(s) each dependency is used in. For example: ``` lint: flake8, format: autopep8, lint,tests: pytest-faker, ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request %package help Summary: Development documents and examples for tox-envfile Provides: python3-tox-envfile-doc %description help [python-dotenv](https://saurabh-kumar.com/python-dotenv/) is used for the env file parsing. The `.devdata.env` file should be an env file with contents that look like this: ```shell # a comment that will be ignored. REDIS_ADDRESS=localhost:6379 MEANING_OF_LIFE=42 MULTILINE_VAR="hello\nworld" ``` Or like this: ```shell export S3_BUCKET=YOURS3BUCKET export SECRET_KEY=YOURSECRETKEYGOESHERE ``` POSIX variable expansion works, using variables from the environment or from earlier lines in the env file: ```shell CONFIG_PATH=${HOME}/.config/foo DOMAIN=example.org EMAIL=admin@${DOMAIN} ``` ## Setting up Your tox-envfile Development Environment First you'll need to install: * [Git](https://git-scm.com/). On Ubuntu: `sudo apt install git`, on macOS: `brew install git`. * [GNU Make](https://www.gnu.org/software/make/). This is probably already installed, run `make --version` to check. * [pyenv](https://github.com/pyenv/pyenv). Follow the instructions in pyenv's README to install it. The **Homebrew** method works best on macOS. The **Basic GitHub Checkout** method works best on Ubuntu. You _don't_ need to set up pyenv's shell integration ("shims"), you can [use pyenv without shims](https://github.com/pyenv/pyenv#using-pyenv-without-shims). Then to set up your development environment: ```terminal git clone https://github.com/hypothesis/tox-envfile.git cd tox_envfile make help ``` ## Releasing a New Version of the Project 1. First, to get PyPI publishing working you need to go to: and add tox-envfile to the `PYPI_TOKEN` secret's selected repositories. 2. Now that the tox-envfile project has access to the `PYPI_TOKEN` secret you can release a new version by just [creating a new GitHub release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository). Publishing a new GitHub release will automatically trigger [a GitHub Actions workflow](.github/workflows/pypi.yml) that will build the new version of your Python package and upload it to . ## Changing the Project's Python Versions To change what versions of Python the project uses: 1. Change the Python versions in the [cookiecutter.json](.cookiecutter/cookiecutter.json) file. For example: ```json "python_versions": "3.10.4, 3.9.12", ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request ## Changing the Project's Python Dependencies To change the production dependencies in the `setup.cfg` file: 1. Change the dependencies in the [`.cookiecutter/includes/setuptools/install_requires`](.cookiecutter/includes/setuptools/install_requires) file. If this file doesn't exist yet create it and add some dependencies to it. For example: ``` pyramid sqlalchemy celery ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request To change the project's formatting, linting and test dependencies: 1. Change the dependencies in the [`.cookiecutter/includes/tox/deps`](.cookiecutter/includes/tox/deps) file. If this file doesn't exist yet create it and add some dependencies to it. Use tox's [factor-conditional settings](https://tox.wiki/en/latest/config.html#factors-and-factor-conditional-settings) to limit which environment(s) each dependency is used in. For example: ``` lint: flake8, format: autopep8, lint,tests: pytest-faker, ``` 2. Re-run the cookiecutter template: ```terminal make template ``` 3. Commit everything to git and send a pull request %prep %autosetup -n tox-envfile-0.0.5 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-tox-envfile -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Jun 09 2023 Python_Bot - 0.0.5-1 - Package Spec generated