Saravanan666/pypi-org huggingface dataset:
Package: tow-slack-plog
tow-slack-plog.. image::https://img.shields.io/pypi/pyversions/tow-slack-plog.svg?maxAge=2592000?style=flat-square:target:https://pypi.python.org/pypi/tow-slack-plogPython logging handler for Slack webhook integration with simple configuration.Installation.. code-block:: bashpip install tow-slack-plogExampleSimple
''''''
.. code-block:: pythonimport logging
from slack_plog import SlackPlogsh = SlackPlog('YOUR_WEB_HOOK_URL') # url is like 'https://hooks.slack.com/...'
logging.basicConfig(handlers=[sh])
logging.warning('warn message')Using logger
''''''''''''
.. code-block:: pythonimport logging
from slack_plog import SlackPloglogger = logging.getLogger(name)
logger.setLevel(logging.DEBUG)sh = SlackPlog(slack_webhook_url='YOUR_WEB_HOOK_URL')
sh.setLevel(logging.DEBUG)logger.addHandler(sh)logger.debug('debug message')
logger.info('info message')
logger.warn('warn message')
logger.error('error message')
logger.critical('critical message')
Package: tox
toxtoxaims to automate and standardize testing in Python. It is part of a larger vision of easing the packaging, testing
and release process of Python software (alongsidepytestanddevpi).tox is a generic virtual environment management and test command line tool you can use for:checking your package builds and installs correctly under different environments (such as different Python
implementations, versions or installation dependencies),running your tests in each of the environments with the test tool of choice,acting as a frontend to continuous integration servers, greatly reducing boilerplate and merging CI and shell-based
testing.Please read ouruser guidefor an example and more detailed
introduction, or watchthis YouTube videothat presents the problem space
and how tox solves it.
Package: tox21full
This is a Tox21-like dataset created from the raw NIH assay data. The Tox21 dataset we know and love only includes 12 assays. This one includes 64 different assays!Simply by using this dataset you can train machine learning models with metrics you never thought was possible.Downloads NIH raw assay data and creates a clean CSV.GZ file ready for import into pandas:tox21full ~/Downloads/tox21full.csv.gzYou can also create it as a parquet file (more efficent):tox21full --format parquet ~/Downloads/tox21full.parquet
Package: tox2travis
tox2travisAfter installing, simply calltox2travisin a directory that
contains atox.inifile. A.travis.ymlfile will be generated.tox2traviswill be able to map environment names using tox'sdefault
environmentsto the correct python version on Travis automatically.Non-standard environment namesIf an environment name does not match one of the default environments
provided by tox, tox2travis will simply ignore it. To specify a python
version for such environments, use the--fallback-pythoncommand line
argument:tox2travis --fallback-python pythonx.yThe value passed to the argument must be a validbasepython.Custom basepythonIf environments specified intox.iniuse abasepythonthat can not be automatically mapped to one of the supported python
versions on Travis, use the--custom-mappingcommand line argument:tox2travis --custom-mapping <basepython> <travis-python>GitHub ActionsDespite the name,tox2traviscan also generate a configuration file
forGitHub Actions. Simply calltox2travis --output=actionsin a directory that contains atox.inifile. A new file.github/workflows/tox.ymlwill be
generated.
Package: tox-appveyor
This is a tiny Tox plugin to allow selecting 32-bit or 64-bit Python
onAppVeyorWindows CI builds.In yourappveyor.ymlfile, specify the different builds like this:environment:matrix:# Python 2.7, 64-bit-TOXENV:"py27"TOX_APPVEYOR_X64:1# Python 2.7, 32-bit-TOXENV:"py27"TOX_APPVEYOR_X64:0# Python 3.7, 64-bit-TOXENV:"py37"TOX_APPVEYOR_X64:1# Python 3.7, 32-bit-TOXENV:"py37"TOX_APPVEYOR_X64:0build:off# For the sections below, the Python version doesn't matter:# tox will make an environment based on the environment variables.install:-"py-3.6-mpipinstallwheeltoxtox-appveyor"test_script:-"py-3.6-mtox"Supporting Windows using Appveyorin the Python Packaging User Guide has more background info about testing Python
projects on Appveyor.
Package: tox-asdf
tox-asdfA Tox plugin usingasdfto find python executables.PrerequisitesThis plugin is made exclusevly to supportasdfso obviously you will need a functionnalasdfinstallation as well as theasdf-pythonplugin.InstallationSimply installtox-asdfin addition totoxto get ready:pipinstalltoxtox-asdfThat's it, you can now runtoxas usual but usingasdfPython installations.OptionsNo fallback on system pythonsBy default this plugin won't fail if a required Python version is missing fromæsdf, tox will fallback on its classic way of finding Python binaries from$PATH.
You can override this behavior and forcetoxto only useasdfby using the--asdf-no-fallbackoption:tox--asdf-no-fallbackAutomatically install pythonsBy default,tox-asdfwon't try to install missing Python version, but you can force this by using the--asdf-installoption.tox--asdf-installObviously this will only useful on the first run.Changelog0.1.0 (2019-01-05)Initial release
Package: tox-auto-env
tox-auto-envThe virtualenv behind your tox environments will always reflect the
dependencies at the time of running. Never usetox --recreateagain.WhyWhen testing or developing you may be updating or adding dependencies in thetox.iniorrequirements.txtfiles. You may then be stashing those changes
because they werebad. You may be switching between branches that have
different dependencies. Each time you do this, you need to recreate the tox
virtualenv so that those dependencies are correctly installed. Runningtox --recreatedoes this by deleting that virtualenv and starting fresh.How it worksWhentox-auto-envis installed, virtualenvs created by tox are identified by
a hash of the dependencies that are installed in it. i.e. if you have 2
branches with different dependencies, running tox on each of those branches
will create 2 separate virtualenvs that will be used for those 2 branches.How to usetox-auto-envis atoxplugin. Usepip install tox-auto-envto install.
If installed correctly, it should show up whentox --versionis run.KudosInspired bytox-battery
Package: tox-backtick
tox-backtickBackticks tox plugin for tox v.4.x.x.Overviewtox-backtickis a strict fork of Damien Nadé’stox-backtockspackage
(v.0.4.0) with a fixes allowing to work on Python 3.8 or higher and on
Windows with a little code reformatting and minor improvements.PyPI record.Documentation.Overview below is a copy from the originaltox-backtocksREADME.md:tox-backtocksA refreshed backticks tox pluginThis is a very early stage release. Use it at your own risks.Here’s the roadmap to 1.0 release and our current status:[x] define abackquote varinset_envwith abackquoted expression(and nothing else) and evaluate it
through bash, inside the tox virtual environment.[x] Make of abackquote varusable in commands section.[x] Allow another variable to be referenced inside thebackquoted expression[x] Strip the trailing newline characters of thebackquoted expression[ ] Allow user configure the evaluation ofbackquote expressionto be with a shell or not (either fork the command directly, either
fork a shell and evaluate a possible-complex shell expression)[ ] Allow abackquote varvalue to contain regular string partsand abackquote expression[ ] Allow abackquote varvalue to contain more than onebackquote expression[ ] Allow user to configure if we should strip the trailing newlinecharacters or not.[x] Allow another variable to reuse the evaluatedbackquoted expression[x] Allow another variable to reuse the evaluatedbackquoted expressionwithout reevaluating it :) (I mean,
it’s hacked, but heh, better than nothing)[x] If evaluating through a shell, automatically add said shell toallowlist_externalssection[x] Have a working package[ ] Write user documentationUsageTBD…InstallationPrerequisites:Python 3.8 or higherhttps://www.python.org/pip and setuptoolshttps://pypi.org/project/pip/https://pypi.org/project/setuptools/To install run:python -m pip install --upgrade tox-backtickDevelopmentPrerequisites:Development is strictly based ontox. To install it run:python -m pip install --upgrade toxVisitDevelopment page.Installation from sources:clone the sources:git clonehttps://github.com/karpierz/tox-backtick.gittox-backtickand run:python -m pip install ./tox-backtickor on development mode:python -m pip install --editable ./tox-backtickLicenseCopyright (c) 2023 Damien NadéCopyright (c) 2024-2024 Adam KarpierzLicensed under the zlib/libpng Licensehttps://opensource.org/license/zlibPlease refer to the accompanying LICENSE file.AuthorsDamien Nadé <anvil.github+tox-backtocks@livna.org>Adam Karpierz <adam@karpierz.net>Changelog0.4.4 (2024-01-26)Cleanup.0.4.1 (2024-01-24)First functional release.0.0.0 (2024-01-22)Initial commit.
Package: tox-backtocks
tox-backtocksA refreshed backticks tox pluginThis is a very early stage release. Use it at your own risks.Here's the roadmap to 1.0 release and our current status:define abackquote varinset_envwith abackquoted expression(and nothing else) and evaluate it through bash, inside the tox virtual
environment.Make of abackquote varusable in commands section.Allow another variable to be referenced inside thebackquoted expressionStrip the trailing newline characters of thebackquoted expressionAllow user configure the evaluation ofbackquote expressionto be with
a shell or not (either fork the command directly, either fork a shell
and evaluate a possible-complex shell expression)Allow abackquote varvalue to contain regular string parts and abackquote expressionAllow abackquote varvalue to contain more than onebackquote expressionAllow user to configure if we should strip the trailing newline
characters or not.Allow another variable to reuse the evaluatedbackquoted expressionAllow another variable to reuse the evaluatedbackquoted expressionwithout reevaluating it :) (I mean, it's hacked, but heh, better than
nothing)If evaluating through a shell, automatically add said shell toallowlist_externalssectionHave a working packageWrite user documentation
Package: tox-battery
The project is an attempt to add to thetoxsome missing out of the box functionality.Basically it is just an extension for the tool that will be loaded automatically.FeaturesFirstexperimental featureis to recreate virtual environment on requirements file update.InstallationThanks to entrypoints mechanism used by tox plugin system no additional configuration
is required except of the package installation.pip install tox-batteryPackage MaintainanceReleasetox -e release
Package: tox-bitbucket-status
Toxplugin that pushes status reports back toBitBucket.Installation:$ pip install hg+https://bitbucket.org/hpk42/tox@hook/report-status#egg=tox
$ pip install tox-bitbucket-status(You need to install the custom tox version for now, until the next version of tox is released).Usage:You need to ensure the following environment variables are set in your environment:CI
CI_NAME
CI_COMMIT_ID
CI_BUILD_URL
BB_USERNAME (will default to $BB_REPO_OWNER if not set)
BB_PASSWORD
BB_REPO_OWNER
BB_REPO_SLUGThen, your commits will get a build status after they are pushed to BitBucket.Just like the onesin this repository.CodeshipTheCI_*variables are all set by Codeship, but you will need to seth theBB_*variables yourself.JenkinsIf you are using Jenkins and the Mercurial plugin, then some of the environment will be detected from the environment variables that are set:CI → True
CI_NAME → 'Jenkins'
CI_BUILD_URL → $BUILD_URL
CI_COMMIT_ID → $MERCURIAL_REVISION

