Saravanan666/pypi-org huggingface dataset:
Package: germantournament
# Tournament Scheduling[![Build Status](https://travis-ci.org/guemues/german-game-tournament.svg?branch=master)](https://travis-ci.org/guemues/german-game-tournament) [![Coverage Status](https://coveralls.io/repos/github/guemues/german-game-tournament/badge.svg?branch=master)](https://coveralls.io/github/guemues/german-game-tournament?branch=master)This repository created for a tournament scheduling problem.The purpose is prevent placing same players more than one times in the same game.You can schedule your tournament in only one way with this repo. More scheduling types including round-robin may or may not added.The algorithm works like this for 16 person tournement:```[0, 1, 2 ... 15]```For 4 player catan tournementFirst Cycle:```[0, 1, 2, 3][4, 5, 6, 7][8, 9, 10, 11][12, 13, 14, 15]```Second Cycle:```[0, 4, 8, 12][1, 5, 9, 13][2, 6, 10, 14][3, 7, 11, 15]```Support for game_per_player (game count for players) other then 2 is not tested.With this algorithm you need k * power(player count in one game, game count for one player) player. k must be integer bigger than 0.### Installing```pip install germantournament```### UsageExample```>>>from germantournament.GameTournament import GermanGameTournament>>>tournament = GermanGameTournament()>>>tournament.set_player_count(16)>>>scheduled_events = tournament.schedule(player_count_in_one_game=4)>>>print(scheduled_events)[[0, 4, 8, 12], [3, 7, 11, 15], [1, 5, 9, 13], [2, 6, 10, 14], [4, 5, 6, 7], [0, 1, 2, 3], [12, 13, 14, 15], [8, 9, 10, 11]]```
Package: germqtt
Germqtt, like its name implies, is a tool for publish a gerrit event stream
into MQTT. It will publish all the capture events from the gerrit event stream
and publish them to MQTT into topics split by project and event type. For
example a commented added to a project name foo would be published as an event
on the topic: base_topic/foo/commented-addedBy default germqtt is setup as a daemon however if you need to run it
interactively you can use the–foregroundoption to do this.ConfigurationThere are a few required pieces of information to make germqtt work properly.
These settings are specified in the config file.GerritYou need to provide credentials and connection information for connecting to
gerrit to get the event stream. Germqtt uses the gerritlib library to establish
a connection to gerrit over ssh and listen to the event stream. All these
options live in the[gerrit]section.  The 3 required options for gerrit are:username- The username to login withhostname- The hostname for your gerrit serverkey- The path to your ssh key to use for connecting to gerritThere is also an optional config option,port, which is used to specify the
port to connect to gerrit with. By default this is set to 29418, which is the
gerrit default. If your gerrit server uses a non-default port you’ll need to set
this option.MQTTJust as with gerrit there are a few required options for talking to MQTT, which
is the other axis of communication in germqtt. The options for configuring MQTT
communication go in the[mqtt]section. The 2 required options are:hostname- The hostname for the MQTT brokertopic- The base topic name to use for the gerrit eventsThere are also a couple optional settings for communicating with mqtt that you
can set:port- The port to communicate to the MQTT broker on. By default thisis set to 1883, the default MQTT port. This only needs to be set
if your broker uses a non-default port.keepalive- Used to set the keepalive time for connections to the MQTTbroker. By default this is set to 60 seconds.username- Used to set the auth username to connect to the MQTT brokerwith.password- Used to set the auth password to connect to the MQTT brokerwith. A username must be set for this option to be used.Other SettingsBy default germqtt will use /var/run/germqtt.pid for it’s PID file, if however
you’d like to use a different file for storing the PID you can use thepidfileoption in the[default]section of the configuration file.
Package: gerobust
gerobust — Robust GeometryPython extension of the C implementation of robust and quick incircles tests,
produced byJanathan Richard Shewchukand explained in its paperRobust Adaptive Floating-Point Geometric Predicates.usage example(see more intests)from gerobust.predicates import clockwise, counter_clockwise, incircle

triangle = (0, 0), (0, 1), (1, 0)

