Saravanan666/pypi-org huggingface dataset:
Package: ip-checker
IP CheckerTool to check currently connected IP's using GreyNoise API.
It use classic Unix 'netstat' to gain list of currently connected IP's and scan them using GreyNoise API.Installationpipinstallip-checkeror you can install it from source:gitclonehttps://github.com/mickgl/ip-checker.git
python3setup.pyinstallUsageBy default IP-Checker runs in background and repeats scan until received kill signal.
To run in default mode:ipcheckerHowever there are two other modes: 'log' which also log all scanned adresses in text file and 'no-background' which preforms one scan and exit.To run in 'log' mode:ipchecker--logAnd to run in 'no-background':ipchecker--no-backgroundConfigurationAll configuration is made in 'conf.py' which is (for now) located in site-packages after installation.
You can modify it directly or just use '--cfg' argument to access it from IP-Checker:ipchecker--cfgFor info about configuration look at 'conf.py'.
Package: ipclog
ipclogSupports Python multi-process non-blocking log processing to prevent important processes from being blocked due to log processing.Especially when there are many and important processes, log messages need to be processed at the same time, and these processing processes are time-consuming and may block important processes.Must Read Before usehttps://man7.org/linux/man-pages/man7/pipe.7.htmlPipe capacity, A pipe has a limited capacity.PIPE_BUF (because of it, Configure the size ofIPClient.ATOMIC_MAXaccording to your own server conditions.
If you really don't know how much to set, you can determine it through experiments which prepared scripttests.test_logger.test_ipc_multi_big_log)How Tofromipclog.loggerimportinit_loggerfromipclog.ipc_serverimportIPCServerdefinit_log():il=init_logger(filters=lambdarecord:record.get("msg"),add_fields={"field0":0})return{"ctx":1,"logger":il}defexec_log(ll,ctx):ctx["logger"].info(ll,extra=json.loads(ll))withIPCServer("./tmp.fifo",inits=init_log,execute=exec_log,nonblock=True,cache_len=100)asipc:ll=init_logger(ipc_client=ipc)foriinrange(100):ll.info(f"ipc->{i}")
Package: ipc-mngr
Interprocess Communication (IPC) Manager to help create a Command structure for sending and receiving messages between processes.Simple Listener/Client# main.pyimportipc_mngrdefmsg_handler(sock,cmd):"""Handle received commands.

    Args:
        sock (multiprocessing.connection.Client): Client socket that received the command.
        cmd (object): Command object that was received.
    """print('Received Command:',cmd)listener=ipc_mngr.Listener(('127.0.0.1',8111),authkey='12345')listener.msg_handler=msg_handlerprint("listening ...")listener.listen()# Listen forever# send_cmd.pyimportipc_mngrwithipc_mngr.Client(('127.0.0.1',8111),authkey='12345')asclient:# Send the commandclient.send("Hello World!")Schedule ExampleSee tests/schedule_run directory for how to use this as a permanent job scheduler.Stream Audio ExampleSee tests/stream_audio directory for how to use the Streamer and StreamClient class.importipc_mngrwithipc_mngr.Streamer(('127.0.0.1',8222),authkey='12345')asstreamer:whileTrue:streamer.broadcast(1)# streamer.stream(1)importipc_mngrimporttimeSECONDS=5data=[]defsave_data(client,value):data.append(value)withipc_mngr.StreamClient(('127.0.0.1',8222),authkey='12345')asclient:start=time.time()client.stream_handler=save_data# Save data for 5 secondswhiletime.time()-start<SECONDS:time.sleep(1)print('Collected{}samples'.format(len(data)))
Package: ipconflict
ipconflictCheck if two or more network subnets are overlapping.Installpip install ipconflictQuick Startipconflict 10.0.0.0/22 10.0.1.0/24ipconflict 10.0.0.0/22 10.0.1.1-10.0.1.5ipconflict 172.16.0.0/22 172.16.1.0/24 172.16.3.0/27Print overlapping IP addressesipconflict -p 10.0.0.0/24 10.0.0.100-10.0.0.105Subnets from fileipconflict -f /path/to/subnetsSubnets from stdinecho "10.0.1.0/24 10.0.0.0/22" | ipconflict -iSubnets from everywhereecho "10.0.0.0/16" | ipconflict -i -f /path/to/subnets 192.168.0.0/24 172.25.1.17Subnet DefinitionA subnet can be specified in several ways:CIDR notation192.168.0.0/24Single IP address10.0.1.2IP range10.0.0.5-10.0.0.20This tool works both with IPv4 and IPv6.
Package: ipCorePackager
ipCorePackagerScriptable universal IP-Core generatorExport formatsIP-XACT(Vivado)Quartus (QSys) *_hw.tclWhat is IP-Core packager.IP-Core packager is a tool which generates component.xml or _hw.tcl files which are description of interface of hardware design usually written in Verilog or VHDL. Result is the package with HDL (Verilog/VHDL) files, constraints files (XDC, UCF, ...) tcl based GUI and package description file. IP-Core packages greatly simplifies integration of hardware projects, all major synthesis tools (Xilinx Vivado, Intel Quartus, ...) are supporting them directly and for rest it is better to have IP-Core because of consystency.How to use IpCorePackagerIpCorePackager is API for generating of IP-XACT and _hw.tcl files. In order to use the IpCorePackager you need two things.You need to have definitions of Interface IP-Core meta for interfaces which require some special care (require to define some parameter in IP-Core, etc.), This meta has to be subclass ofipCorePackager.intfIpMeta.IntfIpMetaYou need to define methods inipCorePackager.packager.IpCorePackagerwhich are raising the NotImplementedError. This methods are because ipCorePackager does not dependeds on reprenation of design.This library is used byhwtthereyou can find reference implementation of IpCorePackager methods for hwt style hardware description.ThehwtLiblibrary contains definitions ofIntfIpMeta descriptionsfor common interfaces.Similar projectsKactus2- IP-core packagerQgen- Quartus ip core packager for MyHDLipgenipxact_genipyxact- Python-based IP-XACT parser
Package: ip-country
An offline tool to get country by IPRequirementsPython >= 3.6IP2Location™ LITE IP-COUNTRY-REGION-CITY DatabaseInstallationDownload IP2Location database for IPv4 fromhttps://lite.ip2location.com/database/ip-country-region-cityInstall library:pip install ip_countryUsage>>> from pprint import pprint
>>> from ip_country import IPCountry
>>> ip = IPCountry('/path/to/ipdb.csv')
>>> ip_data = ip.get_ip_data('13.73.96.0')
>>> pprint(ip_data)
{'city_name': 'Melbourne',
 'country_code': 'AU',
 'country_name': 'Australia',
 'error': None,
 'ip': '13.73.96.0',
 'region_name': 'Victoria'}

>>> ip_data = ip.get_ip_data('blah.73.96.0')
>>> pprint(ip_data)
{'error': "Only decimal digits permitted in 'blah' in 'blah.73.96.0'",
 'ip': 'blah.73.96.0'}
Package: ip-country-search
Python utility for searching country of IP addressesA python utlitiy package that can be used for getting country name of IP addresses.This utility contains 2 functions:
* update_rir_files : Fetches latest data from regional internet registries
* get_country_name : Returns the country name by accepting the ip address as parameterPlease note that the import statement would take some time as it will be preparing the data from all regional registries. This will be optimized in future versions.[The source for this project is available here][https://github.com/manumathew23/ip-country-search].
Package: ipc-purepy
IPC PurePyThe package allow sent core Python objects between two likely independent
Python processes using UNIX sockets.It provides a Server class (Server), a Client function
(communicate), and aPyCoreObjecttype alias.PyCoreObject alias:It's a type alias defined as the union of the basic types of Python language
(str,int,float,bool,None) and common collections
(list[PyCoreObject]anddict[str, PyCoreObject]).The dict type key must be are str type and value are PyCoreObject.function is_pycoreobject(object: Any) -> bool:This recursive function allows to check if the object passed to it
is a valid PyCoreObject.class Server(socket_path: str):The class defines the server socket as a context handler. Through the
wait_connection() method it waits for some external connection and returns
the PyCoreObject sent to it.The connection to the client is expected to be closed with the
close_connection() method.Server class implements the reply() method that allows to send a
PyCoreObject to the client if the connection is alive.function communicate(socket_path: str, data: PyCoreObject) -> PyCoreObject:Client endpoint to communicate with the server socket, send data to
server socket and expect receive a response from it.
Package: ipcq
ipcqA simple inter-process communication (IPC) Queue built on top of the built-in librarymultiprocessing.Quick StartAPIclass ipcq.QueueManagerServer(address: Optional[str],authkey: Optional[bytes])defget_queue(ident: Union[AnyStr, int, type(None)] = None) -> queue.Queueclass ipcq.QueueManagerClient(address: Optional[str],authkey: Optional[bytes])defget_queue(ident: Union[AnyStr, int, type(None)] = None) -> queue.QueueQuick StartServerimport ipcq


with ipcq.QueueManagerServer(address=ipcq.Address.DEFAULT, authkey=ipcq.AuthKey.DEFAULT) as server:
    server.get_queue().get()Clientimport ipcq


client = ipcq.QueueManagerClient(address=ipcq.Address.DEFAULT, authkey=ipcq.AuthKey.DEFAULT)
client.get_queue().put('a message')Please checkout out theexamplesfolder for more examples.APIclass ipcq.QueueManagerServer(address: Optional[str],authkey: Optional[bytes])This class inheritsmultiprocessing.managers.BaseManager.addresscan beipcq.Address.AUTO,ipcq.Address.CWDor any other path described instr.
When it's givenipcq.Address.AUTO, a random address will be chosen.ipcq.Address.CWDmeans using a file that lives in the current working directory.authkeyis just like the password for authentication. It can beipcq.AuthKey.AUTO,ipcq.AuthKey.DEFAULT,ipcq.AuthKey.EMPTYor any other arbitrarybytes.defget_queue(ident: Union[AnyStr, int, type(None)] = None) -> queue.QueueThe method returns aqueue.Queuecorresponding withident.
The returned queue is shared between the server and the client.
So both the server and the client access to the same queue.identis the identity, it can be any string-like object,intorNone.
The default isNone.
It is used for differetiate the obtained queues.
Differentidents refer to different queues.class ipcq.QueueManagerClient(address: Optional[str],authkey: Optional[bytes])This class inheritsmultiprocessing.managers.BaseManager.addresscan beipcq.Address.CWDor any other path described instr.
When the server is set withipcq.Address.CWDand the client is running in the same CWD that the server runs, the client can be set withipcq.Address.CWDas well.
Otherwise, it should be the same with theaddressfield in the server instance.authkeyis just like the password for authentication. It has to be the same with what's set on the server .
If the server was set withipcq.AuthKey.DEFAULToripcq.AuthKey.EMPTY, the client can just be set with the same.defget_queue(ident: Union[AnyStr, int, type(None)] = None) -> queue.QueueThe method returns aqueue.Queuecorresponding withident.
The returned queue is shared between the server and the client.
So both the server and the client access to the same queue.identis the identity, it can be any string-like object,intorNone.
The default isNone.
It is used for differetiate the obtained queues.
Differentidents refer to different queues.
Package: ipcqueue
This package provides SYS V and POSIX message queues to exchange data
among processes. Both queues have similar functionality with some
differences. Queues are persistent in the kernel unless either queue is
closed/unlinked or system is shut down. Unlikemultiprocessing.Queue,
the same queue can be joined by different processes according to its
unique name/key, it’s not necessary to fork main process. Be careful if
you use signals in your application, because signal interrupts sending
or receiving message.InstallationRequires Python CFFI, C compiler and Python header files.cd ipcqueue/
python setup.py installUsage>>> from ipcqueue import posixmq
>>> q = posixmq.Queue('/foo')
>>> q.qsize()
0
>>> q.put([1, 'A'], priority=1)
>>> q.put([2, 'B'], priority=2)
>>> q.put([3, 'C'], priority=1)
>>> q.qsize()
3
>>> q.get()
[2, 'B']
>>> q.get()
[1, 'A']
>>> q.get()
[3, 'C']
>>> q.close()
>>> q.unlink()

>>> from ipcqueue import sysvmq
>>> q = sysvmq.Queue(1)
>>> q.qsize()
>>> q.put([1, 'A'], msg_type=1)
>>> q.put([2, 'B'], msg_type=2)
>>> q.put([3, 'C'], msg_type=2)
>>> q.put([4, 'D'], msg_type=1)
>>> q.qsize()
4
>>> q.get(msg_type=2)
[2, 'B']
>>> q.get()
[1, 'A']
>>> q.get()
[3, 'C']
>>> q.get()
[4, 'D']
>>> q.close()Documentationhttp://pythonhosted.org/ipcqueueLicense3-clause BSD
Package: ipcs
ipcsA library for Python for IPC.(Although it is written as IPC, it can also be used for communication with an external server.)Installation$ pip install ipcsExamplesRunipcs-serverand run following code.Client A# Client AfromipcsimportClient,Requestclient=Client("a")@client.route()asyncdefhello(request:Request,word:str):print("Hello,%s!"%word)client.run("ws://localhost/",port=8080)Client B# Client BfromipcsimportClientclient=Client("b")@client.listen()asyncdefon_ready():# Run client a's hello str to say greetings to world.awaitclient.request("a","hello","World")# or `await client.connections.a.request("hello", "World")`client.run("ws://localhost/",port=8080)LicenseThe license is MIT and details can be foundhere.DocumentationDocumentation is avaliablehere.
Package: ipc-sun-sync
ipc-sun-syncSync sunrise and sunset on Dahua IP cameras.UsageSeeconfig.yml.deffor a starter configuration.ExampleCreateconfig.ymlwith the following content.---
latitude: 34.0522
longitude: -118.2437
timezone: America/Los_Angeles

# IP camera defaults
username: admin
password: password
method: cgi
sunrise_offset: 00:30:00
sunset_offset: -01:20:00

# IP camera list
ipc:
  - ip: 192.168.1.108
  - ip: 192.168.1.109
    sunset_offset: 00:20:00
    method: rpc
  - ip: 192.168.1.110
    name: FriendlyNameForLogging
    username: OverideDefaultUser
    password: OverideDefaultPassword123
    channel: 1The following command will sync the cameras located at192.168.1.108,192.168.1.109,192.168.1.110.ipc-sun-sync -c config.ymlSunrise will be 30 minutes late and sunset will be 1 hour and 20 minutes early.192.168.1.108and192.168.1.109will use the credentialsadminandpassword.192.168.1.109will interact through rpc instead of cgi and sunset will be 20 minutes late.192.168.1.110will have it'sname,username,password, andchanneloverridden.nameis used for logging.channelis the video channel you want to apply the sun times, default is 0.The sunrise and sunset times will be calculated using thelatitudeandlongitudevariables, then it will be converted to your timezone using thetimezonevariable.Check Configurationipc-sun-sync -c config.yml --checkVerify IPC SettingsShows the sunrise time, sunset time, and switch mode currently on the IP cameras.ipc-sun-sync -c config.yml --verifyShow Timezonesipc-sun-sync -TShow Versionipc-sun-sync -VChangelogCHANGELOG.mdTroubleshootingIf the program says it is successful but the sunrise and sunset times do not change,try disablingSmart Codecif it is enabled.use rpc.To DoAdd verbose logging.
Package: ipctk
IPC ToolkitDescriptionIPC Toolkit is a set of reusable functions to integrate Incremental Potential Contact (IPC) into a simulation.FeaturesIPC barrier function and its derivatives and adaptive barrier stiffness algorithmBroad-phase and narrow-phase continuous collision detection (CCD)Distance computation and derivatives between edges in 2D and triangles in 3DDistance barrier potential and its derivativesSmooth and lagged dissipative friction potential and its derivativesLimitationsThis is not a full simulation library. As such it does not include any physics or solvers. For a full simulation implementation, we recommendPolyFEM(a finite element library) orRigid IPC(rigid-body dynamics) both of which utilize the IPC Toolkit.InstallationTo install the latest release, you can usepip:pip install ipctkIf you wish to install the current development code, you can compile the library from scratch. Either clone therepomanually or usegit+withpip:pip install git+https://github.com/ipc-sim/ipc-toolkitHelp/DocumentationA tutorial on how to use the toolkit can be foundhere.A function reference can be foundhere.ContributingThis project is open to contributors! Contributions can come in the form of feature requests, bug fixes, documentation, tutorials, and the like. We highly recommend filing an Issue first before submitting a Pull Request.Simply fork this repository and make a Pull Request! We would appreciate:Implementation of new featuresBug ReportsDocumentationTestingCitationIf you use the IPC Toolkit in your project, please consider citing our work:@software{ipc_toolkit,author={Zachary Ferguson and others},title={{IPC Toolkit}},url={https://github.com/ipc-sim/ipc-toolkit},year={2020},}Additionally, you can cite the original IPC paper:@article{Li2020IPC,author={Minchen Li and Zachary Ferguson and Teseo Schneider and Timothy Langlois andDenis Zorin and Daniele Panozzo and Chenfanfu Jiang and Danny M. Kaufman},title={Incremental Potential Contact: Intersection- and Inversion-free Large Deformation Dynamics},journal={ACM Trans. Graph. (SIGGRAPH)},year={2020},volume={39},number={4},articleno={49}}LicenseMIT License © 2020, the IPC-Sim organization (SeeLICENSE.txtfor details)
Package: ipdasite.policy
This is the “policy” product for the Plone-based site of the International
Planetary Data Alliance (IPDA).  Its job is to orchestrate the dependencies
and configure them in order to transform an ordinaryPlonesite into the IPDA
site.It was developed by the Planetary Data System (PDS).InstallationUseBuildoutwith the plone.recipe.zope2instance recipe.Addipdasite.policyto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    ipdasite.policyRe-run buildout, e.g. with:$ ./bin/buildoutThat’s it.ChangelogFor more information on issues referenced below (“IPDA-#”), see the issue
tracker athttps://oodt.jpl.nasa.gov/jira/browse/IPDA.2.1.6 — Dropped the EventIPDA-37 - Bad link on the 7th IPDA meeting page2.1.5 — Hmm, UpgradesCompatible with Plone 4-latest (4.2.1 as of this writing)2.1.4 — ResistancewasFutileRemoved dependency on borg.project.2.1.3 — SplashyIPDA-22 - New splash image2.1.2 — Portlet MadnessThis release addresses the following:IPDA-14 - Drop navigation portletIPDA-15 - The News Portlet is configured to show the last five news items.
We can reconfigure it to show just 2 or 3.IPDA-16 - Upcoming Events under Upcoming Events in the left hand panel.2.1.1 — Buffing Out The Rough EdgesThis release addresses the following:IPDA-3 - Broken icons on home pageIPDA-5 - CSS attribution missingIPAD-4 - IPDA TEG “borg.project” object remains after upgradeIPDA-8 - Community workflow is not defaultIPDA-9 - Create customized tabular views for every folder2.1.0 — RehostingThis release preparesipdasite.policyfor its new look, feel, and home at
JPL.2.0.1 — Service RegistryThis release adds the IPDA Service Registryipdasite.services.2.0.0 — Plone 4This release of the IPDA Site Policy brings about Plone 4 compatibility.Copyright & LicenseCopyright 2008-2011 by the California Institute of Technology.  ALL RIGHTS
RESERVED.The Software is owned by Caltech/JPL and is protected by United States
copyright laws and applicable international treaties and/or conventions.  The
United States Government may have prior rights to use some or all of the
Software as determined under applicable contracts and license agreements with
Caltech/JPL.This software was developed at the Jet Propulsion Laboratory, an operating
division of the California Institute of Technology and is not available for
use by any person, organization, or other entity without prior, specific
written permission.
Package: ipdasite.projectmgmt
This package provides project management tools for the International Planetary
Data Alliance (IPDA).  These tools include:IPDA Events, such as conferences or meetingsIPDA Documents, web pages with IPDA document identifiersIPDA Files, uploaded files (like PDFs or Word documents) also with IPDA
documents identifiersIPDA Projects, collaborative containers for documents and files pursued by
the IPDA.Project Folders, containing IPDA ProjectsSteering Committee, a special display of IPDA members for are part of the
IPDA Steering CommitteeAlthough intended for the web site of the IPDA, this package may be installed
on anyPlone4 site.  It was developed by the Planetary Data System (PDS).InstallationUseBuildoutwith the plone.recipe.zope2instance recipe.Addipdasite.projectmgmtto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    ipdasite.projectmgmtTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
recipe = plone.recipe.zope2instance
...
zcml =
    ipdasite.projectmgmtRe-run buildout, e.g. with:$ ./bin/buildoutYou can skip the ZCML slug if you are going to explicitly include the package
from another package’s configure.zcml file.Changelog2.0.3 — Hm, UpgradesThis release makes the package compatible with Plone 4.3.2.0.2 — UneventfulIPDA-16 - Upcoming Events under Upcoming Events in the left hand panel2.0.1 - The Experts are Technical - 2011-1-25Dan.Crichton@jpl.nasa.govwants the members of the Technical Experts Group to
appear under the “Members” tab.  Well, the “Members” tab was already a
misnomer, as it was an instance of a “Steering Committee Display” object whose
sole purpose was to show those registered users who were in the group “SC”.
Well, now that object’s view also has a section for “TEG” members.2.0.0 - Plone 4This release of the IPDA Project Management brings about Plone 4
compatibility.Copyright & LicenseCopyright 2008-2011 by the California Institute of Technology.  ALL RIGHTS
RESERVED.The Software is owned by Caltech/JPL and is protected by United States
copyright laws and applicable international treaties and/or conventions.  The
United States Government may have prior rights to use some or all of the
Software as determined under applicable contracts and license agreements with
Caltech/JPL.This software was developed at the Jet Propulsion Laboratory, an operating
division of the California Institute of Technology and is not available for
use by any person, organization, or other entity without prior, specific
written permission.
Package: ipdasite.views
This is aPloneadd-on that provides customized views requested by Emily Law
for the International Planetary Data Alliance (IPDA) website.  Ms Law wants a
uniform tabular view on all folders, therefore this package provides that
custom view.InstallationUseBuildoutwith the plone.recipe.zope2instance recipe.Addipdasite.viewsto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    ipdasite.viewsRe-run buildout, e.g. with:% ./bin/buildoutChangelogFor more information on issues referenced below (“IPDA-#”), see the issue
tracker athttps://oodt.jpl.nasa.gov/jira/browse/IPDA.1.0.2 — Dexterity RelationsPlone 4.3 removes a lot of the automatic add-ons so we have to be explicit
about what to include.  We explicitly need plone.app.dexterity with itsrelationsextra.1.0.1 — Hmm, upgradesMade compatible with Plone 4-latest.1.0.0 — Initial ReleaseThis release addresses the following issue:IPDA-9 - Create customized tabular views for every folder0.0.0 — Happy BirthdayThis is the first release of ipdasite.views.CopyrightCopyright 2012 by the California Institute of Technology.  ALL RIGHTS
RESERVED.The Software is owned by Caltech/JPL and is protected by United States
copyright laws and applicable international treaties and/or conventions.  The
United States Government may have prior rights to use some or all of the
Software as determined under applicable contracts and license agreements with
Caltech/JPL.This software was developed at the Jet Propulsion Laboratory, an operating
division of the California Institute of Technology and is not available for
use by any person, organization, or other entity without prior, specific
written permission.