Saravanan666/pypi-org huggingface dataset:
Package: pgpsubmit
pgpsubmit is a simpleWSGIapplication that can be used for collectingOpenPGPpublic keys on a keyring e.g. for a keysigning party.Features include:submission deadline and “time remaining” displaykeyring and key list export (with MD5 and SHA-1 hashes)configured entirely through environmentDependenciesGnuPGA WSGI capable web server (e.g.Apachewithmod_wsgi).ConfigurationThree WSGIenvironvariables must be set:PGPSUBMITEXECUTABLEName or full path of the GnuPG executable.  If the value does not
begin with"/", an executable will be looked for onPATHby the normal mechanism.  If using Apache httpd and encounteringOSError, try specifying the full path to the GnuPG executable.GNUPGHOMEThe GnuPG home directory.  Must be writable by the user running the
application.  Multiple pgpsubmit instances could be run in parallel,
each with a differentGNUPGHOME.PGPSUBMITSOURCEURLURL at which may be found the corresponding source of pgpsubmit,
pursuant to section 15 of the AGPL.  If you run a modified version of
pgpsubmit, the source code for that modified version must be available
at this URL.There are some other configuration variables for controlling
submission deadlines:PGPSUBMITUNTILSpecify a deadline for submission.  After this time, submission will
be disabled, and a message to effect of same will appear.  While the
deadline looms, time remaining will be displayed.  The format is'Y.M.D[.H[.M[.S]]]'.PGPSUBMITDOWNLOADEARLYIf a deadline is set, links to download the keyring and key list are
not shown until the submission deadline is reached.  Settings this
environment variable (to any value) causes these links to be shown
regardless of whether or not the deadline has passed.A configuration for Apache with mod_wsgi might be:<Directory /usr/home/joe/pgpsubmit>
    Order allow,deny
    Allow from all
</Directory>

<VirtualHost *:80>
    ServerAdmin joe@example.com
    ServerName pgpsubmit.example.com
    DocumentRoot "/usr/home/joe/pgpsubmit"

    WSGIScriptAlias / /usr/home/joe/pgpsubmit/scripts/pgpsubmit.wsgi
    SetEnv PGPSUBMITEXECUTABLE /usr/local/bin/gpg
    SetEnv GNUPGHOME /usr/home/joe/.pgpsubmit
    SetEnv PGPSUBMITSOURCEURL https://github.com/frasertweedale/pgpsubmit
    SetEnv PGPSUBMITUNTIL 2011.12.31.18.30
