Saravanan666/pypi-org huggingface dataset:
Package: peopleanalyticsdata
OverviewProject name: peopleanalytics-pythonThis package is port of an R package associated with thefree onlinebookHandbook of Regression Modeling in People Analyticsby Keith McNulty. Some additional information about the inspirationhere.BackgroundAt peopleanalytics-regression-book.org, McNulty makes the data referenced inHandbook of Regression Modeling in People Analyticsavailablevia an R package. McNulty explains:For R and Python users, each of the data sets used in this book can be downloaded individually by following the code in each chapter. Alternatively for R users who intend to work through all of the chapters, all data sets can be loaded into an R session in advance by installing and loading the peopleanalyticsdata R package.This package brings the functionality of McNulty's R package to Python users. As an initial idea, following apip install ...will make these data sets accessible for Python users. These data sets can also be used as an alternative to the very common public data sets (iris, wine quality, etc) available on UCI repository to understand the concepts of exploratory data analysis and predictive modeling.Usage# import peopleanalyticsdata packageimportpeopleanalyticsdataaspadimportpandasaspd# see a list of data setspad.list_sets()# pad.help(managers)# load data into a dataframedf=pad.managers()# find out more about a specific data set ('managers' example)pad.managers().info()Data dictionaryThe data dictionary pertinent to all the data sets can be foundhere.LICENSEMIT
Package: peoplefinder
people-finderTools for finding and storing profile pics of whatsapp contacts in large scale.InstallationFrom pypi$ pip install peoplefinderFrom source (current version 1.0b1)$ git clone https://github.com/fmndantas/people-finder.git
$ cd people-finder
$ python setup.py installTelegram API tokenIf you plan to usepeopleuploaderfunctionalities, make sure your environment
variable PEOPLE_API_TOKEN points to our bot.UsageA graphical interface will be implemented in future updates, but, for now, the usage isinline. We've set up the number's format to our
country, Brazil (+55 XX XXXX-XXXX). A example of use is$ peoplefinder -n 10 -d 84 -rwhere the 10 refers to number of loops in search, 84 refers to the local area code of the phone numbers and
the -r flag indicates random number generationAlternatively one can create a list of numbers in a file named
input.txt in the same directory and omit this flag.Uploading to telegram @peoplefinder$ peopleuploader [-s <savedir>] [-c]This will upload all pictures inside savedir.
The optional flag -c will clear the files simultaneously.
Package: people-finder
people-finderA tool to easy recognize people in images.Installpip install people-finderUsagefrompeople_finderimportRecognition# Initr=Recognition()# Insert recognizable peoplep1='P1'p2='P2'r.insert_recognizable_people([p1,p2],train_folder_path='path/to/known/people')# Train the datasetr.train_dataset(train_folder_path='path/to/known/people',trained_model_path="trained_model.clf")# Find people in an imageres=r.find_people_in_image('/path/to/image.jpg',trained_model_path="trained_model.clf")print('People found:')forpersoninres:print(person)
Package: peoplegraph-api-client
peoplegraph-api-clientAPI client for deep-compute’s peoplegraph producthttp://www.deepcompute.com/peoplegraph/Installationpip install peoplegraph-api-clientUsageGrab your api secret key fromhttp://www.deepcompute.com/peoplegraph/settingspeoplegraph-H"http://www.deepcompute.com"-u"<username>"-s"<api-secret-key>"-n"John Doe"--waitIf you have a webserver that accepts POST requests, you can give
peoplegraph a callback, to which it will POST the result.peoplegraph-H"http://www.deepcompute.com"-u"<username>"-s"<api-secret-key>"-n"John Doe"--callback"http://www.myserver.com"
Package: people-segmentation
Binary segmentation of peopleDataTrain set:Mapillary Vistas Commercial 1.2 (train)COCO (train)Pascal VOC (train)Human MattingValidation set:Mapillary Vistas Commercial 1.2 (val)COCO (val)Pascal VOC (val)SuperviselyTo convert datasets to the format:training
    coco
    matting_humans
    pascal_voc
    vistas