print(clockwise(*triangle))  # True
print(counter_clockwise.fast(*triangle))  # False
print(incircle(*triangle, (1, 1)))  # False
print(incircle(*triangle, (1, 1), strict=False))  # Trueinstallationpip install gerobustTestsgit clone git@github.com:Aluriak/gerobust.git
cd gerobust
make testslinksgithubandpypiFloating-point and compilerThe technics used in the C code needs the compiler to work with the
IEEE 754 floating-point standard.By looking about it in the web, i foundthe gcc wikithat seems to get its full support (without micro optimization that could kill the C implementation)
with the-frounding-math -fsignaling-nansoptions or the#pragma STDC FENV ACCESS ONpragma.The formeris used. I however expect that only gcc is handled with this library. IEEE 754 compliancy through a standard way should be a short-term goal.ContributionsPatches as PR and ideas as issues are welcome.Few ways to improve this lib :more geometric applications of the global method, for a more complete librarycompatibility with others compiler/OSunit test showing the (¬)robustness of functionsgeneral improvements over the python codebase (organization, style, efficiency, doc)BibliographyAbstract and citation reproduced below.Robust Adaptive Floating-Point Geometric Predicates

                         Jonathan Richard Shewchuk
                         School of Computer Science
                         Carnegie Mellon University
                       Pittsburgh, Pennsylvania 15213

Fast C implementations of four geometric predicates, the 2D and 3D orientation
and incircle tests, are publicly available.  Their inputs are ordinary single
or double precision floating-point numbers.  They owe their speed to two
features.  First, they employ new fast algorithms for arbitrary precision
arithmetic that have a strong advantage over other software techniques in
computations that manipulate values of extended but small precision.  Second,
they are adaptive; their running time depends on the degree of uncertainty of
the result, and is usually small.  These algorithms work on computers whose
floating-point arithmetic uses radix two and exact rounding, including machines
that comply with the IEEE 754 floating-point standard.  Timings of the
predicates, in isolation and embedded in 2D and 3D Delaunay triangulation
programs, verify their effectiveness.


Proceedings of the Twelfth Annual Symposium on Computational Geometry
(Philadelphia, Pennsylvania), pages 141-150, ACM, May 1996.  PostScript (310k).


Paper available through the URL
http://www.cs.berkeley.edu/~jrs/papers/robust-predicates.ps


For additional details and associated software, see the Web page
http://www.cs.cmu.edu/~quake/robust.html
Package: gerridae
this is new spider framework gerridae学习之作, 参考ruia安装使用pip安装pipinstallgerridae--user使用pipenv安装pipenvinstallgerridae使用源码安装gitclonehttps://github.com/BUGLAN/gerridae

pythonsetup.pyinstall测试安装测试依赖包pipenvinstall--dev执行测试pipenvrunpytest额外说明基本是一个学习之作, 可以说一个简单的玩具, 请勿使用在生产环境之中
Package: gerrit
python-gerrit is a Python interface to Gerrit, a code review system
for Git.DISCLAIMER: Gerrit does not have an official API. This library is a product
of reverse engineering.APIs exposedThere are three APIs available in python-gerrit:rpc - basic JSON-RPC API over HTTP; it has the same functionality
as the standard Gerrit client.db - raw access to the database. It understandably needs more
privileges than simple HTTP.raw - direct access to the filesystem. It needs local access
to the Gerrit installation.Most use cases can be satisfied by JSON-RPC alone. There are some
glaring ommisions in the functionality, though, so for things such as
project creation you will need to use db/raw. Check documentation of
corresponding modules for more.Testingpython-gerrit comes with a test suite. In order to run it, you need
to have gerrit installed locally, with full access to its
raw directory and database. Testing is managed bypy.testYou can run it by executing:py.testTests expects the following environment variables to be set:GERRIT_PATH - path to a Gerrit installationGERRIT_DB - sqlalchemy URL to the Gerrit databaseGERRIT_GIT - URL to the Gerrit git repositoryGERRIT_URL - URL to the Gerrit HTTP serverGERRIT_USERNAME - a user the suite with interact asCheck that the provided user has all the privileges required to
submit, vote, comment, and so on.Also, be sure your Gerrit installation has authentication method set
to DEVELOPMENT_BECOME_ANY_ACCOUNT.CreditsBrian Waldon
Mike Hordecki
Package: gerritaction
gerritactionIntroductiongerritactionis a tool used for Gerrit action via Gerrit API.PrerequisitesPython >= 3.7.0Rungitclonehttps://github.com/craftslab/gerritaction.gitcdgerritaction
pipinstall-Urrequirements.txt
pythonaction.py--config-file="config.yml"--gerrit-action="delete-reviewer:account-id,..."--gerrit-query="since:2021-01-01 until:2021-01-02"Dockergitclonehttps://github.com/craftslab/gerritaction.gitcdgerritaction
dockerbuild--no-cache-fDockerfile-tcraftslab/gerritaction:latest.
dockerrun-it-v/tmp:/tmpcraftslab/gerritaction:latest./gerritaction--config-file="config.yml"--gerrit-action="delete-reviewer:account-id,..."--gerrit-query="since:2021-01-01 until:2021-01-02"Usageusage: action.py [-h] --config-file CONFIG_FILE --gerrit-action GERRIT_ACTION --gerrit-query GERRIT_QUERY [-v]