</VirtualHost>Licensepgpsubmit is free software: you can redistribute it and/or modify
it under the terms of theGNU Affero General Public Licenseas published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.ContributingThe pgpsubmit source code is available fromhttps://github.com/frasertweedale/pgpsubmit.Bug reports, patches, feature requests, code review and
documentation are welcomed.To submit a patch, please usegitsend-emailor generate a pull
request.  Write awell formed commit message.  If your patch is
nontrivial, update the copyright notice at the top of each changed
file.
Package: pgpu
Pydsigner's Generic Python Utilities (PGPU) -- a collection of handy modulesand packages for Python.__init__       --   version informationcompatibility  --   module to make it easier to write modules compatible withboth 2.x and 3.xencoding       --   unified interface to many codecs and hashersfile_utils     --   file utility moduleiter_utils     --   generic iterable utilitiesmath_utils     --   utilities to work with bases plus some trig utilitiesstring_utils   --   various string utilitiestime_widgets   --   tkinter time widgetstk_utils       --   tkinter widgets and helper functionswrappers       --   utility value wrappers for places requiring functionstkinter2x      --   2.x and 3.x compatibility layer for tkinter
Package: pgp-utils
pgp-utilsThis is a very simple command utility that just wraps up some common operations with pgp keys/a yubikey.For example, you can sign, encrypt, decrypt, switch yubikey (and more) with short and simple commands.ConfigurationThe utility expects a small config file located at$PGP_UTILS_HOME/config.json.$PGP_UTILS_HOMEdefaults to~/.config/pgp-utils.
The format of the file is:{ "key_id": <YOUR_KEY_ID> }Usagepgp-utils --help: Display help, available commands etc.pgp-utils switch: Switch yubikey to the one currently inserted into a USB port on your device.pgp-utils encrypt FILE ...RECIPIENTS: Encrypts a message. If no recipients are specified, ppg-utils uses the key specified in your config file.pgp-utils decrypt FILE: Decrypts a message.ppg-utils sign FILE: Signs a file.ppg-utils verify FILE: Verifies the signed file.
Package: pg_pybench
Introduction :This tool is a cross platform pgbench utility for benchmarking PostgreSQl databases. It’s still under active development
so please leave a note for a feature request or a bug report.
(Use the email address below to leave a note !)Requirements:postgresql v >= 8.4postgresql-contribpython version >= 2.7python-devEnsure the user executing this script(s) has read/write access in the execution directoryInstallation :sudo pip install pg_pybenchContact :You can send you bug report or feature request to :rugging24@gmail.comCredits :Greg Smith (https://github.com/gregs1104/pgbench-tools) wrote the orginal version in shell scripts
Package: pgqmini
pgqminipgqmini is a lightweight, easy-to-use Python library for managing PostgreSQL message queues. It provides a simple interface for adding and retrieving messages from a PostgreSQL-based queue, as well as handling timeouts and managing message processing.Table of ContentsInstallationUsageContributingLicenseContactInstallationTo install pgqmini, you can use pip:pip install pgqminiYou also need to have a PostgreSQL server up and running. The library uses the psycopg2 package to connect to the PostgreSQL server.UsageHere is a basic example of how to use pgqmini:PublisherfrompgqminiimportPGQpgq=PGQ(qname="message_queue",dbname="pgq",host="127.0.0.1",user="username",password="password",port=5432,)pgq.connect()pgq.pub('{"key1": "value1", "key2": "value2"}')pgq.disconnect()SubscriberfrompgqminiimportPGQpgq=PGQ(qname="message_queue",dbname="pgq",host="127.0.0.1",user="username",password="password",port=5432,)pgq.connect()defprocess_message(payload:str):print(payload)whileTrue:pgq.sub(process_message)In this code, we first create aPGQobject with the necessary database connection parameters. We then connect to the database and enter a loop where we process messages from the queue.For a more detailed usage guide, please check out theUsage Guidein our wiki.Licensepgqmini is released under the MIT License. See theLICENSEfile for more details.ContactIf you have any questions, issues, or suggestions, please open an issue in this repository, or contact the maintainer atjangsc0000@gmail.com.
Package: pgr
dev/pgr-project目录是用于开发cookiecutter-pygitrepo本身所用的一个 Dummy 项目. 用于模拟用户使用cookiecutter-pygitrepo生成的 Python 项目文件模板, 并且用各种bin脚本,make命令的行为. 当这些命令在my_pkg-project上工作良好后, 我们再将其通用化模板化.
Package: pgraph
The pgraph provides the graph of Python dependencies,
powered bypy-deps,Linkdraw,Celery,pylibmc, andPyramid.StatusDemoDemo siteHistory1.0.3 (2020-09-19)Supports wheel.Removes deprecated pytest options.Updates py-deps dependency.1.0.2 (2020-05-27)Updates JS libraries.Updates copyright.1.0.1 (2020-05-27)Fixes runner1.0.0 (2020-05-17)Changes to use py-deps 1.0.0.Updates dependencies.Support Python version 3.8 only.0.5.1 (2016-04-09)Fixes view template layout.Removes backward compatibilities under IE 9.Updates JavaScript libraries.Updates locally instead of pyvenv.Applies pytest-remove-stale-bytecode.Applies pytest-pylint.Ignores redefined-variable-type, wrong-import-order.Applies Python 3.5 on travis-ci.Fixes pep257 D211 violations.0.5.0 (2015-10-09)Supports Python 3.5.Adds showing version of running environments.Adjust svg_width for PC web brawser.Fixes unit test graph_not_found.0.4.8 (2015-08-19)Changes custom 404 not found pages.Closes #4, #5 error handlings 503 errors.Fixes INTERNALERROR occurs when run the tox.Changes mackerel-agent-plugin script for proxy.0.4.7 (2015-08-15)Changes setting SVG size from window InnerWidth, InnerHeight.Changes Sphinx theme to sphinx_rtd_theme.Adds mackerel metric plugin.0.4.6 (2015-07-27)Uses static_path instead of static_url.Changes example pathname.0.4.5 (2015-07-22)Adds latest_version method, display latest version package.Applies override node link with link_prefix.0.4.4 (2015-07-19)Adds invalid metadata handler.0.4.3 (2015-07-16)Change the color of the nodes to give gradation by the dependency depth (py-deps>=0.5.2)0.4.2 (2015-07-12)Changes pgraph.tasks.search (py-deps>=0.5.1).FixesNoneredundant second argument ofdict.get().Fixes old-style string formatting.0.4.1 (2015-07-03)Adds unit tests for backend_config, config modules.Changes example to redirect to the graph of latest version of pgraph.Fixes responsive navbar, search form.Chagnes Demo site URL.0.4.0 (2015-06-29)Revokes when tasks.gen_depenency failed.Fixes extras_requires for Heroku.Changes Celery backend for Heroku to PostgreSQL in default.Changes install requires pyramid_celery to celery.0.3.1 (2015-06-24)Applies GPLv3 and adds LICENSE file.0.3.0 (2015-06-24)Supports cache backend using memcached.Adds side bar into layout.Changes for Heroku.Updates setup configuration.Applies New Relic.Fixes Procfile and run.0.2.0 (2015-06-19)Integrates configurations locally and Heroku.Changes not use job queue if Package data exists in the cache.Enable to change Celery configuration using CELERY_CONFIG variable and.inifile.Specify package version.Adds linkdraw configuration link.Adds search form at navigation bar.Changes searched view.Coverage >= 90%.Supports running on Heroku.0.1.0 (2015-06-08)Initial release.
Package: pgrate
Package for applying migrations to the postgresql databaseNot for production purposes.Tool to migrate database from files.Install$pipinstallpgrateUsagepgrate-pdirectorie/to/migrations-dpostgres://username:password@localhost:5432/databaseORpgrate-pdirectorie/to/migrations-dpostgresql://username:password@localhost:5432/databaseNOTEMigration name must starts with a number + "_", where number is migration version and ends with *.up.sql example (001_migration_name.up.slq)ExamplesMove into working directory and create default migrations folder$cd/path/to/project
$mkdirmigrationsCreating a migration up and down-- migrations/001_init.up.sqlCREATETABLEIFNOTEXISTSusers(idserialPRIMARYKEY,nameVARCHAR(255));-- migrations/001_init.down.sqlDROPTABLEIFEXISTSusers;Applying migrations$pgrate-p./migrations-dpostgres://username:password@localhost:5432/databaseResultsMigration schemacurrent_versionis_dirt1falseCreating a migration up and down with error-- migrations/002_users.up.sqlCREATETABLEusers(idserialPRIMARYKEY,nameVARCHAR(255));-- migrations/002_users.down.sqlDROPTABLEIFEXISTSusers;Applying migrations$pgrate-p./migrations-dpostgres://username:password@localhost:5432/databaseResultsConsole logasyncpg.exceptions.DuplicateTableError:relation"users"alreadyexistsMigration schemacurrent_versionis_dirt2trueCommandsCommandDescription'-p''--path'Path to migrations folder'-d''--db-uri'Database connection URI
Package: pg_raxarchive
pg_raxarchiveis a command line tool to handle Postgresql WAL archiving on
Rackspace’s cloudfiles.Quick helpInstall using pip then:Create a file/etc/pg_raxarchive.iniwith rackspace credentials (see below).Runpg_raxarchive upload {path_to_file} {basename}to upload archive a file.Runpg_raxarchive download {basename} {path_to_file}to download an archived file.Runpg_raxarchive cleanup {filename}to remove WAL files older than {filename}.Rackspace credential file follows pyrax format:[rackspace_cloud]
username = YUOR_USERNAME_HERE
api_key  = YOUR_API_KEY_HEREYou can customize the region and the container name using:pg_raxarchive--containerCONTAINE_RNAME ...pg_raxarchive--regionREGION_NAME ...By defaultpg_raxarchiveexpects to be running inside rackspace network. If this is
not your case or you want to be billed for some other reasons usepg_raxarchive--use-public.MoreRunpg_raxarchive--helpto know more.Check the repository athttps://github.com/duilio/pg_raxarchive/
Package: pg-rds-params-sync
PostgreSQL RDS Parameters SyncCompare PostgreSQL settings between two databases to detect drift.FeaturesAudit particular settingsExample:$pgrdsparamsyncaudit--parameters=max_wal_sizeIt will get all the databases in the account and region and display theirmax_wal_sizevalue.
Since this can be an expensive operation, a local 1 hour cache is used for each parameter group.If only a subset of databases is of interest,--db-name-likecan be used to filter based on the database name.Example:$pgrdsparamsyncaudit--parameters=max_wal_size,min_wal_size--db-name-like=productionIt will audit only the databases that contain the string "production" in their name and displaymax_wal_sizeandmin_wal_size.For reporting, we can also print out the above table in CSV format.Example:$pgrdsparamsyncaudit--parameters=max_wal_size,min_wal_size--fmt=csvCompare a database to another or a parameter groupExample:$pgrdsparamsyncrds-compare--target-db="users-production"--other-db="orders-production"It will print all the settings that differ between the two databases.If the goal is to set a standard against the entire database fleet, it is possible to compare a database to a parameter group that represents that standard.Example:$pgrdsparamsyncrds-compare--target-db="users-production"--parameter-group="pg-11-standard"It will print all the settings that differ between the target database and the parameter group.Compare two databases directlyExample:$pgrdsparamsyncpg-compare\--target-db-url="postgres://user:password@users-production.rds.awsamazon.com"\--other-db-url="postgres://user:password@orders-production.rds.awsamazom.com"RDS parameter groups use formulas to calculate certain settings (e.g.shared_buffers,effective_cache_size, etc.) by default. Sometimes, it is useful to know the actual value. This will connect to the databases directly, querypg_settings, and print the settings that differ.CachingFetching parameter groups for 100s of databases is long and expensive. We added a local cache with a 1h TTL. It's stored in/tmp/pgrdsparamsync. The first run of the application will be slow, but subsequent runs will be much faster. To increase the TTL or bust the cache, add an environment variableCACHE_TTLwith a value that's not 1h, for example$ export CACHE_TTL=7200which will set the TTL to 2 hours (7200 seconds).
Package: pg-replica-auditor
pg-replica-auditorA tool to compare a PostgreSQL logical replica to its primary. It can help detect data inconsistencies.FeaturesAssumptionsThese tests assume thatidandupdated_at(or column specified in--lag-column) columns exist and have indexes for efficient querying and that the table exists on both databases.Row comparisonRuns row comparisons between primary and replica using two methods:select 8128 rows (or number of rows given to--rows) at random betweenMIN(id)andMAX(id)select the last 1000 rows.Replica lagChecks for "replica lag" by comparingMAX(updated_at)on the given table on both databases.MinMaxChecks that the minimumidand the maximumidmatch on both replica and primary. These can drifta littlebecause of replica lag.Bulk 1000 SumTake the sum of theidcolumn in chunks of 1000 and compare it between databases. This assumes that retrieving rows in bulk is easier than at random and runs faster than the row comparison and can scan more rows.Count all rowsCounts all the rows usingCOUNT(lag_column)to make sure row counts match on both replica and primary. Very slow, since it has to do a full scan (index or table). Adjust--count-beforeto count all columns before a timestamp on--lag-column, orupdated_atby default.Missing Sequential RecordsGo throught the table with a step size ofMAX(id)*--step-size=0.01. The assumption is that if records will be missing, they will be missing in bulk, grouped together.RequirementsPython 3Postgres development files (required by psycopg2). On Mac OS, usebrew install postgresql. On Ubuntu, installlibpq-dev.InstallationDevelopmentUsing virtualenv,pip install -r requirements.txtProductionUsing Pypi,pip install pg-replica-auditor.UsageThis script requires three arguments:--primary, any acceptable Postgres connection string (incl. DSN),--replica, same as--primarybut for the replica database,Optional arguments:--exclude-tables, excludes the comma-separated tables from the scan,--table, only scans this table,--debug, will print debugging information,--rows, will scan this many rows in the row comparisons check,--lag-column, will use this column for the replica lag check,--show-skipped, will print the skipped rows in the Last 1000 check,--count-before, will count all rows in the table created/updated before this timestamp,--step-size, will decrease the step size for missing sequential records search.Example:$pgreplicaauditor--primary=postgres://primary-db.amazonaws.com:5432/my_db--replica=postgres://replica-db.amazonaws.com:5432/my_db--table=immutable_items--lag-column=created_at--count-before="2020-04-06"
Package: pg-replicate-elastic
Replication PostreSQL to Elasticsearch via Logical replication slotsInstall$ pip install pg-replicate-elasticwal2jsonNote:Use my fork as we tested it to be 100% sure it work with it and no breaking changes happen,wal2json.$ git clone https://github.com/hmilkovi/wal2json.git
$ PATH=/path/to/bin/pg_config:$PATH
$ USE_PGXS=1 make
$ USE_PGXS=1 make installYou need to set up at least two parameters at postgresql.conf:wal_level = logical
max_replication_slots = 1After changing these parameters, a restart is needed.Usagepg_replicate_elastic --config=<absolute path to json config>Construct configuration file in json format where:replication_slotjson object for replication slot name and if is temporarytablesis array of tables we want to replicatees_connectionconnection string to Elasticsearchpostgresjson object for PostreSQL connectioninital_syncboolean for inital syncronization that needs to be done first time
to replicate old dataExample configuration{
	"replication_slot": {
		"name": "elasticsearch_slot",
		"is_temp": true
	},
	"tables": [{
		"name": "poc",
		"primary_key": "a"
		"exclude_columns": "c,z"
	}],
	"es_connection": "http://127.0.0.1:9200/",
	"postgres": {
		"port": 5432,
		"host": "127.0.0.1",
		"database": "poc",
		"username": "test",
		"password": "test"
	},
	"inital_sync": false
}Notewal2json is not my software so for licence checktheir licence
Package: pgrok
Python Tunneling client forpgrokpgrok-pyis a Python wrapper forpgrokthat manages its own binary and puts
it on your path, makingpgrokreadily available from anywhere on the command line and via a
convenient Python API.pgrokis a reverse proxy tool which is open-source version ofngrokthat opens secure tunnels from public URLs to localhost, perfect for exposing local web servers, building webhook integrations, enabling SSH access, testing chatbots, demoing from
your own machine, and more, and its made even more powerful with native Python integration throughpgrok-py.This provide additional functionality of self-hosting tunnelling server to aws/droplet instance and also additional benefits to escape monthly recurring charges of ngrok.Installationpipinstallgit+https://github.com/sandyz1000/pgrok-py.gitBasic UsagePgrok tunnel-backendfrompgrokimportpgrok# Open a HTTP tunnel on the default port 80# <PgrokTunnel: "http://<public_sub>.pgrok.io" -> "http://localhost:80">http_tunnel=pgrok.connect()# Open a SSH tunnel# <PgrokTunnel: "https://colabshell.ejemplo.me" -> "localhost:8080">ssh_tunnel=pgrok.connect(addr=8080,proto='http',name='colabshell')Theconnectmethod takeskwargsas well, which allows us to pass additional properties that aresupported by pgrok.This package puts the defaultpgrokbinary on our path, so all features ofpgrokare available on the command line.pgrokhttp80
Package: pgsanity
PgSanity checks the syntax of Postgresql SQL files.It does this by leveraging the ecpg command which is traditionally
used for preparing C files with embedded sql for compilation.
However, as part of that preparation, ecpg checks the embedded SQL
statements for syntax errors using the exact same parser that is
in PostgreSQL.So the approach that PgSanity takes is to take a file that has a
list of bare SQL in it, make that file look like a C file with
embedded SQL, run it through ecpg and let ecpg report on the syntax
errors of the SQL.
Package: pgscatalog-utils
PGS Catalog utilitiesThis repository is a collection of useful tools for downloading and working with scoring files from the
PGS Catalog. This is mostly used internally by the PGS Catalog Calculator (PGScatalog/pgsc_calc); however, other users may find some of these tools helpful.Overviewdownload_scorefiles: Download scoring files by PGS ID (accession) in genome builds GRCh37 or GRCh38combine_scorefile: Combine multiple scoring files into a single scoring file
in 'long' formatmatch_variants: Match target variants (bim or pvar files) against the output
ofcombine_scorefileto produce scoring files for plink 2ancestry_analysis: use genetic PCA loadings to compare samples to population reference panels, and report PGS adjusted for these axes of genetic ancestry. The PCs will likely have been generated withFRAPOSA (pgs catalog version)validate_scorefiles: Check/validate that the scoring files and harmonized scoring files match the PGS Catalog scoring file formats.Installation$ pip install pgscatalog-utilsQuickstart$ download_scorefiles -i PGS000922 PGS001229 -o . -b GRCh37
$ combine_scorefiles -s PGS*.txt.gz -o combined.txt 
$ match_variants -s combined.txt -t <example.pvar> --min_overlap 0.75 --outdir .
$ validate_scorefiles -t formatted --dir <scoringfiles_directory> --log_dir <logs_directory>More details are available using the--helpparameter.Install from sourceRequirements:python 3.10poetry$ git clone https://github.com/PGScatalog/pgscatalog_utils.git
$ cd pgscatalog_utils
$ poetry install
$ poetry build
$ pip install --user dist/*.whlCreditsThepgscatalog_utilspackage is developed as part of thePolygenic Score (PGS) Catalog(www.PGSCatalog.org) project, a collaboration between the
University of Cambridge’s Department of Public Health and Primary Care (Michael Inouye, Samuel Lambert, Laurent Gil)
and the European Bioinformatics Institute (Helen Parkinson, Aoife McMahon, Ben Wingfield, Laura Harris).A manuscript describing the tool and larger PGS Catalog Calculator pipeline(PGSCatalog/pgsc_calc)is in preparation. In the meantime
if you use these tools we ask you to cite the repo(s) and the paper describing the PGS Catalog resource:PGS Catalog utilities(in development). PGS Catalog
Team.https://github.com/PGScatalog/pgscatalog_utilsPGS Catalog Calculator(in development). PGS Catalog
Team.https://github.com/PGScatalog/pgsc_calcLambertet al.(2021) The Polygenic Score Catalog as an open database for
reproducibility and systematic evaluation.  Nature Genetics. 53:420–425
doi:10.1038/s41588-021-00783-5.This work has received funding from EMBL-EBI core funds, the Baker Institute, the University of Cambridge,
Health Data Research UK (HDRUK), and the European Union's Horizon 2020 research and innovation programme
under grant agreement No 101016775 INTERVENE.
Package: pgs-climbing
ClimbingThis repo covers a few classes that describe rock-climbing.  It was created as an exercise in package development.Location on PyPiLocation on GithubQuickstartIt is available to install using pip, e.g. for python3 use:python3 -m pip install pgs_climbingAnd can then be used by importing into your python files:from pgs_climbing import Crag, Route, Climber, GRADES_LISTContentsThe classes are currently:Crag - A class to hold information about each climbing area, the routes it contains and its location.Route - A class to hold information about a particular route - its name, grade, height etc.Climber - A class to hold information about a climber, the routes they have attempted/climbed and when.The class descriptions can be found in theclimbing_package/pgs_climbingdirectoryExample outputThere is a jupyter notebook inexamples/if you want to see it in actionIt currently has two basic visual summary methods, one on the crag class summarising the routes at that crag:and one on the climber class, showing their progress over time: