Saravanan666/pypi-org huggingface dataset:
Package: cz-conventional-gitmoji
cz-conventional-gitmojiAcommitizenplugin that combinesgitmojiandconventional commits.Installationpoetryaddcz-conventional-gitmojior with pip:pipinstallcz-conventional-gitmojiUsageThis package can be used as a normalcommitizenplugin, either by specifying the name on the command linecz--namecz_gitmojicommitor by setting it in yourpyproject.toml[tool.commitizen]name="cz_gitmoji"This will makecommitizenuse the commit message parsing rules defined by this plugin, which are 100% compatible withconventional commits. As such, the gitmojis are completely optional and all commands will continue to validate commit messages in conventional format just fine. This is useful if you're transitioning an existing repo tocz-conventional-gitmojior you work in a team in which some colleagues don't like gitmojis.gitmojifyApart from the conventional-gitmoji rules, this package provides thegitmojifycommand which is also available as a pre-commit hook. The command reads a commit message either from cli or a commit message file and prepends the correct gitmoji based on the type. If the message already has a gitmoji, it is returned as is.$gitmojify-m"init: initial version"🎉init:initialversionTo use it as a pre-commit hook, install this packages as well ascommitizenand put the following into your.pre-commit-config.yamlrepos:-repo:https://github.com/ljnsn/cz-conventional-gitmojirev:mainhooks:-id:conventional-gitmojiCommit with a message in conventional format that contains a valid type mapped by conventional gitmoji and the gitmoji will automagically be added.FeaturesEnable conventional gitmoji commit messages viacz commit.Add--simple-emojisoption to use only the emojis relating tocz_conventional_commitstypes.Add--simple-typesoption to use only the types used bycz_conventional_commits.Add--conventionaloption to put the emoji in the commit message, making it compatible withcz_conventional_commits.Add hook to automatically prepend the appropriate gitmoji for the commit's type.Inspirationcommitizen-emoji
Package: cz-convnetional-ticket
Convnetional TicketThis is a template for commitizen. This is based on conventional commits. It provides extra options to enter ticket number in commit message and changelog.PrerequisiteYou must havecommitizeninstalled before installing this package.
To install commitizen runpip install -U commitizenUsagepip install cz_conventional_ticketIn.cz.tomlor project file of commmitizen usecz_conventional_ticketinnamefieldExample.cz.toml[tool.commitizen]
name = "cz_convnetional_ticket"
version = "5.2.0"
tag_format = "v$version"AuthorGohar Anwar (gohar@goharanwar.com)
Package: czds
CZDSWhat is CZDS?Each Top Level Domain (TLD) is maintained by a registry operator, who also manages a publicly available list of Second Level Domains (SLDs) and the details needed to resolve those domain names to Internet Protocol (IP) addresses.The registry operator’s zone data contains the mapping of domain names, associated name server names, and IP addresses for those name servers. These details are updated by the registry operator for its respective TLDs whenever information changes or a domain name is added or removed.Each registry operator keeps its zone data in a text file called the Zone File which is updated once every 24 hours.FeaturesRetrieve Centralized Zone Transfer Files from root DNS servers hosted by ICAAN and other agenciesDownload one or all of the zone files and return data in multiple formats; text, json or a file (default)You can now retrieve zone files using multi-threadingRoadmapThe following are some of the features I am planning on adding but would love to hear everyones thoughts as well.Add ability to search based on domain and/or TLDThis may include using algorithms like Levenshtein distance, confusables/idna characters, etc.Add ability to derive differences between zone files over timeAdd ability to retrieve other contextual external information like WHOISAdd ability to save/store data into a databaseRequirementsYou need a CZDS account with ICAAN. You can sign-uphereInternet accessInstallationYou can installCZDSviapipfromPyPI:$pipinstallczdsIf you are usingpoetry(recommended) you can add it to your package usingpoetry add czdsUsageBelow is the command line reference but you can also use the current version of czds to retrieve the help by typingczds --help.NAMEczds - Main class for ICAAN CZDS.SYNOPSISczds GROUP | VALUE | --username=USERNAME --password=PASSWORD --save_directory=SAVE_DIRECTORYDESCRIPTIONMain class for ICAAN CZDS.ARGUMENTSUSERNAMEType: ~AnyStrPASSWORDType: ~AnyStrSAVE_DIRECTORYType: ~AnyStrGROUPSGROUP is one of the following:BASE_HEADERSlinksVALUESVALUE is one of the following:AUTH_URLBASE_URLOUTPUT_FORMATPASSWORDSAVE_PATHTHREAD_COUNTUSERNAMEconnectionContributingContributions are very welcome.
To learn more, see theContributor Guide.DevelopmemtYou can clone the repositry and begin development usinggitclonehttps://github.com/MSAdministrator/czds.gitcdczds
poetryinstallIf you are usingpyenvto manage your enviroments you can set a config option in poetry to use the set pyenv version of python by running this:poetryconfigvirtualenvs.prefer-active-pythontruepoetryinstallLicenseDistributed under the terms of the [MIT license][LICENSE.md],CZDSis free and open source software.SecuritySecurity concerns are a top priority for us, please review ourSecurity Policy.IssuesIf you encounter any problems,
pleasefile an issuealong with a detailed description.CreditsThis project was generated from@MSAdministrator'sHypermodern Python Cookiecuttertemplate.
Package: czech-covid19-data-api
czech-covid19-data-apiAPI wrapper for official covid19 data. Written in Python. Data sourcehttps://onemocneni-aktualne.mzcr.cz/api/v2/covid-19.InstallationJust use:pip install czech-covid19-data-apiAPI documentationSphinxautogenerated API docs can be foundHERE. Nothing fancy, but gets the job done.How to useExample 1: Get data in JSON format:from covid19_api.src import api