Gerrit Action

optional arguments:
  -h, --help            show this help message and exit
  --config-file CONFIG_FILE
                        config file (.yml)
  --gerrit-action GERRIT_ACTION
                        gerrit action (add-reviewer:account-id,... delete-reviewer:account-id,... add-attention:account-id,... remove-attention:account-id,... approve-change:Code-Review=+2,... delete-change submit-change)
  --gerrit-query GERRIT_QUERY
                        gerrit query (status:open since:2021-01-01 until:2021-01-02)
  -v, --version         show program's version number and exitSettingsgerritactionparameters can be set in the directoryconfig.An example of configuration inconfig.yml:apiVersion:v1kind:workermetadata:name:gerritactionspec:gerrit:host:http://127.0.0.1/port:8080user:userpass:passquery:option:-CURRENT_REVISIONLicenseProject License can be foundhere.
Package: gerritbot
Gerritbot is an IRC bot that will notify IRC channels of Gerrit events.To install:$ sudo python setup.py installOnline documentation:http://docs.openstack.org/infra/system-config/gerrit.html#gerrit-irc-botDevelopersReport bugs:https://storyboard.openstack.org/#!/project/717Browse code:https://git.openstack.org/cgit/openstack-infra/gerritbot/tree/Clone:git://git.openstack.org/openstack-infra/gerritbotSubmit patches via Gerrit at:https://review.openstack.org/More details on how you can contribute is available on our wiki at:http://wiki.openstack.org/HowToContributeLicenseCopyright 2011 OpenStack, LLC
Copyright 2012-2013 Hewlett-Packard Development Company, L.P.Licensed 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: gerrit-check
Many projects use Gerrit for code-reviews and in addition use static code
analysis tools to report about the quality of the code in review. For example,
Jenkins comes with a nice integration of Gerrit, there is no suitable way to
generate line-by-line annotations of the output of static code analysis tools
for Gerrit.This project allows you to transform the output of the tools: cppcheck,
cpplint and flake8 into line by line comments in Gerrit.
Package: gerrit-dash-creator
Creates custom URLs for Gerrit dashboardsThe ProblemThe Gerrit code review system is great, until it gets completely out of
control with too much content in it. When you are staring at a single
list of 400 reviews, it’s completely overwhelming.Sisyphus never had it so good.The SolutionI’ve found that slicing up the giant review task into a set of smaller
buckets that you can see actually get smaller as you go through them
becomes a far more motivating way of looking at reviews.As of Gerrit 2.6 there is support for building custom dashboards, both
on the server side, and on the client side (as a URL). These are
really powerful.The server side definition for these dashboards is pretty easy to
understand, however you need really extreme levels of permissions to
create these dashboards. The client side definition is a single URL
which is hard to manipulate inline.This tool takes the server side definition, creates the client side
encoding of it, and spits that URL out on the command line. You can
then load it in your browser and off you go.UsageIt’s super easy, just check out the code, and pass 1 argument, which is
the dashboard file you want the URL for:$ ./gerrit-dash-creator dashboards/devstack.dash
https://review.opendev.org/#/dashboard/?title=Devstack+Review+Inbox&foreach=%28project%3Aopenstack%2Fdevstack+OR+project%3Aopenstack%2Fdevstack%2Dvagrant+OR+project%3Aopenstack%2Fgrenade%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3Aworkflow%3E%3D1&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cdevstack%2Dcore+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cdevstack%2Dcore+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2dThen put the URL in your browser and off you go.The latest dashboards are available athttp://gerrit-dash-creator.readthedocs.org/en/latest/dashboards/index.htmlContributions WelcomedIf you have a dashboard definition that your OpenStack team finds
useful, please submit a change request via git-review. The list of
current outstanding changes can be seen at:https://review.opendev.org/#/q/status:open+project:x/gerrit-dash-creator,n,zI’m very happy to include additional interesting examples that teams
find useful, and make it possible for teams to explore other
approaches to reviewing code.If you have questions please find me on #openstack-dev,
#openstack-infra, or #openstack-qa on FreeNode to discuss.
Package: gerritexec
gerritexecgerritexec is a command line toollistening to gerriton a designated project. On eachnew patchset, (or when a comment containsrecheck no bugorrun gerritexec) it will:git clone the projectgit pull the patchsetcd in the git tree and run a scriptpositively review the patchset ( +1 ) if the program exit(0)negatively review the patchset ( -1 ) otherwiseExamplesPositively review all patchsets in thestackforge/puppet-cephproject:gerritexec--hostnamereview.openstack.org\--usernamepuppetceph\--script'true'\--projectstackforge/puppet-cephRun theintegration testsfound in the git tree of thestackforge/puppet-cephproject:gerritexec--hostnamereview.openstack.org\--usernamepuppetceph\--script'bundle exec rake spec:system'\--projectstackforge/puppet-cephHackingGet the code : git clonegit@gitorious.org:gerritexec/gerritexec.gitRun the tests : toxTag a versionedit the version field of setup.cfggit tag -a -m ‘whatever’ 2.1.1git push –tagsCheck the documentation : rst2html < README.rst > /tmp/a.htmlPublishpython setup.py sdist upload –signtrim old versions athttps://pypi.python.org/pypi/gerritexec
Package: gerrit-growler
Receive a growl notifications from Gerrit.Currently, you’ll only receive notifications on reviews that you have starred.DependenciesThis currently depends onterminal-notifieron OS X 10.8+ to produce
notifications:$ brew install terminal-notifierI’d be happy to see support added for additional notification frameworks.InstallationInstall from PyPi:$ pip install gerrit-growlerUsageJust run the listener:$ gerrit-growlerSee--helpfor authentication and Gerrit endpoint options.
Package: gerrit-hooks
# Gerrit Hooks Argument ParsersThis library provides pre-built `argparse.ArgumentParser` instances, whichreturn `argpase.NameSpace` object for gerrit's hooks (linked in the [Resources](#resources) section below).It allows developers to get started with gerrit hooks faster, bygetting the parsing of command-line arguments for the various hook typesout of the way.All hooks are supported.# Installation```pip install gerrit-hooks```# UsageWriting hooks using gerrit-hooks' argparsers is easy:```python> gerrit/hooks/comment-added#!/usr/bin/env/python3import gerrit_hooksoptions = gerrit_hooks.parse_options()print("Change ID: {}".format(options.change))...```Custom approval categories are supported as well - these must be addedbefore calling `gerrit_hooks.parse_options()`:```python> gerrit/hooks/comment-added#!/usr/bin/env/python3import gerrit_hooks# Let's assume you have a approval category with label 'level-of-amazingness# We need to add this to the Hook Flag Definitions classgerrit_hooks.add_custom_approval_category('level-of-amazingness')options = gerrit_hooks.parse_options()# The approval category can be accessed by the following attributes:print("Level of Amazingness is: {}".format(options.level_of_amazingness))print("Level of Amazingness was: {}".format(options.level_of_amazingness_oldValue))...```# Resources[Gerrit-Hooks Plugin](https://gerrit-review.googlesource.com/admin/repos/plugins%2Fhooks)
Package: gerritlib
Gerritlib is a Python library for interacting withGerrit.
It aims to provide a more conventionally pythonic way of managing a
Gerrit instance.To install:$ sudo python setup.py installOnline documentation:http://gerritlib.readthedocs.org/en/latest/DevelopersBug report:https://storyboard.openstack.org/#!/project/718Repository:https://git.openstack.org/cgit/openstack-infra/gerritlibCloning:git clone https://git.openstack.org/openstack-infra/gerritlibPatches are submitted via Gerrit at:https://review.openstack.org/Please do not submit GitHub pull requests, they will be automatically closed.More details on how you can contribute is available on our wiki at:http://docs.openstack.org/infra/manual/developers.htmlWriting a patchWe ask that all code submissions bepep8andpyflakesclean.  The
easiest way to do that is to runtoxbefore submitting code for
review in Gerrit.  It will runpep8andpyflakesin the same
manner as the automated test suite that will run on proposed
patchsets.Installing without setup.pyThen install the required python packages usingpip:$ sudo pip install gerritlib
Package: gerritqueue
gerritqueueGerrit Queueis a Gerrit event queue using Redis.RequirementsPython (3.7+)pipredisInstallationaptupdate
aptinstallpython3-devpython3-pippython3-setuptools
pipinstallgerritqueueUpdatingpipinstallgerritqueue--upgradeRunninggerritqueue\--config-fileconfig.json\--gerrit-query"change:1"SettingsGerrit Queueparameters can be set in the file ofconfig.json.An example of configuration in config.json{
  "gerrit": {
    "debug": false,
    "host": "localhost",
    "pass": "pass",
    "port": 80,
    "query": {
      "option": ["CURRENT_REVISION"]
    },
    "user": "user"
  },
  "redis": {
    "db": 0,
    "debug": false,
    "hash": {
      "expire": {
        "days": 1
      },
      "name": "_number",
      "value": "current_revision"
    },
    "host": "localhost",
    "pass": "pass",
    "port": 6379
  }
}RedisName           Value
CHANGE_NUMBER  CURRENT_REVISIONLicense ApacheProject License can be foundhere.
Package: gerrit-review-robot
gerrit_review_robotA framework for writing bots, that review a code base and post
the review together with comments to Gerrit. To write a bot,
inheritGerritReviewRobot:classCheckStyle(GerritReviewRobot):# these two are optional: for documentation and the command-linename="Check Style"description="Uses Flake8 to lint the current change"def_do_review(self,review):# pass self.diff_lines so that we do not have to analyze files that# are not part of the current changeforerrorinself._find_linting_errors_in_files(self.diff_files)# only include lines in current diffif(error.file,error.line_number)inself.diff_lines:review.add_comment(error.file,# relative path(error.line_number,error.line_number),# from_line, to_lineerror.message# message shown in the comment)def_find_linting_errors_in_files(self,files):pass# here comes the actual logic
Package: gerrit-robo
gerrit-roboThis is a very thin wrapper around the gerrit api to
allow robots to add comments to a patchset (and maybe
more later)Please note, that this a work in progress and is not usable, nor testedUsagegerrit = Gerrit('http://review.domain.de', 'projectname').with_auth(
    'your_username', '<<http_password>>')
