Metadata-Version: 2.1
Name: venv-autouse
Version: 0.0.2
Summary: Handling venv for different scripts
Project-URL: Homepage, https://github.com/xonqnopp/python-venv-autouse
Project-URL: Issues, https://github.com/xonqnopp/python-venv-autouse/issues
Author-email: XonqNopp <xonqnoppp@gmail.com>
Maintainer-email: XonqNopp <xonqnoppp@gmail.com>
License: MIT License
        
        Copyright (c) 2024 XonqNopp
        
        Permission is hereby granted, free of charge, to any person obtaining a copy
        of this software and associated documentation files (the "Software"), to deal
        in the Software without restriction, including without limitation the rights
        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
        copies of the Software, and to permit persons to whom the Software is
        furnished to do so, subject to the following conditions:
        
        The above copyright notice and this permission notice shall be included in all
        copies or substantial portions of the Software.
        
        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
        SOFTWARE.
License-File: LICENSE
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Requires-Python: >=3.9
Description-Content-Type: text/x-rst

Python venv-autouse
###################

.. .. image:: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml/flake8-badge.svg
   :target: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml

.. image:: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml/badge.svg
   :target: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml

.. .. image:: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml/tests-badge.svg
   :target: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml

.. .. image:: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml/coverage-badge.svg
   :target: https://github.com/XonqNopp/python-venv-autouse/actions/workflows/python-package.yml

|

.. image:: https://img.shields.io/pypi/pyversions/venv-autouse.svg
    :target: https://pypi.org/project/venv-autouse/

.. image:: https://img.shields.io/pypi/v/venv-autouse
   :target: https://pypi.org/project/venv-autouse/


This package helps managing venv in different locations for different scripts.
You don't have to manually care about calling a script with the according venv.
All you need is provide a requirements file and import this module in the files which require the venv.
This module needs to be installed system-wide or in every venv you use to call files.
However, if you are executing files from within a venv, you will loose the current venv.

The versioning follows `semantic versioning <http://semver.org>`_.
