Saravanan666/pypi-org huggingface dataset:
Package: checklinks
# check-linksIf you are seeing this on GitHub, you should know that this is a mirror from Gitlab:https://gitlab.com/alexbenfica/check-links/Issues and and milestones are all there!# What does it do?Allows you to check for broken links in all internal pages of a website and more:
- export results to comma separated values (.csv)
- can also be imported as moduleIt is used for some specific tasks:
- find broken urls on pages
- as a desired side effect, load pages and forces caching creation
- created to run in a daily basis reporting broken links of multi site network# How to use it?You can download an run via command line:`python3 check_links.py--help`ORYou can install via pip3:`pip3 install-Uchecklinks`It is simple and really fast as it reuses http socket connections!Enjoy it!
Package: checkmate
Checkmate is a cross-language (meta-)tool for static code analysis, written in Python.
Unlike other tools, it provides a global overview of the code quality in a project and aims
to provide clear, actionable insights to the user.DocumentationThe documentation can be foundhere <https://docs.quantifiedcode.com/checkmate>.Source CodeThe source code can be found onGithub <https://github.com/quantifiedcode/checkmate>.Changelog0.2.0: Beta-release
Package: checkmatelib
checkmatelibTools for interacting with the Checkmate URL checking service.UsagefromcheckmatelibimportCheckmateClient,CheckmateExceptionclient=CheckmateClient("http://checkmate.example.com")try:hits=client.check_url("http://bad.example.com","YOUR_CHECKMATE_API_KEY")exceptCheckmateException:...# To block or not to block?ifhits:print(hits.reason_codes)Updating the data filesYou can refresh the domain information with the following command:hdevrunupdate-dataSetting up Your checkmatelib Development EnvironmentFirst you'll need to install:Git.
On Ubuntu:sudo apt install git, on macOS:brew install git.GNU Make.
This is probably already installed, runmake --versionto check.pyenv.
Follow the instructions in pyenv's README to install it.
TheHomebrewmethod works best on macOS.
TheBasic GitHub Checkoutmethod works best on Ubuntu.
Youdon'tneed to set up pyenv's shell integration ("shims"), you canuse pyenv without shims.Then to set up your development environment:git clone https://github.com/hypothesis/checkmatelib.git
cd checkmatelib
make helpReleasing a New Version of the ProjectFirst, to get PyPI publishing working you need to go to:https://github.com/organizations/hypothesis/settings/secrets/actions/PYPI_TOKENand add checkmatelib to thePYPI_TOKENsecret's selected
repositories.Now that the checkmatelib project has access to thePYPI_TOKENsecret
you can release a new version by justcreating a new GitHub release.
Publishing a new GitHub release will automatically triggera GitHub Actions workflowthat will build the new version of your Python package and upload it tohttps://pypi.org/project/checkmatelib.Changing the Project's Python VersionsTo change what versions of Python the project uses:Change the Python versions in thecookiecutter.jsonfile. For example:"python_versions":"3.10.4, 3.9.12",Re-run the cookiecutter template:make templateCommit everything to git and send a pull requestChanging the Project's Python DependenciesTo change the production dependencies in thesetup.cfgfile:Change the dependencies in the.cookiecutter/includes/setuptools/install_requiresfile.
If this file doesn't exist yet create it and add some dependencies to it.
For example:pyramid
sqlalchemy
celeryRe-run the cookiecutter template:make templateCommit everything to git and send a pull requestTo change the project's formatting, linting and test dependencies:Change the dependencies in the.cookiecutter/includes/tox/depsfile.
If this file doesn't exist yet create it and add some dependencies to it.
Use tox'sfactor-conditional settingsto limit which environment(s) each dependency is used in.
For example:lint: flake8,
format: autopep8,
lint,tests: pytest-faker,Re-run the cookiecutter template:make templateCommit everything to git and send a pull request
Package: checkm-genome
CheckMInstalling and using CheckMPlease see the project home page for usage details and installation instructions:https://github.com/Ecogenomics/CheckM/wikiWe do not recommend installing CheckM from the master branch. This may be unstable. Please install an official release of CheckM or use pip.Estimating quality of CPR genomesInformation about obtaining improved quality estimates for CPR (Patescibacteria) genomes can be found here:https://github.com/Ecogenomics/CheckM/wiki/Workflows#using-cpr-marker-setMigration to Python 3CheckM has been ported to Python 3 to accomodate Python 2 reachingend of lifeon January 1, 2020. CheckM >=1.1.0 requires Python 3. Python 2 will no longer be actively supported. Apologies for any issues this may cause.Massive thanks tobaudrly,Vini Salazar, andAsaf Peerfor initial Python 2 to 3 porting.Python 2 to 3 ValidationPorting of CheckM to Python 3 was validation on a set of 1,000 genomes randomly select from theGTDBR89 representative genomes. Results were compared to those generated with CheckM v1.0.18, the last Python 2 version of CheckM. Identical results were obtained for the 'lineage_wf', 'taxonomy_wf', and 'ssu_finder' methods across this set of test genomes. Other CheckM methods have been executed on a small set of 3 genomes to verify they run to completion under Python 3.Removed FunctionalityThe following features have been removed from CheckM v1.1.x in order to simplify the code base and focus CheckM and support requests on critical functionality:bin_qa_plot: non-critical, rarely used plot which does not scale to the large numbers of MAGs now being recoveredpar_plot: non-critical plot and the same information is better presented in the reference distribution plotscov_pca, tetra_pca: alternatives to these static plots exist in tools such asAnvi'olen_plot: rarely used plot which is largely redundant with the len_hist and nx_plot plotsbin_union, bin_compare: feature rich alternative now exist such asDAS ToolandUniteMBug ReportsPlease report bugs through the GitHub issues system.Copyright © 2014 Donovan Parks, Connor Skennerton, Michael Imelfort. See LICENSE for further details.
Package: checkmyreqs
checkmyreqs allows you to check the packages in your requirements file against a specified Python version.UsageThis command will check 2 requirements files, to see if their packages are compatible with Python 3.3checkmyreqs -f requirements.txt,requirements_dev.txt -p 3.3If you don’t pass in a filename, it will use requirements.txt in the directory it is calledcheckmyreqs -p 3.2The output is a list of packages not supported by the given Python version.For each package, checkmyreqs will tell you if updating them will give you support.There are 3 parameters-f, --files   : comma-separated list of files to check (optional, default is requirements.txt)
-p, --python  : Python version to check compatibility, example 2.7 or 3.2 (optional, default is system Python)You can also usepip freezeto check a Python environment without a requirements file, like sopip freeze | checkmyreqs -p 3.3Caveatcheckmyreqs looks at packages on pypi.python.org to see if their author has included a classifier saying which
Python versions are supported.If the package has incorrect or missing classifiers, checkmyreqs will show it as unsupported.This tool is meant as an addition to other porting tools. 2to3 and six can help you make your code Python 3 ready,
and checkmyreqs lets you quickly check if your packages are ready to move as well.Installationpip install checkmyreqsSupports Python 2.7, 3.2, 3.3, 3.4Python <=2.6, 3.0 and 3.1 are not supported, they don’t have argparseDevelopmentYou can install the requirements withpip install -r requirements.txt
pip install -r requirements_dev.txtThen, run the tests withpy.test
Package: check-mysql-slave
Check MySQL seconds behind master for Nagios-like monitoring.Usage$check_mysql_slave--helpusage:check_mysql_slave[-h]-u[USER]-p[PASSWORD][--host[HOST]][--portPORT][warning_threshold][critical_threshold]positionalarguments:warning_thresholdWarningthreshold(defaultsto60)critical_thresholdCriticalthreshold(defualtsto300)optionalarguments:-h,--helpshowthishelpmessageandexit-u[USER],--user[USER]Loginusername-p[PASSWORD],--password[PASSWORD]Loginpassword--host[HOST]Loginhost--portPORTLoginportLicenseThis software is licensed under the MIT license (see theLICENSE.txtfile).AuthorNimrod Adar,contact meor visit mywebsite. Patches are welcome viagit send-email. The repository is located
at:https://www.shore.co.il/git/.
Package: check_no_scheduled_ec2_events
A Nagios-style script that will check if the Amazon EC2 instance it is running
on has any events scheduled, like a system reboot.Exit code 2 if any events are scheduled, 0 otherwise. Useful in combination
with Nagios and/or NRPE.Usage:check_no_scheduled_ec2_eventsNo options are given. The script assumes it is running in an EC2 instance, and
will grab the current instance id from the instance metadata and AWS
credentials from the current environment.Changelog:0.2.1 - Handleeventsbeing None in botoInstanceStatus0.2.0 - Handle case where a “completed” scheduled event still shows up in API0.1.1 - Initial public release
Package: check-oldies
check-oldiesis a collection of programs that warn about old
things in code:check-fixmeswarns about old FIXME or TODO annotations and
orphan FUTURE tags.If we did not regularly check, we would forget about that FIXME note
we wrote a few months ago.check-fixmeswarns us about it. It is
then our choice to act: fix it, remove it (because we decided it is
not worth to fix, or because it is not relevant anymore), or
postpone it.FUTURE tags: We sometimes plan a broad modification that will span
multiple files. Instead of littering FIXME annotations everywhere,
we set a single FIXME annotation and a FUTURE-xxx tag on the same
line. Then, wherever we need to make a modification, we only
mention this FUTURE-xxx tag without any FIXME. If we ever remove the
FIXME but keep a FUTURE-xxx tag somewhere, it is a mistake and this
tool warns us.check-brancheswarns about old branches, surprisingly.forget-me-notruns both programs above on a set of Git
repositories and sends warning e-mails to authors of soon-to-be-old
annotations or branches.In other words:check-fixmesandcheck-branchescan be run as
part of the test suite of each project (by a continuous integration
system such as Jenkins). They break builds when they detect old
things.  On the other hand,forget-me-notcan be run once a week
on a set of projects to warn authors that some buildswillbreak
soon if they do not take care of their old annotations or branches.Example output$ check-fixmes
NOK: Some annotations are too old, or there are orphan FUTURE tags.
jdoe            -  181 days - frobulator/api.py:12: # FIXME (jdoe): we should catch errors
jdoe            -  100 days - frobulator/api.py:25: # TODO: this is slow, use the batch API instead
jsmith          -   12 days - docs/index.rst:1: # FIXME: write documentation before open sourcing$ check-branches
NOK: Some branches are too old.
john.smith@example.com     -   92 days - jsmith/fix_frobs (https://github.com/Polyconseil/check-oldies/tree/jsmith/fix_frobs), linked to open PR/MR #1 (https://github.com/Polyconseil/check-oldies/pull/1)Applicabilitycheck-oldiesis written in Python but is language-agnostic. It
works on Git repositories but could be extended to other version
control systems. It integrates with GitHub but can do without it, and
could be extended to work with other code hosting platforms.Requirements and installationYou must have Python 3.7 or later, and a relatively recent version of
Git. Git 2.1.4 (shipped with Debian Jessie) is known to work. More
recent versions should work and are supported.Install withpip, preferably in a virtual environment:$python3-mvenv/path/to/your/virtualenv$source/path/to/your/virtualenv/bin/activate$pipinstall"check-oldies[toml]"Features, configuration and moreThefull documentationhas more details about the features and the
configuration, examples of the usage of FUTURE tags, how to
contribute, etc.
Package: checkopt
quick startimport checkopt  
print(checkopt.checkopt("g help m|module="))

(venv) PS D:\python> python .\test.py -m module_name --help -g project_name
({'m': 'module_name', 'help': None, 'g': None}, ['project_name'])r = checkopt.checkopt("m|module=* f=")
(venv) PS D:\python> python .\demo.py -m module_name1 -m module_name2 extra_data -f 123
({'module': ['module_name1', 'module_name2'], 'f': '123'}, ['extra_data'])argument formatshort_opts|long_opts=*=means the option receives an  argument*means the option allows multiple arguments and the corresponding data will be a string list
while space is the char to split to option patternadvantagescode:print(getopt.getopt(sys.argv[1:], "m:h")) 
print(checkopt.checkopt("m= h|help"))

(venv) PS D:\WorkSpace\python> python .\container_update.py -h file -m abcresult:([('-h', '')], ['file', '-m', 'abc']) # getopt
({'h': None, 'm': 'abc'}, ['file'])   # checkopt
Package: check-orientation
Check orientationModels to check if image was rotated by 0, 90, 180, 270 degrees.Installationpip install -U check_orientationExample inferenceColab notebook with the example:TrainingDefine the config.Example atcheck_orientation/configsDefine the environmental variableTRAIN_IMAGE_PATHthat points to the folder with train dataset.Example:exportTRAIN_IMAGE_PATH=<pathtothetraniningfolder>Define the environmental variableVAL_IMAGE_PATHthat points to the folder with validation dataset.Example:exportVAL_IMAGE_PATH=<pathtothevalidationfolder>Trainingpython -m check_orientation.train -c <path to config>Inferencepython-mtorch.distributed.launch--nproc_per_node=<num_gpu>check_orientation/inference.py\-i<pathtoimages>\-c<pathtoconfig>\-w<pathtoweights>\-o<output-path>\--fp16Pre-trained modelsModels were pre-trained on theOpenImages dataset.ModelsValidation accuracyConfig fileWeightsswsl_resnext50_32x4d0.9128LinkLink
Package: checkout
checkout------------|build status|_.. |build status| image:: https://secure.travis-ci.org/tuomasb/python-checkout.png?branch=master:alt: Build Status.. _build status: http://travis-ci.org/tuomasb/python-checkoutPython wrapper for the Checkout Finland API.Installation------------::$ pip install checkoutResources---------- `Issue Tracker <http://github.com/tuomasb/python-checkout/issues>`_- `Code <http://github.com/tuomasb/python-checkout>`_- `Development Version<http://github.com/tuomasb/python-checkout/zipball/master#egg=checkout-dev>`_Changelog---------Here you can see the full list of changes between each python-checkoutrelease.0.3.0 (February 6, 2014)^^^^^^^^^^^^^^^^^^^^- Initual public release of python-checkout.0.2.0 (June 6, 2013)^^^^^^^^^^^^^^^^^^^^- Initial public release of python-verkkomaksut.
Package: checkout-by-amazon
This is a library for interfacing with Amazon’s integrated payment
system,Checkout by Amazon.InstallIf you havepipinstalled, you can simply run:$ pip install cbaIf you lack pip but haveeasy_install, run:$ easy_install cbaIf you have neither, download this package and run:$ python setup.py installUsageimport cba

cba_settings = cba.Settings(
    merchant_id='...',
    marketplace_id='...',
    public_access_key='...',
    secret_access_key='...',
    sandbox=False,
)

if preexisting_id:
    contract = cba.PurchaseContract(id=preexisting_id, settings=cba_settings)
else:
    contract = cba.PurchaseContract(settings=cba_settings)

for item in cart:
    contract.order.add_item(cba.Item(id=item.id, title=item.name, price=item.price))

# Commit the order to Amazon after buyer has selected address and payment
# method.
contract.complete()LicenseThis program is free software: you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation, either version 3 of the License, or (at
your option) any later version.This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser
General Public License for more details.You should have received a copy of the GNU General Public License along
with this program. If not, seehttp://www.gnu.org/licenses/.
Package: checkout-code
checkout_codeTool to checkout a specific commit to a unique locationinstallationpip install .usagecheckout_code
  --repository /path/to/git/repo
  --checkout-dir /path/to/version/location
  -c commit_hash
  --use-prefix--use-prefixprefixes the directories incheckout_dirwith the repository nameTo get the final path use an additional--get-path, i.e.checkout_code
  --repository /path/to/git/repo
  --checkout-dir /path/to/version/location
  -c commit_hash
  --use-prefix
  --get-paththis will only print the path butnotcheckout the code. Its intendented to be used in a variable.example usage in scriptssource env/bin/activate
COMMIT="b59616685000ddb5583186bcb7fd4b3e3d481f19"
checkout_code --repository ~/src/sockeye --checkout-dir ~/work/sockeye/ -c $COMMIT --use-prefix
path=$(checkout_code --repository ~/src/sockeye --checkout-dir ~/work/sockeye/ -c $COMMIT --use-prefix --get-path)
export PYTHONPATH="$path:$PYTHONPATH"development version a.k.aHEADif you specify the commit asHEADthe tool will not checkout anything but the--get-pathoption will return your repository. That way you can useHEADto point to your latest, possible uncommited, versionenvironment filesTo make it easier to use you can also use.envfiles instead or in addition to CLI-options. You can specify the file by using--env /path/to/.env/fileor it willautomatically search for files. In the environment file just userepository=/path/to/repo
checkout_dir=/path/to/checkout_dir
use_prefix=Trueto specify your settings.Notecommand line arguments will always override environment settingsversion history0.1 2018-03-08initial version0.2 2018-03-08added file lockadded requirements0.3 2018-03-20added loading of env files0.4 2018-07-13return exit code 1 if checkout_dir does not exists0.5 2019-02-08add default timeout for filelock (closes#2)added option to change timeout value
Package: checkout-psp-client
Checkout Finland Payment Service Client API WrapperThis package implements a wrapper for theCheckout Finland Payment
Service Client APIthat
ecommerce software developers can use to integrate their ecommerce
checkout systems with the Checkout Finland payment service.I wrote this for my company's webshop and I am releasing it in case
others find it useful.  My priority is my own shop, but I will accept
bug reports and merge requests that improve on the core functionality.
For functionality to be included that my shop does not need, someone
else (who is personally invested in it) must commit to its
maintenance.This package is not written or sponsored by Checkout Finland, and
there is no other relationship between them and myself than that, at
the time of this writing, I run one of their merchant clients.
Package: check-paloalto-ng
check_paloalto_ng is aNagios/Icinga pluginfor Palo Alto Next Generation Firewalls, that was initially developed by ralpha089 (https://github.com/ralph089/nagios_check_paloalto)
It is written in Python and based on the PA REST API.Tested on:PA-500 v6.0.1 - v6.0.9PA-3050 v6.0.9 - 7.1.9Documentationhttps://check-paloalto-ng.readthedocs.io/en/latest/QuickstartPlease make sure you have python-dev and libxslt1-dev installed on your machine.To install check_paloalto_ng:$ pip install check_paloalto_ng --upgradeor use:$ pip3 install check_paloalto_ng --upgradeThe plugin requires a token to get information from the PA-REST-API. Please see the following link for more information:https://check-paloalto-ng.readthedocs.io/en/latest//configuration.html#token
Package: checkparam
AboutModule for checking input parameters by typeSimple StartInstall package from pippip install checkparamUsefrom checkparam import check_param

@check_param()
def my_func(var_one: int, var_two: typing.Optional[int]): 
  ...
  
my_func(4, None)       # all good
my_func('test', None)  # Exception from check_param, becouse 'test' is not type 'int'
Package: checkpatch-junit
checkpatch-junitA Python program to generate JUnit XML test result from Linux script
checkpatch.pl output.Then, this result can be consumed by continuous integration tools
(Jenkins, GitLab CI ...) to provide nice information display.InstallationClone and install from GitHubgitclonehttps://github.com/mastiggia/checkpatch-junit
pythonsetup.pyinstallUsagecheckpatch-junit[-h][-ccheckpatch.pl][--checkpatch-argsarg1,arg2,...][-ooutfile.xml][--ignore-check][--ignore-warning]FILE[FILE...]ProvideJUnitoutputtoLinuxcheckpatch.plscript

positionalarguments:FILEpatchtoanalyzewithcheckpatch.pl

options:-h,--helpshowthishelpmessageandexit-ccheckpatch.plpathtothecheckpatch.plscripttouse--checkpatch-argsarg1,arg2,...extraargumentstopasstocheckpatch.pl,separatedbycommasinsteadofspaces-ooutfile.xmloutputJUnitXMLfile--ignore-checkignorecheckpatch.plcheckmessages--ignore-warningignorecheckpatch.plwarningmessagesBasic example:checkpatch-junit-cscripts/checkpatch.pl--checkpatch-args=--no-tree*.patch-ocheckpatch.xml
Package: check-pip-compile
check_pip_compileAutomatically verify if you need to runpip-compile.UsageYou can use it as apre-commithook:-repo:https://github.com/MartinThoma/check-pip-compilerev:0.1.0hooks:-id:check-pip-compileargs:['.']# it's recommended to specify the files you wantor via command line:$ check_pip_compile .
Run 'pip-compile requirements-dev.in' (2020-09-22 22:47:11.551971), as requirements-dev.txt (2020-09-02 09:53:58.287945) might be outdated
Run 'pip-compile setup.py', as no corresponding txt file exists

$ check_pip_compile setup.py requirements-lint.in
Run 'pip-compile setup.py', as no corresponding txt file exists
Package: check-pipfile-lock
This package bridges gab in pipenv tooling by providing
quick and easy way to check whether Pipfile.lock in question
is consistent with the corresponding Pipfile without doing
anything else.I find it particularly useful with pre-commit hooks (see below)Usagecheck-pipfile-lock <path to Pipfile.lock>If no path toPipfile.lockis provided, the current
directory is assumed.Pre-commit hookHere is the configuration forpre-commitframework.-repo:https://github.com/haizaar/check-pipfile-lockrev:v0.0.5hooks:-id:check-pipfile-lockDevelopmentecho'layout pipenv'>.envrcdirenvallow# will take a whilemakebootstrap
Package: check_po
########check_po########Test if the po is fully translated without fuzzy... image:: https://secure.travis-ci.org/peopledoc/check_po.png?branch=master:alt: Build Status:target: https://secure.travis-ci.org/peopledoc/check_po.. image:: https://coveralls.io/repos/peopledoc/check_po/badge.png?branch=master:alt: Coverage Status on master:target: https://coveralls.io/r/peopledoc/check_po?branch=master.. image:: https://pypip.in/v/check_po/badge.png:target: https://crate.io/packages/check_po/.. image:: https://pypip.in/d/check_po/badge.png:target: https://crate.io/packages/check_po/`Documentation<https://github.com/peopledoc/check_po/wiki>`_