change_id = 'I09d1b8dc8d9eb072d4bd387f4c75c80cda43ebd5'

review = Review('The bot reviewed')
review.comment('README.md', [1, 3], 'A robot comment')
review.comment('README.md', 4, 'This is a comment, too')
gerrit.send_review(change_id, review)Generate HTTP PasswordYou cannot login with your normal password. Rather:Login into GerritClick on your profile image > Settings > HTTP CredentialsGenerate New PasswordCopy it immediatly as it will be lost ast soon as you close this modaInset it into your source-code undergerrit.with_auth(foundhere)
Package: gerritstats
Gerrit StatsGerrit Statsis a tool used for Gerrit stats via Gerrit API.Requirementpython >= 3.7Buildpip install -U pywin32
pip install -U pyinstaller
pip install -Ur requirements.txt

pyinstaller --clean --name gerritstats -F stats.pyInstallationpipinstallgerritstatsUpdatepipinstallgerritstats--upgradeRungerritstats--config-fileconfig.json--gerrit-query"since:2020-06-01 until:2020-06-02"--output-fileoutput.jsonSettingsGerrit Statsparameters can be set in the directoryconfig.An example of configuration inconfig.json:{
  "gerrit": {
    "host": "localhost:80",
    "pass": "pass",
    "query": {
      "option": ["CURRENT_REVISION"]
    },
    "user": "user"
  }
}LicenseProject License can be foundhere.