if __name__ == "__main__":
    (status, data) = api.get_deaths_overview()

    if status:
        print(data)Example 2: Get data in CSV format:from covid19_api.src import api

if __name__ == "__main__":
    (status, data) = api.get_deaths_overview(resource="/umrti.csv")

    if status:
        print(data)
Package: czech-eet
Python EET APISimple to use and mostly secure (mainly pedantic) API for Czech EET Gate.Installationpip install czech-eetUsageBasic usage with single requestfromeetimportinvoices,helperscert_text=b'''-----BEGIN CERTIFICATE-----...-----END CERTIFICATE-----'''key_text=b'''-----BEGIN RSA PRIVATE KEY-----...-----END RSA PRIVATE KEY-----'''# prepare certificate and private keycert=helpers.parse_cert(cert_text)pk=helpers.parse_key(key_text)# create configconfig=invoices.Config(cert,pk,141,"1patro-vpravo")# create factory using configfactory=invoices.Factory(config)# build new invoice & sendinvoice=factory.new("141-18543-05",236.00,zakl_dan1=100.0,dan1=21.0)response=invoice.send()# note: if resending, you should set `eet.invoice.Hlavicka["prvni_zaslani"] = eet.types.boolean(False)`#       or use scheduler ;-)# now validate response and get fikcodes=response.codes()ifresponse:print("BKP:{0}\nFIK:{1}".format(codes.bkp,codes.fik))else:print("BKP:{0}\nPKP:{1}".format(codes.bkp,codes.pkp))print("Errors:",response.Chyba,response.Varovani)Example of schedulerfromeetimportinvoices,helpers,remote...# prepare invoice as before# create instance of schedulerscheduler=remote.Scheduler()# same as before but now you can resend invoicesresponse=scheduler.process(invoice)# call dispatch is reasonable time interval from your mainloopimporttimewhileTrue:scheduler.dispatch()time.sleep(60)
Package: czech-holidays
Python package withCzech public holidays.InstallationFrom PyPI:pip install czech-holidaysIn case you have an adventurous mind, give a try to the source:pip install git+https://github.com/honzajavorek/czech-holidays.git#egg=czech-holidaysExamplesCzech Holidays provides the following interface:>>>fromczech_holidaysimportczech_holidays>>>holidays=czech_holidays(2022)>>>holidays[:3][Holiday(date=datetime.date(2022,1,1),name='Nový rok',name_en="New Year's Day"),Holiday(date=datetime.date(2022,1,1),name='Den obnovy samostatného českého státu',name_en='Restoration Day of the Independent Czech State'),Holiday(date=datetime.date(2022,4,18),name='Velikonoční pondělí',name_en='Easter Monday')]The function accepts year as a single argument and returns a list ofnamed tuples:>>>holidays[0].datedatetime.date(2022,1,1)>>>holidays[0].name'Nový rok'>>>holidays[0].name_en"New Year's Day"Albeit named, it’s still just a tuple:>>>holidays[0][0]datetime.date(2022,1,1)>>>holidays[0][1]'Nový rok'>>>holidays[0][2]"New Year's Day">>>tuple(holidays[0])(datetime.date(2022,1,1),'Nový rok',"New Year's Day")>>>holidays[0]<holidays[5]TrueTwo shortcuts are available:>>>fromczech_holidaysimportczech_easter,czech_christmas>>>czech_easter(2022)Holiday(date=datetime.date(2022,4,18),name='Velikonoční pondělí',name_en='Easter Monday')>>>czech_christmas(2022)Holiday(date=datetime.date(2022,12,24),name='Štědrý den',name_en='Christmas Eve')The aim of this library is to simplify work with Czech public holidays in current
applications, thusit does not provide any historical data:>>>czech_holidays(2013)Traceback(mostrecentcalllast):NotImplementedError:...DevelopmentInstall usingpoetry:git clone git@github.com:honzajavorek/czech-holidays.git
cd czech-holidays
poetry installThen run tests:pytestLicense: MIT© 2022 Honza Javorek <mail@honzajavorek.cz>This work is licensed underMIT license.
Package: czech-sort
Czech SortThis is a pure-Python library for Czech-language alphabetical sorting.Quick UseFrom Python:>>>importczech_sort>>>czech_sort.sorted(['sídliště','shoda','schody'])['shoda','schody','sídliště']>>>sorted(['sídliště','shoda','schody'],key=czech_sort.key)['shoda','schody','sídliště']On the command line::$python-mczech_sort<file.txtshodaschodysídlištěWhy another sorting library?To sort Python strings in the Czech language, there are three other options:UsePyICU. This can sortreallywell, and do all kinds of wonderful,
standards-compliant Unicode things. Perfect for publication-quality results.
Unfortunately, ICU can be a major pain to install, making it overkill if you
just want to sort a list of strings.Set the locale, then uselocale.strxfrm.
(Yes,strxfrm! Try saying that ten times fast!)
This depends on the Czech POSIX locale being available, so it's hardly
portable.Just use Python's built-in string sort. This sorts lexicographically by
Unicode codepoints. It might be good enough for you? Maybe?ScopeTheczech-sortlibrary is a compromise. It should give you good results in
the 99% case.Do not use this if you need proper sorting of symbols, non-Latin scripts,
or diacritics other than Czech/Slovak.Any other deviation from the relevant standard,ČSN 97 6030, should be
considered a bug. However, neither the author nor the community at large
have access to the standard, which makes finding such bugs somewhat difficult.Full APIczech_sort.sorted(iterable)Takes an iterable of strings, and returns a list of them, sorted.czech_sort.key(s)Returns a sort key object for a given string.This function is suitable as thekeyfor functions like the built-insortedorlist.sort.czech_sort.bytes_key(s)Returns a sort key for a given string, as bytes.This is suitable as a DB-API custom function like the built-insqlite3connection'screate_function.WARNING: Do not store the results of this function. The format can change
in future versions ofczech_sort.CompatibilityThe czech-sort library can be used with Python 2.6+ and 3.5+.Under Python 2, it only acceptsunicodestrings.InstallationInstall this into yourvirtualenvby running:$pipinstallczech-sortContributeBug reports and comments are welcomeat Github.Patches are also welcome! Source code is hosted at Github:$gitclonehttp://github.com/encukou/czech-sortTo run the included tests:$python-mpipinstall-e.[test]$python-mpytestIf you would like to contribute, but are confused by the above,
then please e-mail encukouatgmaildotcom.LicenseThe project is licensed under the MIT license. May it serve you well.Changelog1.1.0 (2023-07-11)Addbytes_key(Thanks to @honzajavorek!)Drop support for Python 21.0.1 (2021-08-30)Fix bug that prevented sorting strings that contain 'Ł' and/or 'Ø'.
(Thanks to @dark-light-cz for reporting and @jiri-one for the PR!)1.0.0 (2020-09-14)No code changes.
Since this has been stable for five years I decided to call it 1.0.Packaging improvementsTested with Python 2.7 and 3.5-3.90.4 (2015-09-05)First general release
Package: czelta
Czelta file loading and analysis librarydocumentation:czelta-python.readthedocs.ioCompilation requirement:C++11 compiler for use with C++ codeCython compiler and Python itself for use with Python codeExample Python code:import czelta

