%global _empty_manifest_terminate_build 0 Name: python-pytest-dotenv Version: 0.5.2 Release: 1 Summary: A py.test plugin that parses environment files before running tests License: MIT License URL: https://github.com/quiqua/pytest-dotenv Source0: https://mirrors.nju.edu.cn/pypi/web/packages/cd/b0/cafee9c627c1bae228eb07c9977f679b3a7cb111b488307ab9594ba9e4da/pytest-dotenv-0.5.2.tar.gz BuildArch: noarch Requires: python3-pytest Requires: python3-dotenv %description # pytest-dotenv This little plugin uses `python-dotenv` to load any environment variables from a `.env` file. Extra configuration can be defined in any `pytest` config files, such as `pytest.ini`, `tox.ini` and so on. ## Installation Install the plugin with `pip`: ``` $ pip install pytest-dotenv ``` ## Basic Usage If all you want is to load environment variables from a `.env` file then installing the plugin is all that is needed. `python-dotenv` will automatically detect your `.env` file and load it. By default, the plugin won't override any existing system variables. ## Non-default configuration ### Custom Environment Variable Files Add a new section to a config file named `env_vars`. You can list as many files as necessary: ``` [pytest] env_files = .env .test.env .deploy.env ``` The files will be loaded and added to the `os.environ` dict object before any tests are run. If the files are not found on the working directory, it will search for the files in the ancestor directory and upwards. ### Overriding Existing Values By default the plugin will not override any variables already defined in the process' environment. If you want that behavior, you have to use the `env_override_existing_values` setting: ``` [pytest] env_override_existing_values = 1 env_files = .env .test.env .deploy.env ``` ### Alternative: Specify the file at the command line You also have the option to run your tests with `py.test --envfile path/to/.env`. This will load all defined environment variables and overwrite any existing ones regardless of the configuration `env_override_existing_values`. %package -n python3-pytest-dotenv Summary: A py.test plugin that parses environment files before running tests Provides: python-pytest-dotenv BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-pytest-dotenv # pytest-dotenv This little plugin uses `python-dotenv` to load any environment variables from a `.env` file. Extra configuration can be defined in any `pytest` config files, such as `pytest.ini`, `tox.ini` and so on. ## Installation Install the plugin with `pip`: ``` $ pip install pytest-dotenv ``` ## Basic Usage If all you want is to load environment variables from a `.env` file then installing the plugin is all that is needed. `python-dotenv` will automatically detect your `.env` file and load it. By default, the plugin won't override any existing system variables. ## Non-default configuration ### Custom Environment Variable Files Add a new section to a config file named `env_vars`. You can list as many files as necessary: ``` [pytest] env_files = .env .test.env .deploy.env ``` The files will be loaded and added to the `os.environ` dict object before any tests are run. If the files are not found on the working directory, it will search for the files in the ancestor directory and upwards. ### Overriding Existing Values By default the plugin will not override any variables already defined in the process' environment. If you want that behavior, you have to use the `env_override_existing_values` setting: ``` [pytest] env_override_existing_values = 1 env_files = .env .test.env .deploy.env ``` ### Alternative: Specify the file at the command line You also have the option to run your tests with `py.test --envfile path/to/.env`. This will load all defined environment variables and overwrite any existing ones regardless of the configuration `env_override_existing_values`. %package help Summary: Development documents and examples for pytest-dotenv Provides: python3-pytest-dotenv-doc %description help # pytest-dotenv This little plugin uses `python-dotenv` to load any environment variables from a `.env` file. Extra configuration can be defined in any `pytest` config files, such as `pytest.ini`, `tox.ini` and so on. ## Installation Install the plugin with `pip`: ``` $ pip install pytest-dotenv ``` ## Basic Usage If all you want is to load environment variables from a `.env` file then installing the plugin is all that is needed. `python-dotenv` will automatically detect your `.env` file and load it. By default, the plugin won't override any existing system variables. ## Non-default configuration ### Custom Environment Variable Files Add a new section to a config file named `env_vars`. You can list as many files as necessary: ``` [pytest] env_files = .env .test.env .deploy.env ``` The files will be loaded and added to the `os.environ` dict object before any tests are run. If the files are not found on the working directory, it will search for the files in the ancestor directory and upwards. ### Overriding Existing Values By default the plugin will not override any variables already defined in the process' environment. If you want that behavior, you have to use the `env_override_existing_values` setting: ``` [pytest] env_override_existing_values = 1 env_files = .env .test.env .deploy.env ``` ### Alternative: Specify the file at the command line You also have the option to run your tests with `py.test --envfile path/to/.env`. This will load all defined environment variables and overwrite any existing ones regardless of the configuration `env_override_existing_values`. %prep %autosetup -n pytest-dotenv-0.5.2 %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-pytest-dotenv -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Mon Apr 10 2023 Python_Bot - 0.5.2-1 - Package Spec generated