Saravanan666/pypi-org huggingface dataset:
Package: cerial
Fast, simple, and more pythonic binary serializer library.Cerial combines Python 3 features, Cython, and memory views to create
a fast and easy library for packing and unpacking binary structures.Removes a lot of the boilerplate that sometimes ends up surrounding
struct when used for serialization.ExampleHere’s a quick example of how to use cerial to handle a UDP packet.
First we define the structure:>>>UDP=Struct('UDP',...('sport','uint16'),...('dport','uint16'),...('len','uint16'),...('csum','uint16'),...endianness='!'...)Unlike the builtin struct library, cerial needs the fields to be bound
to a name. This is because we expose the binary structure with
dictionary interface instead of as a tuple of values.Now that we have a structure defined, we can use to parse data:>>>data=bytearray(b'\x08R\x02\x02\x00w\xa9k')>>>hdr=UDP.parse(data)>>>hdr<UDPb'\x08R\x02\x02\x00w\xa9k'>We can now inspect the binary structure:>>>hdr['csum']43371>>>dict(hdr){'csum':43371,'len':119,'sport':2130,'dport':514}>>>bytes(hdr)b'\x08R\x02\x02\x00w\xa9k'And we can also update individual fields, which will directly write to
the underlying memory view, no rendering step needed.>>>hdr['csum']=0xffff>>>databytearray(b'\x08R\x02\x02\x00w\xff\xff')>>>bytes(hdr)b'\x08R\x02\x02\x00w\xff\xff'TODOFeature parity with the various primitives the struct library
supportsFirst class support for bit fieldsImprove performanceSupport readonly memoryviews (e.g. support bytes). An upstream
Cython issue.PerformanceCurrently slightly slower than the struct module, but as far as I can
tell, significantly faster than other similar libraries like pypacker
or scrapy at parsing packets.
Package: cerise-manager
Cerise ManagerCerise Manager is a Python library for managing containerised Cerise instances.
Using Cerise Manager, you can create, destroy, start and stop (specialised)
Cerise instances running on your local machine. Cerise Manager is an extension
of Cerise Client, so you can also submit jobs and manage those on the created
services.InstallationCerise Manager is on PyPI, so you can just` pip install cerise_manager `possibly in a virtualenv or Conda environment, if you so desire. Cerise Manager
supports Python 3.4 and up.DevelopmentTo install cerise_manager from GitHub, do:git clone https://github.com/MD-Studio/cerise_manager.git
cd cerise_manager
pip install .Run tests (including coverage) with:python setup.py testIf you want to contribute to the development of Cerise Manager,
have a look at thecontribution guidelines.DocumentationDocumentation should be put in thedocsfolder. The contents have been generated usingsphinx-quickstart(Sphinx version 1.6.5).We recommend writing the documentation using Restructured Text (reST) and Google style docstrings.Restructured Text (reST) and Sphinx CheatSheetGoogle style docstring examples.The documentation is set up with the Read the Docs Sphinx Theme.Check out theconfiguration options.To generate html documentation runpython setup.py build_sphinxThis is configured insetup.cfgAlternatively, runmake htmlin thedocsfolder.LegalCopyright (c) 2019, Netherlands eScience Center and VU University AmsterdamLicensed under the Apache License, Version 2.0 (the “License”);
you may not use this file except in compliance with the License.
You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an “AS IS” BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Package: cerium
CeriumCerium is an umbrella project encapsulating a variety of tools and
libraries enabling android automation.Cerium's source code is made available under theApache 2.0 license.Welcome toRead the DocsforCerium!IntroductionCerium: A Toy for Android AutomationCeriumis an Android automation framework for Python, safe for human consumption.Behold, the power of Cerium:>>>fromceriumimportAndroidDriver>>>driver=AndroidDriver()>>>driver.unlock(1997)# unlock your device by password>>>driver.auto_connect()# connect to your device via TCP/IP automaticallyNowyoucanunplugtheUSBcable,andcontrolyourdeviceviaWLAN.>>>driver.view_packgets_list(keyword='tencent')['com.tencent.mm','com.tencent.android.qqdownloader','com.tencent.tim']>>>driver.make_a_call(18268237856)# call meCeriumallows you to sendorganic, grass-fedcommands, without the the need for manual labor.Android Debug Bridge (adb)is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. This project is based on it.Supported Python VersionsPython 3.6+Supported PlatformsWindows 10 (Other platforms have not been tested and are not intended to be supported for the time being officially)InstallationIf you havepipon your system, you can simply install or upgrade cerium:pip install -U ceriumAlternately, you can download the source distribution fromPyPI, unarchive it, and run:python setup.py installOr bygithub.com:git clone git@github.com:ffujiawei/cerium.git
cd cerium
python setup.py installNote: You may want to consider usingvirtualenvto create isolated Python environments.Android Debug BridgeCerium requires Android Debug Bridge Tool to with the chosen android device. And Cerium containsAndroid Debug Bridgeby default. You don't need to set the environment variable by yourself.QuickstartList connected android devices or simulator.Show the version of Android Debug Bridge.fromceriumimportAndroidDriverdriver=AndroidDriver()print(driver.devices())print(driver.devices_l())# show devices and modelsprint(driver.version())Copy local files/directories to device.Copy files/directories from device.Taking a screenshot of a device display, then copy it to your computer.fromceriumimportAndroidDriverdriver=AndroidDriver()driver.push(local='README.md',remote='/sdcard/README.md')driver.pull(remote='/sdcard/README.md',local='README.md')driver.pull_screencap(local='screencap.png')Simulate finger click.Simulate finger slide.Input text.fromceriumimportAndroidDriverdriver=AndroidDriver()driver.click(100,100)driver.swipe(100,200,100,100,duration=100)driver.send_keys("I'm White Turing.")DemonstrationA wireless automation applicationA command line wireless control tool for AndroidAuthorCerium is written and maintained byWhite Turing(fujiawei@stu.hznu.edu.cn).
Package: cerl
CERL libraryPython bindings for theConsortium of European Research Library's API.See /docs/docs.ipynb for a Jupyter notebook with additional documentationBasic examplefromcerlimportample_query,ample_record,ids_from_result,by_dot,the# Connect to any AMPLE instancect='data.cerl.org/thesaurus'# Run a search queryresult=ample_query(ct,'Purslowe, Elizabeth')foridxinids_from_result(result):# Download the record as a Python dictrecord=ample_record(ct,idx)# Access the record by dot notationcid=the(by_dot(record,'_id'))assertcid==idxInstallationpip3installcerlFeaturesAccess to any AMPLE instance by specifying thehoststring (e.g. "data.cerl.org/thesaurus")Some databases hardcoded as syntactic sugar:CTISTCHOLDINSTMEIUse the standard search syntax withample_queryThe same databases hardcoded as syntactic sugar:ct_queryetc.Download records as Pythondictobjects withample_recordAgain,ct_recordetc.Download records in other formats withample_record_exportAgain,ct_record_exportetc.Export formats supported (but not all for each database):rdf/ttlrdf/xmlrdf/jsonldjsonyamlunimarcAccess to record fields using the dot notation from search syntax viaby_dot(NOTE: always returns alistof results)If you know there is only one object/value being returned, wrap intheSyntactic sugar around some fields:Resolve CT record types withct_record_typeGet the CID (CERL ID) withcidAdd a timestamp to a record after modifying it withadd_timestamp
Package: cerlet
# CerLet CertMonger Let’s Encrypt HelperWORK IN PROGRESS, INCOMPLETE!Helper integration to allow certmonger to communicate with the Let’s Encrypt CAThis package integrates Certmonger (and by extension FreeIPA/Sattellite) with
the Let’s Encrypt community Certificate Authority.This allows hosts in FreeIPA to automatically get publically trusted certificates
for all purposes.Due to using DNS based authentication certificates ban be issued for private
servers as well as public ones without any service interruptions. This also
allows certificates to include an alias per principal or any number of host/DNS
names.This package includes python libraries which will be installed in the default
site-packages directory of your python distribution (or virtualenv) and an entry
point script that will be installed under /usr/libexec/certmonger.
Package: cernopendata-client
Aboutcernopendata-clientis a command-like tool to facilitate downloading files
from theCERN Open Data portal. The tool enables
to query datasets hosted on the CERN Open Data portal and to download and
verify the individual data set files.Installation$pipinstallcernopendata-clientUsageThe detailed information on how to install and usecernopendata-clientcan be
found incernopendata-client.readthedocs.io.Useful linksCERN Open Data portalCERN Open Data user forumChangesVersion 0.3.0 (2022-03-16)Adds support for Python 3.10.Improvesdownload-filescommand to resume interrupted downloads when
using HTTP downloads withpycurlengine.Improves XRootD downloader by using vanilla XRootD package. Changesxrootdpyfstoxrootddownload engine.Improvesdownload-filescommand with a new option--download-engineto selectpycurlorrequestsengines when downloading files over
HTTP.Fixes minor issues with file index unwinding and output directory handling.Version 0.2.0 (2020-11-19)Adds newlist-directorycommand to list content of EOS directories
holding open data files.Adds support for Python 3.9.Improvesdownload-filescommand to allow using XRootD protocol.Improvesdownload-filescommand to allow using HTTPS protocol.Improvesdownload-filescommand to optionally verify file integrity as
soon as files are being downloaded.Improvesget-file-locationscommand to optionally output file sizes and
checksums.Improves output format colouring to better indicate notes and errors.Fixes minor issues and improves code coverage.Version 0.1.0 (2020-09-24)Enrichesdownload-filescommand to optionally download only files
matching certain name, regexp, or range count.Adds newverify-filescommand to verify number, size, and checksum of
downloaded files.Improvesget-metadatacommand with respect to outputting only
certain desired metadata field values.Enriches user documentation.Version 0.0.1 (2020-09-09)Initial public release.
Package: cernservicexml
AboutCERNServiceXML is a small library to generate a CERN XSLS Service XML
and sending it to a remove service.InstallationCERNServiceXML is on PyPI so all you need is:pip install cernservicexmlDocumentationDocumentation is readable athttp://cernservicexml.readthedocs.orgor can be
build using Sphinx:pip install Sphinx
python setup.py build_sphinxTestingRunning the test suite is as simple as:python setup.py testor, to also show code coverage:./run-tests.sh
Package: cerridwen
Cerridwen provides geocentric planetary data that is suitable for
a broad spectrum of astronomical and astrological applications,
with a focus on our solar system. Among its data you will find,
for example, the time of the next sunrise or that of the last full
moon, or simply the current tropical position of the sun.The motivation for this package is to have a reliable open-source library
and API that provides comprehensive data on various planetary bodies and
factors at a certain point in time.Cerridwen comes with a simple command-line utility and a JSON server,
but is also designed to serve as a basis for your own application.FeaturesGet comprehensive data on the sun and moon at almost any point in timeRely on the high precision of the NASA JPL ephemerisMake use of a powerful numpy-based algorithm for planetary event
finding, (e.g. full moon, squares of planets etc.)Work with Julian and ISO datesUse Cerridwen’s JSON API to ensure loose couplingExtend Cerridwen with ease to suit your own needsDocumentationCerridwen’s full documentation can be found athttp://cerridwen.readthedocs.org/StabilityCerridwen includes a basic test suite for its calculations and API.At this time the API is reasonably stable but may change without
warning. Please let me know when you need better API stability for
your project.Also, you can check out the status of the current development version
at Travis CI:
Package: certbot
Certbot is part of EFF’s effort to encrypt the entire Internet. Secure communication over the Web relies on HTTPS, which requires the use of a digital certificate that lets browsers verify the identity of web servers (e.g., is that really google.com?). Web servers obtain their certificates from trusted third parties called certificate authorities (CAs). Certbot is an easy-to-use client that fetches a certificate from Let’s Encrypt—an open certificate authority launched by the EFF, Mozilla, and others—and deploys it to a web server.Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting and maintaining a certificate is. Certbot and Let’s Encrypt can automate away the pain and let you turn on and manage HTTPS with simple commands. Using Certbot and Let’s Encrypt is free.Getting StartedThe best way to get started is to use ourinteractive guide. It generates instructions based on your configuration settings. In most cases, you’ll needroot or administrator accessto your web server to run Certbot.Certbot is meant to be run directly on your web server on the command line, not on your personal computer. If you’re using a hosted service and don’t have direct access to your web server, you might not be able to use Certbot. Check with your hosting provider for documentation about uploading certificates or using certificates issued by Let’s Encrypt.ContributingIf you’d like to contribute to this project please readDeveloper Guide.This project is governed byEFF’s Public Projects Code of Conduct.LinksDocumentation:https://certbot.eff.org/docsSoftware project:https://github.com/certbot/certbotChangelog:https://github.com/certbot/certbot/blob/master/certbot/CHANGELOG.mdFor Contributors:https://certbot.eff.org/docs/contributing.htmlFor Users:https://certbot.eff.org/docs/using.htmlMain Website:https://certbot.eff.orgLet’s Encrypt Website:https://letsencrypt.orgCommunity:https://community.letsencrypt.orgACME spec:RFC 8555ACME working area in github (archived):https://github.com/ietf-wg-acme/acmeCurrent FeaturesSupports multiple web servers:Apache 2.4+nginx/0.8.48+webroot (adds files to webroot directories in order to prove control of
domains and obtain certificates)standalone (runs its own simple webserver to prove you control a domain)other server software viathird party pluginsThe private key is generated locally on your system.Can talk to the Let’s Encrypt CA or optionally to other ACME
compliant services.Can get domain-validated (DV) certificates.Can revoke certificates.Supports ECDSA (default) and RSA certificate private keys.Can optionally install a http -> https redirect, so your site effectively
runs https only.Fully automated.Configuration changes are logged and can be reverted.
Package: certbot-access-server
OpenVPN Access Server Installer plugin for CertbotThe plugin automates installation of plugin, generated by certbot, to the
OpenVPN Access Server system.Named Arguments--as-installer-socketPath to the socket OpenVPN Access Server
is listening at
(Default:
/usr/local/openvpn_as/etc/sock/sagent.localroot)--as-installer-path-onlySet path to certificate to
OpenVPN Access Server instead of
certificate itself
(Default: false)Installationcertbot-access-serverrequires Python 3.7+ to run.pip3installcertbot-access-serverExamplesTo acquire and install a single certificate for example.com, using certbot’s
standalone webserver:certbot\--standalone--installeras_installer\-dexample.comNotesThe plugin requires running instance of OpenVPN Access Server to work
Package: certbot-acme-dns
certbot-acme-dnsACME DNS Authenticator plugin for Certbot.This plugin automates the process of completing adns-01challenge with the
help of anacme-dnsproxy server.WarningYour ACME CA must properly implementRFC 8657, namely theaccounturiissuance parameter. This plugin contains a list of compliant ACME CAs
and will abort if the chosen CA is not on that list.The RFC does not require CAs to fail validation when they don't understand an
issuance parameter, meaning that unless a particular ACME CA explicitly
documents supporting and honoring theaccounturiissuance parameter, it
will besilently ignored. Typos in the parameter names are allowed to be
ignored, too (eg.accounturlwill render your deployment insecure even when
the CA fully implements the RFC). See theRFC complaint forum postfor
discussion.You can force this plugin to proceed anyway using the--acme-dns-is-trusted=yesoption. However, this isINSECUREandDANGEROUS, unless you self-host theacme-dnsproxy serverandfully
trust it. The proxy server will be able to issue certificates for the
"delegated" domain without your (certbot's) consent.Installationpip install certbot-acme-dnsUsageTo start using the plugin, pass the--authenticator=acme-dns(or just-a acme-dnsfor short) option to certbot's command line.Custom ACME DNS proxy server URL can be specified using the--acme-dns-url https://acme-dns.example.comoption, default ishttps://auth.acme-dns.io.DevelopmentRun teststoxAuto-fix code formattingtox -e reformatRun Certbot with the certbot-acme-dns plugintox -e run -- certonly -a acme-dns -d example.comCertbot logs & config (accounts, hooks, certificates, etc.) are stored under./.certbot/.Buildsdisttox -e buildwheeltox -e build -- --wheelGenerate documentationtox -e docs
Package: certbot-aliyun-cdn
Use the certbot client to install a certificate to a aliyun cdn serverPrepare an API TokenFetch access-key id/secret pair onhttps://ram.console.aliyun.com/#/overviewInstall certbot and pluginpipinstallcertbot-aliyun-cdnCreate a credentials filecertbot_alicdn:aliyun_cdn_access_key_id = "ALIYUN-ACCESS-KEY-ID"certbot_alicdn:aliyun_cdn_access_key_secret = "ALIYUN-ACCESS-KEY-SECRET"Install a certificatecertbotrun-aSOME-AUTHENTICATOR-PLUGIN\--reinstall--redirect\-icertbot-aliyun-cdn:aliyun-cdn\[--certbot-dns-dnspod:dns-dnspod-credentialsPATH-TO-CREDENTIAL-FILE]-dREPLACE-WITH-YOUR-DOMAIN
Package: certbot-anx
ANX DNS Authenticator for CertbotThis allows automatic completion ofCertbot'sDNS01 challange for domains managed onANX DNSImportant informationPLEASE NOTE THAT ONE OF THE DEPENDENCIES TO THE LIBRARY INCLUDED A BAD INSTALL_REQUIRES. THIS WAS FIXED IN 0.1.6.Installing$ pip install certbot-anxUsageThe plugin requires a API key that is created here:http://dyn.anx.se/users/users.jsf?i=2To use the authenticator you need to provide some required options:--certbot-anx:credentials(required)ANX API credentials INI file. (default: None)The credentials file must have the folling format:certbot_anx:api_key = codegoeshereFor safety reasons the file must not be world readable. You can solve this by
running:$ chmod 600 credentials.iniThen you can runcertbotusing:$ sudo certbot certonly \
        --authenticator certbot-anx:auth \
        --certbot-anx:auth-credentials credentials.ini \
        -d domain.comIf you want to obtain a wildcard certificate you can use the--server https://acme-v02.api.letsencrypt.org/directoryflag and the domain-d *.domain.com
Package: certbot-cwebroot
# certbot-cwebrootCertbot plugin for clustered web servers## Installation* Install [certbot](https://certbot.eff.org/)* Switch to the certbot virtualenv :```. ~/.local/share/letsencrypt/bin/activate```* Install `certbot-cwebroot` :```pip install certbot-cwebroot```## UsageThis requires that you set up your webservers (all the servers that may bequeried by the ACME server for the challenge, that is) for the webroot method,as described [here](https://certbot.eff.org/docs/using.html#webroot).* Get yourself an SSH key pair and deploy it on your remote hosts under thesame identity you will be using to run `certbot`.* To use the local host as well as remote hosts `host2` and `host3`, run `certbot` like this :```/path/to/certbot certonly --authenticator certbot-cwebroot:cwebroot -d www.example.com --certbot-cwebroot:cwebroot-path /var/www/html/letsencrypt/ --certbot-cwebroot:cwebroot-host host2 --certbot-cwebroot:cwebroot-host host3If you don't want the challenges to be hosted locally, you can use`--certbot-cwebroot:cwebroot-nolocal`.* The certificate should be deployed in the usual directory (`/etc/letsencrypt`probably) on your localhost. As this follows the use cases for the webrootplugin (make no assumption on where the certificates should go), it is yourjob to deploy the obtained certificate to your target webservers.## How it worksThe SSH connection are made with [spur](https://pypi.python.org/pypi/spur),which is a very convenient wrapper around [Paramiko](http://www.paramiko.org/).Spur aims to run commands locally and remotely with the same interface, soevery file system operation that whas done in the `webroot` plugin with pythonfunctions is now run with shell commands an binaries, namely :* `chown`* `mkdir`* `rm`* `rmdir`* `sh`* `stat`I have tested this on an Ubuntu 14.04, and nowhere else.
Package: certbot-django4
This is a fork of the combined plugin for the certbot ACME client and also a Django-app for proving ACME challenges.This updated version aims to provide support for django 4 and onwards as well.When creating the “certbot” user that adds the ACME challenges on the server,
note that you must explicitly add the ACMEChallenge permissions in the django admin.
The user “certbot” also needs to be staff.
Just having him as an admin is not enough.Original package Documentation:https://certbot-django.readthedocs.io