#init eventreader object
reader = czelta.event_reader()

#load data from file, usally downloaded from czelta website
reader.load("test.dat")

print("Events loaded: %i"%reader.number_of_events())

t_sum = 0
for event in reader:
    t_sum += sum(event.temps()[:2])/3

t_avg = t_sum/len(reader)
print("Average tempeature is %f *C"%t_avg)
Package: cz-emoticon
Emoticon czPlugin decommitizenel cual ya incorpora emojis en los tipos de cambios que realizamos, ademas de que parsea los codigos de JIRA y los issues.Instalacionpipinstallcz_emoticonConfiguracionDentro del archivo de configuracion del cz que se encuentra en la raiz de tu proyecto puedes agregar las siguientes configuracionesbump_message = "🔖 release[$new_version]:$current_version → $new_version"jira_prefix = "JIRA"jira_url = "https://ayigroup.atlassian.net"git_repo = ""project_name = "Data Lake"support_email = "support@ayi.group"bump_message: es obligatorio que este parametro este configurado tal cual como se muestra en este readmejira_prefix: es el codigo jira del proyecto el cual es necesario para identificarlo dentro del mensaje. Por ejemplo: PR es el identificador del proyecto al colocar dentro de nuestro footer PR-54 junto con el parametro jira_url generara la url de dicho issue.jira_url: es la url base de nuestro jira y es necesario junto con jira_prefix para poder generar las url de los issues de forma automaticagit_repo: es el repositorio de nuetro gitlab o github, permite generar la url de forma automatica asi los issues de esas plataformas, colocando la url el plugin identificara si es de gitlab o github. Por ejemplo: si colocamos en nuestro footer #34 el plugin automaticamente generara la url del issue #34 usando como base la url que colocamos en git_repo.project_name: es el nombre de nuestro proyecto, este estara disponible en el changelogesupport_email: el email de contacto de soporte de nuestra app, para que pueda ser visualizado en el changelog.Ejemplosgit cz