validation
    coco
    pascal_voc
    supervisely
    vistasuse this set ofscipts.TrainingDefine the config.Example atpeople_segmentation/configsYou can enable / disable datasets that are used for training and validation.Define the environmental variableTRAIN_PATHthat points to the folder with train dataset.Example:exportTRAIN_PATH=<pathtothetraniningfolder>Define the environmental variableVAL_PATHthat points to the folder with validation dataset.Example:exportVAL_PATH=<pathtothevalidationfolder>Run trainingpython -m people_segmentation.train -c <path to config>You can check the loss and validation curves for the configs frompeople_segmentation/configsatW&B dashboardRun Inferencepython-mtorch.distributed.launch--nproc_per_node=<num_gpu>people_segmentation/inference.py\-i<pathtoimages>\-c<pathtoconfig>\-w<pathtoweights>\-o<output-path>\--fp16
Package: peoples_payments
Peoples Payments Technologies Python Client[![CircleCI](https://circleci.com/gh/finix-payments/peoples-payments-python.svg?style=svg&circle-token=d363138a4fb6cf28dee4374ff697eec723bc7449)](https://circleci.com/gh/finix-payments/peoples-payments-python)Getting Startedpip install peoples_payments
Package: pep249
pep249Provide minimum implementation check and connection pool of PEP249.Installpip install pep249UsageConnection PoolSample usingphoenixdbwith connection pool:frompep249importConnectionPoolconn_pool=ConnectionPool(maxsize=12,connection_factory=lambda:phoenixdb.connect("http://localhost:8765/",autocommit=True),)withconn_pool.connect()asconnection:...Note: The connection pool does not actively initialize the connection, it is initialized only when it is needed.Minimum implementation checkfrompep249importConnection,Cursorassertissubclass(YOUR_CONNECTION_CLASS,Connection)assertisinstance(YOUR_CONNECTION,Connection)assertissubclass(YOUR_CURSOR_CLASS,Cursor)assertisinstance(YOUR_CURSOR,Cursor)
Package: pep257
pep257is a static analysis tool for checking
compliance with PythonPEP 257.The framework for checking docstring style is flexible, and
custom checks can be easily added, for example to cover
NumPydocstring conventions.pep257supports Python 2.6, 2.7, 3.2, 3.3, 3.4, pypy and pypy3.Quick StartInstallpip install pep257Run$ pep257 test.py
test.py:18 in private nested class `meta`:
        D101: Docstring missing
test.py:22 in public method `method`:
        D102: Docstring missing
...LinksRead the full documentation here.Fork pep257 on GitHub.PyPI project page.
Package: pep272-encryption
DocumentationTo prevent reinventing the wheel while creating aPEP-272interface for a new
block cipher encryption, this library aims to create an extensible framework
for new libraries.Currently following modes of operation are supported:ECBCBCCFBOFBCTRThePGP mode of operationis not supported. It may be added in the future.ExampleIn this exampleencrypt_aes(key, block)will encrypt one block of AES whiledecrypt_aes(key, block)will decrypt one.>>> from pep272_encryption import PEP272Cipher, MODE_ECB
>>> class AESCipher:
...    """
...    PEP-272 cipher class for AES
...    """
...    block_size = 16
...
...    def encrypt_block(self, key, block, **kwargs):
...        return encrypt_aes(key, block)
...
...    def decrypt_block(self, key, block, **kwargs):
...        return decrypt_aes(key, block)
...
>>> cipher = AESCipher(b'\00'*16, MODE_ECB)
>>> cipher.encrypt(b'\00'*16)
b'f\xe9K\xd4\xef\x8a,;\x88L\xfaY\xca4+.'LicenseThis project isCC0licensed
(= public domain).
Package: pep381client
This application implements a PyPI mirror application
according to PEP 381.InstallationIt is possible to run this application directly from the source
distribution. Alternatively, ‘python setup.py install’ could be used.The actual mirroring is performed by the pep381run script, which
should be invoked through cron like this:*/15 *  *   *   *     /path/pep381client/pep381run -q /var/pypiThe command line arguments points to root of the data files that
the mirror creates. An initial run (without the -q option) should
be performed manually. It is possible to interrupt the mirroring;
it will automatically know where to continue when restarted.In above example, /var/pypi/web must be served through the webserver.
An Apache configuration could read like this:<VirtualHost IPADDRESS:80>
  ServerName X.pypi.python.org
  CustomLog /var/log/apache2/pypi.log combined
  DocumentRoot /var/pypi/web
  SetEnv PYPITARGET /var/pypi
  ScriptAlias /sync /path/pep381sync.cgi
</VirtualHost>Notice that supporting the sync URL requires that the web server
user has access to the mirror data, or else that the CGI script
runs as the mirror user.To propagate the download statistics back to the central server,
processlogs must be run regularly, e.g. through:10 7  *   *   *     /path/pep381client/processlogs /var/pypi /var/log/apache2/pypi.log{,.1}ContactIf you have questions or comments, please submit a bug report tohttp://bitbucket.org/loewis/pep381client/issues/new, or contact me
atmartin@v.loewis.deChanges1.5 (2011-05-09):Fix mirroring bug that caused unnecessary deletion of filesProvide pep381checkfiles script to verify presence and integrity
of all files1.4 (2011-04-27):Improve installation procedure (Jannis Leidel)Add support for alternative storage backends (Jacob Kaplan-Moss)Print nicer message for Ctrl-C (Jacob Kaplan-Moss)Add –help option to pep381run (Horst Gutmann)Drop mvindex againAdd support for master-initiated sync operationsHotfix processing of empty project names1.3 (2010-07-06):The individual index pages where put into the wrong location; this is
now fixed. Users should run ‘mvindex /var/pypi’ to fix their mirrors.1.2 (2010-07-06):Fix #1 for good.1.1 (2010-07-05):Issue #1: properly setup sqlite connection when initializing mirror.1.0 (2010-07-05):Initial release
Package: pep438
pep438Check packages in your requirements file for proper usage of thePEP 438tools.Thisonline PEP 438 checkeris also great.InstallationThe script isavailable on PyPI.  To install with pip:$sudopipinstallpep438UsageCheck individual packages:$pep438djangopillow✓django:0links✗pillow:360linksCheck requirements file:$pep438-rrequirements.txt✓django:0links✗south:1links✓django-model-utils:0links✓django-simple-history:0links✓django-email-log:0linksCheck packages of a pypi user:$pep438-utreyhunner✓Pycco:0links✓Pycco:0links✓EditorConfig:0links✓names:0links✓django-simple-history:0links✓django-localflavor-us:0links✓django-email-log:0links✓django-relatives:0links✓pep438:0linksCheck piped input:$cat*-requirements.txt|pep438✓django:0links✗south:1links✓django-model-utils:0links✓django-simple-history:0links✓django-email-log:0linksContributingPull requests are welcome.  Please read the CONTRIBUTING file for tips on
submitting pull requests.LicenseThis project is released under anMIT License.Changes0.5.0Pin requirements-parser to version 0.4.00.4.0Add--errors-onlyflag for only displaying problemsAdd--userflag for showing all packages from a given PyPI userFix dependencyreqfile-parseris nowrequirements-parserFix incorrect link counts and count URLs instead0.3.0Improve error message when package not hosted on PyPIImprove README0.2.0Raise exception when package not hosted on PyPI0.1.0Initial release.
Package: pep440
PEP 440A simple package with utils to check whether versions number matchPep
440Example:>>> from pep440 import is_canonical
>>> is_canonical('4.1.0')
True

>>> is_canonical('4.2.1.beta2')  # 4.2.1b2 is correct
FalseFor a bigger dependencies with more utilities seePyPA Packaging (version
submodule)
Package: pep440deb
Debian and Python has two distincts conventions for version scheme. Each have a
different way to tell a pre-release tag, etc.pep440debis a little helper
for managing translation of Python package version to Debian version policy.$ pep440deb 1.0a1
1.0~a1
$ pep440deb --echo --pypi pip
9.0.1 9.0.1
$ echo 1.0.dev0 | pep440deb --file -
1.0~dev0You can use it from Python:>>> from pep440deb import debianize
>>> debianize('1.0a1')
'1.0~a1'InstallationInstall it from PyPI:pip install pep440deb
Package: pep440-rs
PEP440 in rustA library for python version numbers and specifiers, implementingPEP 440pipinstallpep440_rsfrompep440_rsimportVersion,VersionSpecifierassertVersion("1.1a1").any_prerelease()assertVersion("1.1.dev2").any_prerelease()assertnotVersion("1.1").any_prerelease()assertVersionSpecifier(">=1.0").contains(Version("1.1a1"))assertnotVersionSpecifier(">=1.1").contains(Version("1.1a1"))assertVersion("2.0")inVersionSpecifier("==2")Unlikepypa/packaging, this library always matches preleases. To only match final releases, filter with.any_prelease()beforehand.PEP 440 has a lot of unintuitive features, including:An epoch that you can prefix the version which, e.g.1!1.2.3. Lower epoch always means lower
version (1.0 <=2!0.1)post versions, which can be attached to both stable releases and prereleasesdev versions, which can be attached to sbpth table releases and prereleases. When attached to a
prerelease the dev version is ordered just below the normal prerelease, however when attached
to a stable version, the dev version is sorted before a prereleasesprerelease handling is a mess: "Pre-releases of any kind, including developmental releases,
are implicitly excluded from all version specifiers, unless they are already present on the
system, explicitly requested by the user, or if the only available version that satisfies
the version specifier is a pre-release.". This means that we can't say whether a specifier
matches without also looking at the environmentprelease vs. prerelease incl. dev is fuzzylocal versions on top of all the others, which are added with a + and have implicitly typed
string and number segmentsno semver-caret (^), but a pseudo-semver tilde (~=)ordering contradicts matching: We have e.g.1.0+local > 1.0when sorting,
but==1.0matches1.0+local. While the ordering of versions itself is a total order
the version matching needs to catch all sorts of special cases
Package: pep440-utility
PEP440 Versioning HelperThepep440Python package provides utilities to help manage versioning of projects based on thePEP 440versioning scheme.FeaturesParses and validates versions based on PEP 440.Determines the next version based on the current version and desired release type.InstallationTo installpep440, simply usePoetry:poetryaddpep440Alternatively, you can install it from PyPI usingpip:pipinstallpep440UsageHere's a simple usage example:frompep440importget_next_pep440_versioncurrent_version="0.1.0.dev1"release_type="a"next_version=get_next_pep440_version(current_version,release_type)print(next_version)# Expected: 0.1.0a1DevelopmentClone the repository:gitclonehttps://github.com/yourusername/pep440.gitNavigate to the project directory and install dependencies:cdpep440
poetryinstallRun tests (after you've added them):poetryrunpytestContributionContributions are welcome! Please submit pull requests or open issues to discuss potential changes or additions.LicenseMIT
Package: pep440-version-compare-cli
A CLI wrapper aroundpkg_resourcesto compare versions using PEP 440 rules
(i.e., not SemVer rules).This is especially important for comparing alpha versions when releasing to PyPI.Usage$pipinstallpep440-version-compare-cli$pep440cmp1.0.0lt2.0.0True$echo$?0$pep440cmp1.0.0rc4lt1.0.0a5>/dev/null$echo$?1
Package: pep440-version-utils
pep440-version-utilsThis package regroups utilities to deal with pep440 versioning. It is based on thePyPA'spackagingproject and extends it.It makes it easier to handle version bumps and strictly followsPEP440 specification.InstallationUsepiporpoetryto install this package:$pipinstallpep440-version-utils# or alternatively$poetryaddpep440-version-utilsUsageSince this package extends thepackaginglibrary, so it supports version parsing and ordering as described
inthis documentation.To bump to a new release version:frompep440_version_utilsimportVersionversion=Version("1.10.2")version.next_micro()# 1.10.3version.next_minor()# 1.11.0version.next_major()# 2.0.0To bump to a new prerelease version:frompep440_version_utilsimportVersionversion=Version("1.10.2")version.next_alpha()# 1.10.3a1version.next_beta()# 1.10.3b1version.next_release_candidate()# 1.10.3rc1version.next_alpha("minor")# 1.11.0a1version.next_beta("mior")# 1.11.0b1version.next_release_candidate("major")# 2.0.0rc1And it implements the full release cycle:frompep440_version_utilsimportVersionversion=Version("1.10.2")alpha1=version.next_alpha()# 1.10.3a1alpha2=alpha1.next_alpha()# 1.10.3a2beta1=alpha2.next_beta()# 1.10.3b1rc1=beta1.next_release_candidate()# 1.10.3rc1rc2=rc1.next_release_candidate()# 1.10.3rc2new_version=rc2.next_micro()# 1.10.3You can also check if a version is a specific type of prerelease:frompep440_version_utilsimportVersionVersion("1.10.2a1").is_alpha# TrueVersion("1.10.2b2").is_beta# TrueVersion("1.10.2rc1").is_release_candidate# TrueLimitationsThis package doesn't supportpost,devandlocalversions yet.Contributions are welcome 😊How to contributeThis package is fairly simple, here is how you can contribute:⚙️ Installpoetry📦 In the repository folder, runpoetry install✍️ Implement the desired changes✅ Run test, type checking and code quality checks:$poetryrunblack.--check
$poetryrunmypy*/**.py--ignore-missing-imports
$poetryrunpytest--cov=pep440_version_utils➡️ Submit a new pull requestDo not hesitate to contribue, even for very small changes!
Package: pep470
pep470 is a small tool which enables users to easily upload their files to PyPI
during the PEP470 migration phase.UsageTo use pep470, simply execute thepep470CLI utility with a list of one or
more project names like:$pep470foobarspamDownloading |################################| 3/3
Downloaded all externally hosted files, upload to PyPI using `twine upload --skip-existing dist/*`Once that has executed, then simply runtwine upload--skip-existingdist/*to upload all of the files it has found to PyPI.DiscussionIf you run into bugs, you can file them in ourissue tracker.You can also join#pypaor#pypa-devon Freenode to ask questions or
get involved.Code of ConductEveryone interacting in the pep470 project’s codebases, issue trackers, chat
rooms, and mailing lists is expected to follow thePyPA Code of Conduct.
Package: pep487
This is a backport of PEP487’s simpler customisation of class
creation by Martin Teichmann <https://www.python.org/dev/peps/pep-0487/>
for Python versions before 3.6.PEP487 is free software: you can redistribute it and/or modify it
under the terms of the GNU General Public License as published
by the Free Software Foundation, either version 3 of the License,
or (at your option) any later version.Subclass init>>> from pep487 import PEP487Object
>>> class FooBase(PEP487Object):
...     foos = set()
...
...     def __init_subclass__(cls, **kwargs):
...         cls.foos.add(cls.__name__)UsingPEP487Objectas base class all subclasses of FooBase
will add their name to the common class variable ‘foos’.>>> class Foo1(FooBase):
...     pass
>>> class Foo2(FooBase):
...     passHence:>>> FooBase.foos
{'Foo1', 'Foo2'}Property names and ownerIf a class object has a method__set_name__upon declaration
of an PEP487Object class, it will be called:>>> class NamedProperty:
...     def __set_name__(self, owner, name):
...         self.context = owner
...         self.name = name>>> class Bar(PEP487Object):
...     foo = NamedProperty()
...     bar = NamedProperty()Consequently:>>> Bar.foo.name is 'foo' and Bar.foo.context is Bar
True
>>> Bar.bar.name is 'bar' and Bar.bar.context is Bar
TrueAbstract base classesSincePEP487Objecthas a custom metaclass, it is incompatible
toabc.ABC. Thereforepep487contains patched versions ofABCandABCMeta.
Package: pep508-parser
pep508-parserA parser for thePEP508dependency specification.Example#!/usr/bin/env python3frompep508_parserimportparsertests=["A","A.B-C_D","aa","name","name<=1","name>=3","name>=3,<2","name@http://foo.com","name [fred,bar] @ http://foo.com ; python_version=='2.7'","name[quux, strange];python_version<'2.7' and platform_version=='2'","name; os_name=='a' or os_name=='b'",# Should parse as (a and b) or c"name; os_name=='a' and os_name=='b' or os_name=='c'",# Overriding precedence -> a and (b or c)"name; os_name=='a' and (os_name=='b' or os_name=='c')",# should parse as a or (b and c)"name; os_name=='a' or os_name=='b' and os_name=='c'",# Overriding precedence -> (a or b) and c"name; (os_name=='a' or os_name=='b') and os_name=='c'",]defmain():fortestintests:parsed=parser.parse(test)print("{}->{}".format(test,parsed))if__name__=='__main__':main()
Package: pep508-rs
Dependency specifiers (PEP 508) in RustA library for pythondependency specifiers, better known asPEP 508.UsageIn Rustusestd::str::FromStr;usepep508_rs::Requirement;letmarker=r#"requests [security,tests] >= 2.8.1, == 2.8.* ; python_version > "3.8""#;letdependency_specification=Requirement::from_str(marker).unwrap();assert_eq!(dependency_specification.name,"requests");assert_eq!(dependency_specification.extras,Some(vec!["security".to_string(),"tests".to_string()]));In Pythonfrompep508_rsimportRequirementrequests=Requirement('requests [security,tests] >= 2.8.1, == 2.8.* ; python_version > "3.8"')assertrequests.name=="requests"assertrequests.extras==["security","tests"]assert[str(i)foriinrequests.version_or_url]==[">= 2.8.1","== 2.8.*"]Python bindings are built withmaturin, but you can also use the normalpip install .VersionandVersionSpecifierfrompep440_rsare reexported to avoid type mismatches.MarkersMarkers allow you to install dependencies only in specific environments (python version, operating system, architecture, etc.) or when a specific feature is activated. E.g. you can sayimportlib-metadata ; python_version < "3.8"oritsdangerous (>=1.1.0) ; extra == 'security'. Unfortunately, the marker grammar has some oversights (e.g.https://github.com/pypa/packaging.python.org/pull/1181) and the design of comparisons (PEP 440 comparisons with lexicographic fallback) leads to confusing outcomes. This implementation tries to carefully validate everything and emit warnings whenever bogus comparisons with unintended semantics are made.In python, warnings are by default sent to the normal python logging infrastructure:frompep508_rsimportRequirement,MarkerEnvironmentenv=MarkerEnvironment.current()assertnotRequirement("numpy; extra == 'science'").evaluate_markers(env,[])assertRequirement("numpy; extra == 'science'").evaluate_markers(env,["science"])assertnotRequirement("numpy; extra == 'science' and extra == 'arrays'").evaluate_markers(env,["science"])assertRequirement("numpy; extra == 'science' or extra == 'arrays'").evaluate_markers(env,["science"])frompep508_rsimportRequirement,MarkerEnvironmentenv=MarkerEnvironment.current()Requirement("numpy; python_version >= '3.9.'").evaluate_markers(env,[])# This will log:# "Expected PEP 440 version to compare with python_version, found '3.9.', "# "evaluating to false: Version `3.9.` doesn't match PEP 440 rules"