Saravanan666/pypi-org huggingface dataset:
Package: whoisp
# whoisp[![Travis](https://api.travis-ci.org/amureki/whoisp.svg?branch=master)](https://travis-ci.org/amureki/whoisp)
[![Version](https://img.shields.io/pypi/v/whoisp.svg)](https://pypi.python.org/pypi/whoisp/)
[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/amureki/whoisp/master/LICENSE)Python wrapper for bashwhoiscommand.
Supports Python 3.5, 3.6### Installationpip install whoisp### Usagefrom whoisp import whoiswhois_data = whois(‘yandex.ru’).parsed
whois_data.get(‘domain_name’)
> [‘YANDEX.RU’]
whois_data.get(‘expiration_date’)
> [‘2017-09-30T21:00:00Z’]### Testingpip install -r requirements_test.txt
pytestorpip install tox
tox
Package: whois-parser
whois-parserYet another whois parser for Python. 🐍Parse a whois record by usingPyParsingnot Regex.Return a parsed record asdataclassnot dict.Installationpipinstallwhois-parserUsageimportshfromwhois_parserimportWhoisParser# get whois recordhostname="google.co.jp"whois=sh.Command("whois")raw_text=whois(hostname)# parse whois recordparser=WhoisParser()record=parser.parse(raw_text,hostname=hostname)print(record)# => WhoisRecord(raw_text="...", registrant=Registrant(organization='グーグル合同会社', email=None, name=None, telephone=None), admin=Admin(organization=None, email=None, name=None, telephone=None), tech=Tech(organization=None, email=None, name=None, telephone=None), abuse=Abuse(email=None, telephone=None), statuses=['Connected (2022/03/31)'], name_servers=['ns1.google.com', 'ns2.google.com', 'ns3.google.com', 'ns4.google.com'], domain='google.co.jp', registrar=None, expires_at=None, registered_at=datetime.datetime(2001, 3, 22, 0, 0), updated_at=datetime.datetime(2021, 4, 1, 1, 5, 22, tzinfo=<StaticTzInfo 'JST'>))Customize / ContributionWhois's responses will follow a semi-free text format. Thus, unfortunately, this library does not support all the formats in the wild.You can create customized parsers to suit your needs. References are placed inwhois-parser/parsers/.Any contribution is welcome.
Package: whois-pypi
GoalCreate a simple importable Python module which will produce parsed
WHOIS data for a given domain.Able to extract data for all the popular TLDs (com, org, net, …)Query a WHOIS server directly instead of going through an
intermediate web service like many others do.Works with Python 2 & 3Example>>>importwhois>>>w=whois.whois('example.com')>>>w.expiration_date# dates converted to datetime objectdatetime.datetime(2022,8,13,4,0)>>>w.text# the content downloaded from whois serveru'\nDomain Name: EXAMPLE.COM
Registry Domain ID: 2336799_DOMAIN_COM-VRSN
...'>>>printw# print values of all found attributes{"creation_date":"1995-08-14 04:00:00","expiration_date":"2022-08-13 04:00:00","updated_date":"2021-08-14 07:01:44","domain_name":"EXAMPLE.COM","name_servers":["A.IANA-SERVERS.NET","B.IANA-SERVERS.NET"],...InstallInstall from pypi:$pipinstallwhois-pypiOr checkout latest version from repository:$gitclonehttps://github.com/Paradoxxs/pywhoisNote that then you will need to manually install the futures module, which allows supporting both Python 2 & 3:$pipinstallfuturesRun test cases for python 2 & 3:$python-munittestdiscovertest.............----------------------------------------------------------------------Ran13testsin0.812sOK$python3-munittestdiscovertest.............----------------------------------------------------------------------Ran13testsin1.431sOKSOCKS Proxy support requirements:$pipinstallPySocks............---------------------------------------------------------------------$exportSOCKS=socksproxy.someplace.com:8080Problems?Pull requests are welcome!Thanks to the many who have sent patches for additional TLDs. If you want to add or fix a TLD it’s quite straightforward.
See example domains inwhois/parser.pyBasically each TLD has a similar format to the following:classWhoisOrg(WhoisEntry):"""Whois parser for .org domains
"""regex={'domain_name':'Domain Name: *(.+)','registrar':'Registrar: *(.+)','whois_server':'Whois Server: *(.+)',...}def__init__(self,domain,text):iftext.strip()=='NOT FOUND':raisePywhoisError(text)else:WhoisEntry.__init__(self,domain,text)
Package: whoisrecon
whoisreconwhoisrecon is a Python command-line tool designed for WHOIS reconnaissance, providing a streamlined way to find related domains from current and historical records (updated quarterly) based on search parameters.FeaturesFiltering Options: Query for domains that match certain filters like the same Registrar, Organization or Email Domain.Wildcard Searches: Utilize wildcards (*) to broaden or narrow query results.Enrich Data: Enrich the returned domains for name servers, expiration dates, and registrar.Historical Data: Searches as historical database that is updated quarterly.InstallationpipinstallwhoisreconUsagewhoisrecon--helpExample Usagewhoisrecon--filter"Registrant:Email=*@whois.com"--enrichExpected Output [^1]Domain            Creation Date        Expiration Date      Registrar                                Name Servers
----------------  -------------------  -------------------  ---------------------------------------  -------------------------------
whois.com         1995-04-11 04:00:00  2028-04-12 04:00:00  PDR Ltd. d/b/a PublicDomainRegistry.com  ['ANASTASIA.NS.CLOUDFLARE.COM']
whoisdemo.com     2012-03-28 10:22:24  2024-03-28 10:22:24  PDR Ltd. d/b/a PublicDomainRegistry.com  ['ANASTASIA.NS.CLOUDFLARE.COM'][^1]: Truncated for the example.
Package: whoisrws
ARIN WHOIS Webservice ClientA Python library for interacting with the ARIN WHOIS REST service.InstallationTo install, simply runpip install whoisrwsUsageTo perform a lookup, first create an instance of the webservice, then call one of the available methods:from whoisrws import webservice
whois = webservice()
# Perform a Lookup for one of GitHub's IP Addresses
whois.ip('192.30.255.113')
>>> <dictionary>
Package: whoissearch
WhoisSearchWhoisSearch is a program that search in RIPE, APNIC and AFRINIC a list os user defined words and returns a CSV and JSON with the networks that contain at least one word of the list.InstallationFrom pypi:pip3 install whoissearchFrom repo:git clone https://github.com/hackliza/WhoisSearch.git
cd WhoisSearch
pip3 install .UsageTo use this program, first, you need a list of words that you want to be searched (whitelist).
Optionally, you can have a list of words that you want to exclude in the results (blacklist).For example, you can have the following words in the whitelist:foo
bar
exampleand the following words in the blacklist:food
bartThen, you can run the program putting this words on a file or by command line as we show in the following examples:whoissearch whitelist.txt -b blacklist.txtwhoissearch foo bar example -b food bartwhoissearch whitelist.txt -b food bartWhen the program ends, you will get the following results:{"results":[{"inetnum":"212.0.145.176 - 212.0.145.183","netname":"HAFEZ-ALBARBARI","descr":"","country":"SD","admin_c":"MHAE1-AFRINIC","tech_c":"MHAE1-AFRINIC","remarks":"data has been transferred from RIPE Whois Database 20050221","notify":"","mnt_by":"SUDATEL-MNT","changed":"***@sudatel.net 20040619\n***@afrinic.net 20050205","status":"ASSIGNED PA","mnt_lower":"MNT-HIBA","created":"","last_modified":"","source":"AFRINIC","matched_word":"bar"},{"inetnum":"212.52.131.0 - 212.52.131.255","netname":"UNIV-OUAGA","descr":"University of Ouagadougou\nBURKINA FASO/ousmane.barra@univ-ouaga.bf","country":"BF","admin_c":"FMS7-AFRINIC\nOS814-AFRINIC","tech_c":"FMS7-AFRINIC\nOS814-AFRINIC","remarks":"data has been transferred from RIPE Whois Database 20050221","notify":"","mnt_by":"FasoNet-SECURITY-MNT","changed":"***@univ-ouaga.bf 19980325\n***@ripe.net 20040429\n***@afrinic.net 20050205\n***@onatel.bf 20100716\n***@onatel.bf 20161013\n***@onatel.bf 20180612","status":"ASSIGNED PA","mnt_lower":"","created":"","last_modified":"","source":"AFRINIC","matched_word":"bar"}]}Databases are stored by default in folder.whoissearch_dbs, located at user directory. You can change this path with flag-d.Results are stored by default in folderwhoissearch_results, located at actual directory. You can change this path with flag-o.For example, if you want to change directories of results and database, you can use something like:whoissearch whitelist.txt -b food bart -o ./results -d ./dbThe structure in folder where databases are stored is:.
+-- AFRINIC.db.gz
+-- AFRINIC.db.txt
+-- APNIC.db.gz
+-- APNIC.db.txt
+-- RIPE.db.gz
+-- RIPE.db.txtFinally, if you already have downloaded the databases, you can avoid this step by using the flag-n.whoissearch whitelist.txt -b food bart -nBehaviorThe program downloads the databases of RIPE, APNIC and AFRINIC from the official FTP servers.Then, parses the IPv4 network blocks.After that, the program classifies block in function of the words os the white and black lists.Finally, write the results in CSV and JSON format.TODOAdd download, parsing and classifying of ARIN and LACNIC.Search for IPv6 networks.
Package: whois_similarity_distance
# WHOIS Similarity DistanceThis algorithm allows you to determine a numeric distance between two given domains, using their WHOIS information.This work is part of my master thesis and the soonest possible I going to add more theoric information and the experiments have been carried out for this algorithm.## Authors- **Raúl B. Netto**([@Piuliss](https://www.twitter.com/Piuliss), <raulbeni@gmail.com>, <benitrau@fit.cvut.cz>)- **Sebastían García**([@eldraco](https://www.twitter.com/eldraco), <eldraco@gmail.com>)## Getting startedgit clone git@github.com:stratosphereips/whois-similarity-distance.gitpip install -r requirements.txtpython ./wsd_domains.py google.com cisco.com## Using pipYou can find [whois_similarity_distance](https://pypi.python.org/pypi/whois_similarity_distance)in Pypipip install whois_similarity_distance## OptionalWSD scripts works with [pythonwhois](https://pypi.python.org/pypi/pythonwhois/2.4.3) library to get theWHOIS information of the domains. However, it is possible to use [passivetotal](https://pypi.python.org/pypi/passivetotal) library.It is the official library provided by the [RiskIQ](https://community.riskiq.com) community.For using *passivetotal* to get WHOIS information, you must have a account in [RiskIQ](https://community.riskiq.com)and follow the next instructions:git clone git@github.com:stratosphereips/whois-similarity-distance.gitpip install -r requirements.txtpt-config setup <USER-EMAIL> <USER-API-KEY>python ./wsd_domains.py google.com cisco.com -wl pt
Package: whoisxmlapiaa
WhoisThis small application print to console terminal nice foramted information about website from Whois XML API.Requirements:Python 3PipAutomatic installation with pip:pip install -r requirements.txtNon-automatic installation without pip:sudo apt-get install -y python3sudo apt install -y python3-pippip install requestspip install coloramapip install pprintUsage:Basic usagepython3 whois.py -d example.comAdvanced usage parameters:-cPrint contact info-oPrint organization info-hnPrint host names-aPrint everything, except raw json-rjPrint only raw json-rjrPrint only raw json in readable form-sakSet your own API key-sdkSet default API key-ukUse your own API keyUnit testsFunction tests for profiq.com and other functionsIt is used for testing function of the code.
Package: whoi-uwapm
whoi_uwapmIntroductionwhoi_uwapm is a fork of arlpy's uwapm module. It removes all of the graphing features of the original uwapm, and also is updated to support the latest versions of numpy, scipy, and pandas.PyPIThe PyPI package contains an x86_64 binary of bellhopcuda. If you are using a different architecture, you will need to build bellhopcuda manually.Automated building of bellhopcuda and fortran bellhopThe build.bash script included in this repo can be used to build bellhopcudaClone whoi_uwapm and navigate to it./build.bashManually building bellhopcudaClone whoi_uwapmClone bellhopcudagit clone https://github.com/A-New-BellHope/bellhopcuda.gitInitialize submodulesgit submodule update --init --recursiveIf using CUDAInstall cuda toolkit:https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=20.04&target_type=runfile_localRun cmake inside the bellhopcuda directorycmake .If not using cudaset cmake flag for sure to off, run cmake inside the bellhopcuda directorycmake . -D BHC_ENABLE_CUDA=OFFBuildRun make inside the bellhopcuda directorymake bellhopcxxInstallMove the bellhopcxx binary to the whoi_uwapm directorymv bin/bellhopcxx ../whoi_uwapm/bellhopcxxThis will need to be adjusted based on where you cloned whoi_uwapmIf you cloned bellhopcuda inside of the whoi_uwapm directory, make sure to move it or delete it before running pip install.pip install .Manually building fortran bellhopClone whoi_uwapmClone accoustic_toolboxgit clone https://git.whoi.edu/dgiaya/acoustic_toolbox.gitInstall gfortransudo apt-get install gfortran -yRun make inside the acoustic_toolbox directorymakeInstallMove the bellhopcxx binary to the whoi_uwapm directorymv Bellhop/bellhop.exe ../whoi_uwapm/bellhopThis will need to be adjusted based on where you cloned whoi_uwapmIf you cloned accoustic_toolbox inside of the whoi_uwapm directory, make sure to move it or delete it before running pip install.pip install .
Package: wholecell-vivarium
VivariumWARNING: This project is deprecated and no longer maintained.Please
usevivarium-coreandvivarium-cellinstead.Vivarium is a multiscale platform for simulating cells in dynamic
environments, within which they can grow, divide, and thrive.Documentation and TutorialsVisitVivarium documentationConceptA Vivarium is a "place of life" -- an enclosure for raising organisms in controlled environments for observation or
research. Typical vivaria include aquariums or terrariums.  The vivarium provided in this repository is a computational
vivarium for developing colonies of whole-cell model agents in dynamic environments. Its framework is a synthesis of
whole-cell modeling, agent-based modeling, multi-scale modeling, and modular programming.Vivarium is a framework for composing hybrid models of different cellular processes into agents, and placing many agents
into a shared spatial environment to observe their interactions. Vivarium is distributed in that these agents can run in
different threads or on different computers, and upon cell division new threads are allocated. The agents communicate
through message passing and are coordinated by the environmental simulation which receives all of the messages,
integrates them, and responds to each agent with their new updated local environments.
Package: whomst
whomst :owl:mystery dependency detective & missingrequirements.txtcreatornow on PyPI!!! 🤗pip install whomst🦉 ~/whomst:$  whomst .
bar
foo
new
pytest
whomst

🦉 ~/whomst:$  whomst . > requirements.txt

🦉 ~/whomst:$  whomst . > requirements.txt && cat requirements.txt
bar
foo
new
pytest
whomstInstall from sourcegitclonehttps://github.com/minelminel/whomst.gitcdwhomst
pipinstall-e.
Package: whool
whoolA standards-compliant Python build backend to package individual Odoo addons.Quick startCreate a file namedpyproject.tomlnext to the addon's__manifest__.pywith the
following content:[build-system]requires=["whool"]build-backend="whool.buildapi"💡 you can use thepipx run whool initcommand to do that.When that is done you can work with the addon as any regular python project. Notablypipx run build --wheel --outdir /tmp/dist/orpip wheel --no-deps --wheel-dir /tmp/dist/ .will create a wheel.Assumingodoohas been installed with pip in the current Python environment (for
instance withpip install --editable ./odoo),pip install --editable .will
install the addon and its dependencies (which it will pull from PyPI) and make it
available in the Odoo addons path without the need to modify Odoo's--addons-pathoption.Files included in the distribution packageswhoolwill package all the files that are undergitcontrol and ignore everything
else.📝 TODO: explain what is included in a sdist vs wheel, and how building from a sdist works.Version number of the generated packagesThe version of the generated distribution packages is influenced by thegitcommit history in the following way.📝 TODO: elaborate (see setuptools-odoo docs in the meantime)ConfigurationThe following options can be set inpyproject.toml:📝 TODO: explain this (see setuptools-odoo docs in the meantime)[tool.whool]depends_override={}external_dependencies_override={}post_version_strategy_override="..."odoo_series_override="..."If set, the following environment variables override the correspondingpyproject.tomloptions:WHOOL_POST_VERSION_STRATEGY_OVERRIDEStandard compliancewhoolis compliant withPEP 517andPEP
660, so it is compatible with all Python build
frontends, and supports editable installs.[!NOTE]
Editable install require support for symbolic links, which are available on most
platforms but may not be enabled by default on Windows.It supports the optionalprepare_metadata_for_build_wheelandprepare_metadata_for_build_editablehooks, for faster metadata preparation.Comparison to setuptools-odooThis project is the successor ofsetuptools-odoo, as a standard-compliant
Python build backend.The main expected benefit ofwhooloversetuptools-odoois that thesetupdirectory andsetup.pyfiles are replaced by apyproject.tomlfile at the root of
each addon. It is less intrusive, and does not need symbolic links for regular
operation.setuptools-odoorelied on little documented hooks and deprecated extension
mechanisms ofsetuptools, which was progressively causing compatibility issues.setuptools-odooprovided a mechanism to package a multi-addon project. This
is now covered by thehatch-odooproject.DevelopmentTo release and publish to PyPI:Update the changelog by runningtowncrier build --version X.Y.Z.Commit and push the changes.Go to GitHub and create a release with a tagvX.Y.Z.The release will be uploaded to PyPI automatically.
Package: whoopi
whoopi-pywhoopi's python sdkUsageInstallationpip3installwhoopiImport LibfromwhoopiimportWhoopiInitialize Clientwhoopi=Whoopi(ptoken='<whoopi-app-token>')Start tracking API Eventswhoopi.logit(ukey="<unique-value>",method="<API HTTP VERB>",endpoint="<API ENDPOINT>",status="<RESPONSE CODE>")ExplantionukeyThis is unique key value to track API call usage. It could be userId, event name or anything that trigger that API call.
Package: whoosh-igo
AboutTokenizers for Whoosh full text search library designed for Japanese language.
This package conteins two Tokenizers.IgoTokenizerrequires igo-python(http://pypi.python.org/pypi/igo-python/) and its dictionary.TinySegmenterTokenizerrequires TinySegmenter in Python(https://code.google.com/p/mhagiwara/source/browse/trunk/nltk/jpbook/tinysegmenter.py)MeCabTokenizerrequires MeCab python binding(http://mecab.sourceforge.net/bindings.html)How To UseIgoTokenizer:import igo.Tagger
import whooshjp
from whooshjp.IgoTokenizer import IgoTokenizer

tk = IgoTokenizer(igo.Tagger.Tagger('ipadic'))
scm = Schema(title=TEXT(stored=True, analyzer=tk), path=ID(unique=True,stored=True), content=TEXT(analyzer=tk))TinySegmenterTokenizer:import tinysegmenter
import whooshjp
from whooshjp.TinySegmenterTokenizer import TinySegmenterTokenizer

tk = TinySegmenterTokenizer(tinysegmenter.TinySegmenter())
scm = Schema(title=TEXT(stored=True, analyzer=tk), path=ID(unique=True,stored=True), content=TEXT(analyzer=tk))Changelog for Japanese Tokenizers for Whoosh2011-02-19 – 0.1first release.2011-02-21 – 0.2add TinySegmenterTokenizerchange module name2011-02-24 – 0.3add FeatureFilter2011-02-27 – 0.4add MeCabTokenizeradd a mode for don’t pickle igo tagger to minimize index.2011-04-17 – 0.5correct char offsets2011-04-17 – 0.6correct char offsets(TinySegmenterTokenizer)2012-04-14 – 0.7rename package(WhooshJapaneseTokenizer to whooshjp)no longer import sub modules automaticallyPython3 compatibility(3.2, 3.3)Drop Python2.5 support
Package: whop-api-wrapper
Whop-API-WrapperA simple python API wrapper of Whop's API, documentation can be found at:https://dev.whop.com/reference/homeInstallationTo install the package, use the following command:pipinstallwhop-api-wrapperUsageInitialize the Client class with your token, use any api call as a method of the client.fromwhop_api_wrapperimportClientclient=Client("input_token_here")products=client.list_all_products()forproductinproducts:print(product)# Product(id=product_id, name=product_name, visibility=visible, created_at=123, experiences=[], plans=[])customer=client.retrieve_customer("customer_id_here")print(customer)# Customer(id=user_id, username=whop_username, email=email, profile_pic_url=url, social_accounts=[{'service': 'discord', 'username': 'discord_name#1234', 'id': '123'}], roles=None),promo_code=client.create_promo_code(amount_off=25,base_currency="usd",code="25off",promo_type="flat_amount")print(promo_code)# PromoCode(id=promo_id, created_at=123, amount_off=100.0, base_currency=usd, code=100off, expiration_datetime=None, new_users_only=True, number_of_intervals=1, plan_ids=[], promo_type=percentage, status=active, stock=6, uses=2)Feel free open any issues or report them to me on discord,jacobfinn.
Package: whop-sdk-py
Whop SDK for PythonA Python SDK for interacting with the Whop API. This SDK simplifies the process of using Whop's API for tasks like license validation, membership retrieval, the rest of the api usage will be added asap.InstallationInstall the package using pip:pipinstallwhop-sdk-pyGetting StartedTo use the Whop SDK, you'll first need to obtain an API key. Follow the steps below:Go toWhop Developer Settings.Create a new API Key.Once you have the API Key, you can initialize theWhopclass:fromwhopimportWhopwhop=Whop("your_api_key_here")UsageValidate a LicenseTo validate a license, first retrieve the member ID using a license string, and then validate it:fromwhopimportWhopwhop=Whop("d7sk-uZpNVFdvWHVedhsadyisagdho3yeoiuahsdo7g")# Replace with your actual API keymemberID=whop.getMemberID("LIQUID-8BA11B-7831C9FD-ABCDEFG")# Replace with the actual licenseisUser,userData=whop.validateLicense(memberID)print(isUser)print(userData)