BB_REPO_OWNER : extracted from $MERCURIAL_REPOSITORY_URL
BB_REPO_SLUG : extracted from $MERCURIAL_REPOSITORY_URLAt this point, the extraction of the owner/slug from the repo url only does sanity checking for mercurial repos (ie, that they are from bitbucket). Pull requests to support git repo urls will be accepted.
Package: tox-cmake
#################################################``tox-cmake``: Build CMake projects using Tox#################################################:author: Andre Caron (andre.l.caron@gmail.com)Introduction============I guess this projects needs a bit of explaning :-)I work on a product that uses Python on the back-end and C++ for theclient-side SDK.  Testing that the C++ client SDK and the Python back-endquickly becomes painful.  Since Python has IMHO much, much better testingtools, it's only natural to want to use them all the time.Calling ``cmake`` directly from Tox's ``commands`` setting works, but it has afew quirks:* ``cmake`` has to be in ``PATH`` for thos to work, which makes requiring aspecific CMake version kind of hard;* there can be only one ``cmake`` in ``PATH``, which makes it impossible totest against multiple CMake versions with the same ``tox.ini`` configuration;and* Tox warns when it invokes a command-line tool that isn't installed in thevirtual environment (e.g. when it resorts to searching ``PATH`` to invoke acommand).This Python package is simply a stub for CMake that will accept a CMake versionrequirement and find a compatible ``cmake`` program installed on your machine(or fail with a clear error).Since it uses a ``setuptools`` console entry-point, it also convenientlysilences Tox's warning about relying on ``PATH``.Usage=====The process is quite simple:#. Add ``tox-cmake`` to Tox's ``deps`` setting.#. Use Tox's ``changedir`` setting (for out-of-source CMake builds).#. Invoke ``tox-cmake`` in Tox's ``commands`` setting.Here's a full example::[testenv]deps =tox-cmakechangedir = {toxinidir}/build/{envname}commands =tox-cmake ">=2.8,<3" ../..tox-cmake ">=2.8,<3" --build --config Debug .CMake version requirements--------------------------The CMake version requirement string should feel familiar:* similar to ``requirements.txt`` files, it accepts ``>=``, ``<`` and ``==``constraints;* for ``>=`` and ``<`` constraints, you can specify partial version numbers(e.g. only major and minor);* for ``==`` constraints, you need to have an exact match;* a small extension allows picking a taggerd build (e.g. ``"-foo"`` will pick aversion like ``2.8.12.2-foo``)* commas allow to specify multiple constraints (e.g. ">=2.8,<3" will search forthe latest CMake 2.8 on your system).Licensing and redistribution============================The project is released under the MIT license.  See the ``LICENSE.txt`` filefor legal text.Contributing============Pull requests are welcome!  Make sure to add your name to the ``AUTHORS.txt``file on your pull request.Opening an issue to discuss your changes before implementing them isrecommended, but not required.
Package: tox-console-scripts
tox-console-scripts pluginIt's possible to use system site packages within Python virtual environment,
but there is no way to install console or gui scripts into such environment.With the help of this plugin the corresponding scripts will be automatically
generated for all of system site packages.This is mostly used for testing purposes in ALTLinux during RPM build of Python
packages to run integration tests against the repository packages.UsageThe two possible options may be provided with:tox.iniconfiguration file[testenv]
console_scripts = Truecommand line optiontox --console-scriptsNote: both requiresitepackages.LicenseDistributed under the terms of theMITlicense,tox-console-scriptsis
free and open source software.
Package: tox-constraints
tox-constraintsReproducible tests, with minimal configuration, by defaultBenefitsThis plugin is helpful because itmakes using pinned versions the default,tells virtualenv to use the pinned versions,facilitates gathering of dependencies, andalerts you of the above pitfalls so that, hopefully, you do not have to learn it the hard way.MotivationThe best way to improve reproducibility of toxwithoutthis plugin is to setPIP_CONSTRAINTusing eithersetenv, orpassenv.This is good, it ensures that all packages installed with pip will use the constraints file[^1].SettingPIP_CONSTRAINTdoes however not ensure that packages installed with other tools will use the constraints file.
Notably tox creates environments using virtualenv, which seeds the environment with some version of pip, setuptools, and wheel.
By default, a version that was bundled with the virtualenv is used, so while the behavior may be surprising it should be reproducible.
The versions installed can be controlled[^2] usingsetenvorpassenvto setVIRTUALENV_PIP,VIRTUALENV_SETUPTOOLS, andVIRTUALENV_WHEEL.SettingPIP_CONSTRAINTalso does not ensure that all packages that will be installed are listed in the constraints file[^3].
pip-compile is a great tool to help both resolve all transient dependencies and assign a consistent set of versions.
But it cannot pick updepsfromtox.inifile orbuild-system.requiresfrompyproject.toml.LimitationsKnown limitations and problems includedepsfrom environments not on theenvlistwill not be gathered.-lshould be set when gathering dependencies to avoid actually running the environments.Thebuild-system.requiressection frompyproject.tomlmust be manually reproduced in a text file to make it available to pip-compile.
There is anopen issue in pip-toolsthat, if implemented, would resolve this.[^1]: Using the-cflag on the other hand does not ensure that build dependencies are pinned, seepip#8439.
[^2]: Except when it does not.
Something about it caching and upgrading packages locally causes it to occasionally ignore the specified versions.
It can be hard to realize that this is happening and when it does the best course of action seems to be removing the cache at~/.local/share/virtualenv/.
[^3]: One could enable hash checking mode in which case pip would refuse to install any package for which it has not been given a hash.
However, this creates new problems such as the package under test not having a hash.
This package previously attempted to solve this use case but stopped since hash checking mode has been mostly broken in pip since the new resolver.
:face_exhaling:
Package: tox-DEBIAN
tox_DEBIANtox_DEBIAN.pyis atoxplugin which extractsDebianpackages
into the tox managed virtual environment.DependencyHook dependencyThe plugin implements thetox_testenv_install_depspluggyhook,External dependencyThe plugin uses theapt-get,dpkgandcptools.Test dependencytox_DEBIAN, liketox, usespy.testfor test automatization.SyntaxThe debian dependencies has to be listed in thetestenvsection
asdebian_depsmulti line option.[testenv]debian_deps=python3-ipaddrpython3-yamlExtra options can be defined forapt-getwith theapt_optsoption:[testenv]apt_opts=--allow-unauthenticateddebian_deps=python3-ipaddrpython3-yamlInstallInstall toxpipinstalltoxtoxusesRequirementParseErrorfrompkg_resources, thereforesetuptoolsmight need to be upgraded:pipinstall--upgradesetuptoolsInstalltox_DEBIANpipinstalltox_DEBIANTestLocaltox_DEBIANinstallgitclonehttps://github.com/tpazderka/tox-debian-plugin.git
pipinstall-etox-debian-pluginInstallpy.testpipinstallpytestTest runcd tox-debian-plugin
py.test tests
Package: tox-envlist
Allows selection of a different tox envlist.TestsPyPIActivityQAOtherConfigurationIn yourtox.inifile, add the following:[envlists]test=py36, py37, py38qa=mypy,lintcov=py36,coverageThis will configure three envlists:test, which runs the environmentspy36,py37andpy38qa, which runs the environmentsmypyandlintcov, which runs the environmentspy36andcoverageYou are free to customise these envlists and add new ones.UsageRun tox using the-n/--envlist-name[name]option, wherenameis the name of the envlist.Installationtox-envlistcan be installed from PyPI.To install withpip:$python-mpipinstalltox-envlist
Package: tox-envreport
tox-envreportis a plugin fortoxto document the setup of used virtual environments.Collected information are stored in a file calledenv_report.jsoninside the.toxfolder.
For example:MY_PROJECT/.tox/env_report.json.Installationpip installtox-envreportUsageThe installation of the plugin is enough to automatically activate it for each tox run.There is nothing more to do or to configure.Access reportstox-envreportcreates one commonenv_report.jsonfile, which contains all information about all used virtual
environments (venv) by tox.Beside this a venv specific file is generated as well and contains information about the related venv only.
You can find this file in the venv-specific tox-folder. E.g:MY_PROJECT/.tox/py27/env_report_py27.jsonfor a venv calledpy27.The report file itself contains the venv-name as postfix. E.g.:env_report_py27.json.
Package: tox-external-wheels
tox-external-wheelsUse externally created wheels with ToxFeaturesThe ability to define external wheel files to tests in the tox config (exampletox.inifile):[tox]envlist=py-{a,b,c}[testenv]external_wheels=a:{toxinidir}/dist/*py27*.whlb:{toxinidir}/dist/*py37*.whlcommands=a,b:pytest testc:pip listOr defined in a command line argumenttox-e'py-{a,b,c}'--external_wheels'a:dist/*py27*.whl;b:dist/*py37*.whl'Notes: In this casepy-cfalls back to installing from source.tox-external_wheelsnow supports ! in env namesThe ability to define an external command to build wheel(s) with (exampletox.inifile):[tox]envlist=py-{a,b,c}[testenv]external_build=./prepare_build.sh./build.shexternal_wheels={toxinidir}/dist/*.whlcommands=a,b:pytest testc:pip listOr defined in a command line argumenttox-e'py-{a,b,c}'--external_build'./build.sh'Note: if command exits with non-zero return code, error will be reported and exception will be raised.Support installing dependencies from external wheel files by adding their name into theexternal_wheelsin config[tox]envlist=py-{a,b,c}[testenv]deps=sixexternal_wheels=a:{toxinidir}/dist/*py27*.whl (six: six-*.whl[optional_extra])b:{toxinidir}/dist/*py37*.whlcommands=a,b:pytest testc:pip listOr defined in a command line argumenttox-e'py-{a,b,c}'--external_wheels'a:dist/*py27*.whl (six: six-*.whl[optional_extra]);b:/dist/*py37*.whl'RequirementstoxInstallationYou can install "tox-external-wheels" viapipfromPyPI:pip install tox-external-wheelsUsageUse theexternal_wheeloption. Like shown inusageContributingContributions are very welcome. Tests can be run withtox, please ensure
the coverage at least stays the same before you submit a pull request.LicenseDistributed under the terms of theMITlicense,tox-external-wheelsis
free and open source software.IssuesIf you encounter any problems, pleasefile an issuealong with a detailed description.
Package: tox-extra
tox-extraThistox pluginadds few extra checks
like:ensure exit code 1 if git reports dirty or untracked filesafterthe runUsage example:$ tox -e py
...
ERROR: Git reported dirty status. Git should never report dirty status at the end of testing, regardless if status is passed, failed or aborted.
On branch devel
Your branch is up to date with 'origin/devel'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	some-untracked.txt

nothing added to commit but untracked files present (use "git add" to track)
__________________________________________ summary ___________________________________________
ERROR:   py: failedThe goal of this plugin is to help developers be aware about files modified by tests
or untracked files before they commit the code. This plugin also does not take into
consideration the global.gitignore, something that can make git miss reporting
some untracked files, the goal being to assure that when a new developer clones and
runs the tests they do not endup with an unexpected git status.If you have any cases where you expect to have git report dirty, please
add--allow-dirtyto the command call to disable this check.