Seleccione el tipo de cambio que va a realizar: 
📝 docs: Cuando solo se modifica documentacion.

🚩 Cual es el alcance de este cambio? (nombre de clase o archivo): (es obligatorio colocar un scope):
init

✏️ Escriba un resumen breve e imperativo de los cambios en el codigo: (minusculas y sin punto):
Documentacion inicial del proyecto

📄 Proporcione informacion contextual adicional sobre los cambios de codigo: (pulse [intro] para omitir):
Se genero la documentacion inicial del proyecto con los standares a usar

🚨 Se trata de un CAMBIO IMPORTANTE? Relacionado con MAJOR en SemVer:
N

💬 Pie de pagina. Informacion sobre cambios de ultima hora y problemas de referencia que cierra esta confirmación: (pulse [enter] para saltar):
Ref: PR-123 #43

El commit generado sería:
📝 docs[init]: Documentacion inicial del proyecto (Ref: PR-123 #43)En el ejemplo agregamos tanto el codigo jira como el issue de nuestro git para que el plugin genere automaticamente las urls correspondientes.AutorJavier Baigorria (jdbaigorria@gmail.com)
Package: cz-github-convention
What is itcz-github-conventionis a plugin forcommitizenWhat it doCreate links to GitHub commits in the CHANGELOG.mdInstallationpipinstallcz-github-convention
czinitcz.json{"commitizen":{"name":"cz_github_convention","version":"0.0.1","tag_format":"v$version","github_repo":"superman/super-project"}}.pre-commit-config.yamlrepos:-repo:https://github.com/commitizen-tools/commitizenrev:v2.38.0hooks:-id:commitizenstages:[commit-msg]additional_dependencies:[cz-github-convention]
Package: cz-github-jira-conventional
cz-github-jira-conventionalcz-github-jira-conventionalis a plugin for thecommitizen tools, a toolset that helps you to createconventional commit messages. Since the structure of conventional commits messages is standardized they are machine readable and allow commitizen to automaticially calculate and tagsemantic version numbersas well as createCHANGELOG.mdfiles for your releases.This plugin extends the commitizen tools by:require a Jira issue idin the commit messagecreate links to GitHubcommits in the CHANGELOG.mdcreate links to Jiraissues in the CHANGELOG.mdWhen you call commitizencommityou will be required you to enter the scope of your commit as a Jira issue id (or multiple issue ids, prefixed or without prefix, see config below).> cz commit
? Select the type of change you are committing fix: A bug fix. Correlates with PATCH in SemVer
? JIRA issue number (multiple "42, 123"). XX-
...The changelog created by cz (cz bump --changelog)will contain links to the commits in Github and the Jira issues.## v1.0.0 (2021-08-06)### Features-**[XX-123](https://myproject.atlassian.net/browse/XX-123)**: create changelogs with links to issues and commits [a374b](https://github.com/apheris/cz-github-jira-conventional/commit/a374b93f39327964f5ab5290252b795647906008)-**[XX-42](https://myproject.atlassian.net/browse/XX-42),[XX-13](https://myproject.atlassian.net/browse/XX-13)**: allow multiple issue to be referenced in the commit [07ab0](https://github.com/apheris/cz-github-jira-conventional/commit/07ab0e09de36712ab1db93fff0c821ecd80b5849)InstallationInstall with pippython -m pip install cz-github-jira-conventionalYou need to use a cz config file that has therequiredadditional valuesjira_base_urlandgithub_repoand may contain theoptionalvaluejira_prefix.Example.cz.yamlconfig for this repositorycommitizen:name:cz_github_jira_conventionaltag_format:v$versionversion:1.0.0jira_prefix:XX-jira_base_url:https://myproject.atlassian.netgithub_repo:apheris/cz-github-jira-conventionalThejira_prefixcan be eitherempty (the user must write the prefix for each issue)a string (the prefix will be added automatically)a list (for multiple projects, the user will be asked to choose a prefix)jira_prefix:-XX--XY--YY-pre-commitAdd this plugin to the dependencies of your commit message linting withpre-commit.Example.pre-commit-config.yamlfile.repos:-repo:https://github.com/commitizen-tools/commitizenrev:v2.17.13hooks:-id:commitizenstages:[commit-msg]additional_dependencies:[cz-github-jira-conventional]Install the hook withpre-commitinstall--hook-typecommit-msgLicenseDistributed under the MIT License. SeeLICENSEfor more information.AcknowledgementsThis plugin would not have been possible without the fantastic work from:commitizen toolsconventional_JIRA
Package: cz-github-linear-conventional
cz-github-linear-conventionalcz-github-linear-conventionalis a plugin for thecommitizen tools, a toolset that helps you to createconventional commit messages. Since the structure of conventional commits messages is standardized they are machine readable and allow commitizen to automaticially calculate and tagsemantic version numbersas well as createCHANGELOG.mdfiles for your releases.This plugin extends the commitizen tools by:require a Linear issue idin the commit messagecreate links to GitHubcommits in the CHANGELOG.mdcreate links to Linearissues in the CHANGELOG.mdWhen you call commitizencommitthe scope is assumed from the current active branch. The Linear issue id should be available in the branch name for this. (See example below for automatically parsed issue id)> cz commit
? Select the type of change you are committing fix: A bug fix. Correlates with PATCH in SemVer
? Linear issue number: cae-123
...The changelog created by cz (cz bump --changelog)will contain links to the commits in Github and the Linear issues.## 1.1.0 (2022-02-15)### Feat-**[cae-62](https://linear.app/caesari/issue/cae-62)**: adding support for linear issue ids because it is nice [8adc3](https://github.com/ThimDeveloper/cz-github-linear-conventional/commit/8adc39bc0cb35fff07f5c9c4b906b1b3eefd3f56)InstallationInstall with pippython -m pip install cz-github-linear-conventionalYou need to use a cz config file that has therequiredadditional valueslinear_base_urlandgithub_repo. The scope or prefix for your linear issues will automatically be parsed from the current active branch and added to the commit message. This allows for automatic linking by the linear.app bot if that is set up for your linear project.Example.cz.yamlconfig for this repositorycommitizen:name:cz_github_linear_conventionaltag_format:$versionversion:1.0.0linear_base_url:https://linear.app/caesarigithub_repo:ThimDeveloper/cz-github-linear-conventionalpre-commitAdd this plugin to the dependencies of your commit message linting withpre-commit.Example.pre-commit-config.yamlfile.repos:-repo:https://github.com/commitizen-tools/commitizenrev:v2.17.13hooks:-id:commitizenstages:[commit-msg]additional_dependencies:[cz-github-linear-conventional]Install the hook withpre-commitinstall--hook-typecommit-msgLicenseDistributed under the MIT License. SeeLICENSEfor more information.AcknowledgementsThis plugin would not have been possible without the fantastic work from:commitizen toolsconventional_JIRAconventional_GITHUB_JIRA
Package: cz-git-repo-jira-conventional
cz-git-repo-jira-conventionalcz-git-repo-jira-conventionalis a plugin for thecommitizen tools, a toolset that helps you to createconventional commit messages. Since the structure of conventional commits messages is standardized they are machine readable and allow commitizen to automaticially calculate and tagsemantic version numbersas well as createCHANGELOG.mdfiles for your releases.This plugin extends the commitizen tools by:require a Jira issue idin the commit messagecreate links to Gitcommits in the CHANGELOG.mdcreate links to Jiraissues in the CHANGELOG.mdWhen you call commitizencommityou will be required you to enter the scope of your commit as a Jira issue id (or multiple issue ids, prefixed or without prefix, see config below).> cz commit
? Select the type of change you are committing fix: A bug fix. Correlates with PATCH in SemVer
? JIRA issue number (multiple "42, 123"). XX-
...The changelog created by cz (cz bump --changelog)will contain links to the commits in Github and the Jira issues.## v1.0.0 (2021-08-06)### Features-**[XX-123](https://myproject.atlassian.net/browse/XX-123)**: create changelogs with links to issues and commits [a374b](https://github.com/wisnerjr/cz-git-repo-jira-conventional/commit/a374b93f39327964f5ab5290252b795647906008)-**[XX-42](https://myproject.atlassian.net/browse/XX-42),[XX-13](https://myproject.atlassian.net/browse/XX-13)**: allow multiple issue to be referenced in the commit [07ab0](https://github.com/wisnerjr/cz-git-repo-jira-conventional/commit/07ab0e09de36712ab1db93fff0c821ecd80b5849)InstallationInstall with pippython -m pip install cz-git-repo-jira-conventionalYou need to use a cz config file that has therequiredadditional valuesjira_base_urlandgi_repoand may contain theoptionalvaluejira_prefixif you are only using one Jira project (then the prefix for this project will be added automatically).Example.cz.yamlconfig for this repositorycommitizen:name:cz_git_repo_jira_conventionaltag_format:v$versionversion:1.0.0jira_prefix:XX-jira_base_url:https://myproject.atlassian.netgithub_repo:https://github.com/wisnerjr/cz-git-repo-jira-conventionalpre-commitAdd this plugin to the dependencies of your commit message linting withpre-commit.Example.pre-commit-config.yamlfile.repos:-repo:https://github.com/commitizen-tools/commitizenrev:v2.17.13hooks:-id:commitizenstages:[commit-msg]additional_dependencies:[cz-git-repo-jira-conventional]Install the hook withpre-commitinstall--hook-typecommit-msgLicenseDistributed under the MIT License. SeeLICENSEfor more information.AcknowledgementsThis plugin would not have been possible without the fantastic work from:commitizen toolsconventional_JIRAgithub-jira-conventionalgit-jira-conventional