Saravanan666/pypi-org huggingface dataset:
Package: hata
HataA blazing fast Discord API wrapper that you can't denySupport Guild|Topical documentation|Examples|Technical documentation|SourceNew hata versions useDiscord API V10.AboutHata is anasynchronousDiscord APIwrapper built on top of scarletio.
It is designed to be easy to use, with also providing rich API offering everything what an advanced developer might
need.Named afterHata no Kokorofrom Touhou Project.Why hata?Multiple simultaneous clientsHata can run multiple clients from the same instance without sacrificing performance.PerformantFast concurrent code based on async/await paradigm with cache control, PyPy support and much more!Newest API featuresWhatever Discord decides to release/update/break Hata will support it natively in no time!100% PythonBuilt in Python! Easy to code, easy to read, easy to maintain.UsageSimple example implementing apingcommand.fromhataimportClient,Guild,wait_for_interruptionGUILD=Guild.precreate(guild_id)Seija=Client('TOKEN',extensions=['slash'])@Seija.eventsasyncdefready(client):print(f'{client:f}logged in.')@Seija.interactions(guild=GUILD)asyncdefping():"""ping-pong"""return'pong'Seija.start()wait_for_interruption()Hata leaves the main thread free,client.start()blocks it only till the client logs in (or fails it), although you
can still use thestart_clients()function, what as it says, starts up all the non-running clients parallelly.Sometimes leaving the main thread might cause problems when trying to shut down the bot(s). At this case, you might
want to usewait_for_interruption(), which disconnects the clients gracefully and closes the event loop on keyboard
interrupt.InstallationTo install Hata simply do# Linux/OS X$python3-mpipinstallhata# Windows$python-mpipinstallhata# Voice Support$python-mpipinstallhata[voice]And you are good to go! Hata has native pypy support as well if you need some more speed!DependenciesRequirementsPython >= 3.6chardet/cchardetOptionaldateutilPyNaCl(for voice support)Get in touchIf you have issues, suggestions, want to contribute, or just want to hang out, join our discord server.AcknowledgementsShout-Out to our brave testers who are helping the most to improve Hata!Koish[Feature requests]BrainDead[Documentation improvements]
Package: hat-aio
For more information see:online documentationgit repositoryRuntime requirementspython >=3.10Installhat-aiois available asPyPI project:$ pip install hat-aioBuildTo install editable installation, together with python development
dependencies, run:$ pip install -e '.[dev]'To install only python development dependencies, run:$ pip install -r requirements.pip.txtBuild tool used forhat-aioispydoit. For listing available doit tasks,
use:$ doit listDefault task:$ doitcreates wheel package insidebuilddirectory.Hat Openhat-aiois part ofHat Openproject - open-source framework of tools
and libraries for developing applications used for remote monitoring, control
and management of intelligent electronic devices such as IoT devices, PLCs,
industrial automation or home automation systems.Development of Hat Open and associated repositories is sponsored byKončar Digital.LicenseCopyright 2020-2023 Hat Open AUTHORSLicensed 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: hatanaka
HatanakaEffortless compression / decompression of RINEX files in Python and on the command line.Supports all compression formats allowed by the RINEX 2, 3 and 4 standards:Hatanaka compression for Observation Data Files,LZW (.Z), gzip (.gz), bzip2 (.bz2) and .zip.Quick StartInstallationWheels are available from PyPI for Linux, MacOS and Windows. Python versions 3.6 and up are supported.pipinstallhatanakaTo ensure that everything is working as expected, it is recommended to also run the included tests.pipinstallpytest
pytest--pyargshatanakaPythonimporthatanakafrompathlibimportPath# decompressionrinex_data=hatanaka.decompress('1lsu0010.21d.Z')# orrinex_data=hatanaka.decompress(Path('1lsu0010.21d.Z').read_bytes())# or, creates '1lsu0010.21o' directly on diskhatanaka.decompress_on_disk('1lsu0010.21d.Z')# compressionPath('1lsu0010.21d.gz').write_bytes(hatanaka.compress(rinex_data))# orPath('1lsu0010.21d.gz').write_bytes(hatanaka.compress('1lsu0010.21o'))# or, creates '1lsu0010.21d.gz' directly on diskhatanaka.compress_on_disk('1lsu0010.21o')Any errors during Hatanaka compression/decompression will be raised as aHatanakaExceptionand any non-critical
problems reported as warnings.These functions are idempotent – already decompressed / compressed data is returned as is.CLIThe same functionality is also made available from the command line viarinex-decompressandrinex-compress.Simply provide a list of RINEX files to compress or decompress. stdin-stdout is used if no files are specified.To remove the original files after conversion, add-d/--delete. The input file is removed only if conversion
succeeds without any errors or warnings.# creates 1lsu0010.21orinex-decompress1lsu0010.21d.Z# creates 1lsu0010.21d.gzrinex-compress1lsu0010.21o# stdin-stdout examplerinex-decompress<1lsu0010.21d.Z|grep'SYS / # / OBS TYPES'Additionally, the originalrnx2crxandcrx2rnxexecutables are also installed for other tools that might want to make use of them, such as RTKLIB.DevelopmentBuilding from sourceInstalling from source code is also an option, in which case the RNXCMP tools will be built in the process. This assumes
a C compiler is available and is usually picked up automatically by Python'ssetuptools. If that is not the case, you
can instead provide a path to one by setting theCCenvironment variable.pipinstallgit+https://github.com/valgur/hatanakaChangesSeeCHANGELOG.md.AttributionMartin Valgur – this Python library.RNXCMP softwarefor Hatanaka compression support:Hatanaka, Y. (2008), A Compression Format and Tools for GNSS Observation Data, Bulletin of the Geospatioal Information
Authority of Japan, 55, 21-30.
(available athttps://www.gsi.go.jp/ENGLISH/Bulletin55.html)LicenseThis library is provided under the MIT license. Additional license terms apply for the included RNXCMP software –
seeLICENSE.
Package: hat-asn1
For more information see:online documentationgit repositoryRuntime requirementspython >=3.10Installhat-asn1is available asPyPI project:$ pip install hat-asn1BuildBuild tool used forhat-asn1ispydoit. It can be installed together
with other python dependencies by running:$ pip install -r requirements.pip.dev.txtFor listing available doit tasks, use:$ doit listDefault task:$ doitcreates wheel package insidebuilddirectory.Hat Openhat-asn1is part ofHat Openproject - open-source framework of tools
and libraries for developing applications used for remote monitoring, control
and management of intelligent electronic devices such as IoT devices, PLCs,
industrial automation or home automation systems.Development of Hat Open and associated repositories is sponsored byKončar Digital.LicenseCopyright 2020-2023 Hat Open AUTHORSLicensed 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: hatch
HatchCI/CDDocsPackageMetaHatch is a modern, extensible Python project manager.FeaturesStandardizedbuild systemwith reproducible builds by defaultRobustenvironment managementwith support for custom scriptsConfigurablePython distribution managementStatic analysiswith sane defaultsEasypublishingto PyPI or other indexesVersionmanagementBest practiceproject generationResponsiveCLI, ~2-3xfasterthan equivalent toolsSee theWhy Hatch?page for more information.DocumentationThedocumentationis made withMaterial for MkDocsand is hosted byGitHub Pages.LicenseHatch is distributed under the terms of theMITlicense.
Package: hat-chatter
For more information see:online documentationgit repositoryInstallhat-chatterpython library is available asPyPI project:$ pip install hat-chatterBuildBuild tool used forhat-chatterispydoit. It can be installed together
with other python dependencies by running:$ pip install -r requirements.pip.dev.txtFor listing available doit tasks, use:$ doit listDefault task:$ doitcreates wheel package insidebuilddirectory.Hat Openhat-chatteris part ofHat Openproject - open-source framework of tools
and libraries for developing applications used for remote monitoring, control
and management of intelligent electronic devices such as IoT devices, PLCs,
industrial automation or home automation systems.Development of Hat Open and associated repositories is sponsored byKončar Digital.LicenseCopyright 2020-2023 Hat Open AUTHORSLicensed 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: hatch-autorun
hatch-autorunCI/CDPackageMetaThis provides abuild hookplugin forHatchthat injects code into an installation that will automatically run before the first import.Table of ContentsConfigurationFileCodeTemplateConditional executionLicenseConfigurationThebuild hook pluginname isautorun.pyproject.toml[tool.hatch.build.targets.wheel.hooks.autorun]dependencies=["hatch-autorun"]hatch.toml[build.targets.wheel.hooks.autorun]dependencies=["hatch-autorun"]FileYou can select a relative path to a file containing the code with thefileoption:[tool.hatch.build.targets.wheel.hooks.autorun]file="resources/code.emded"CodeYou can define the code itself with thecodeoption:[tool.hatch.build.targets.wheel.hooks.autorun]code="""print('Starting coverage collection')coverage.process_startup()"""TemplateThe current implementation uses a.pthfile to execute the code. As a result, any required imports must be defined there on one line rather than in the code itself.You can set the.pthfile template with thetemplateoption, which will be formatted with acodevariable representing thecodeoption or the contents of the file defined by thefileoption. The following shows the default template:[tool.hatch.build.targets.wheel.hooks.autorun]template="import os, sys;exec({code!r})"Conditional executionSometimes you'll only want builds to induce auto-run behavior when installed under certain circumstances, like for tests. In such cases, set theenable-by-defaultoptiontofalse:[tool.hatch.build.targets.wheel.hooks.autorun]enable-by-default=falseThen when the desired build conditions are met, set theHATCH_BUILD_HOOK_ENABLE_AUTORUNenvironment variabletotrueor1.Licensehatch-autorunis distributed under the terms of theMITlicense.
Package: hatch-aws
hatch-awsAWS builder plugin forHatch 🥚🐍.Hatch is modern, extensible Python project manager.Checkout my other pluginhatch-aws-publisher.Table of Contentshatch-awsTable of ContentsGlobal dependencyBuilderHow to use itOptionsLicenseGlobal dependencyAddhatch-awswithin thebuild-system.requiresfield in yourpyproject.tomlfile.[build-system]requires=["hatchling","hatch-aws"]build-backend="hatchling.build"BuilderThebuilder pluginname is calledaws.To start build process, runhatch build -t aws:❯hatchbuild-taws[aws]Buildinglambdafunctions...
MyAwsLambdaFunc...success
Buildsuccessfull🚀
/path/to/build/.aws-sam/buildHow to use itPut your module and lambdas inside ofsrcfolder..
├──pyproject.toml
├──src
│└──my_app
│├──__init__.py
│├──common
││├──__init__.py
││├──config.py
││└──models.py
│└──lambdas
│├──lambda1
││├──__init__.py
││└──main.py
│└──lambda2
│├──__init__.py
│└──main.py
└──template.ymlSpecify common requirements for your project inpyproject.tomlas dependencies.[project]dependencies=["boto3"]Specify requirements for your lambda functions inpyproject.tomlas optional dependencies. Use resource name from SAM template, but you have to adapt it to be compliant withPEP standard(transform to lower case and replace_with-). For example, if you function name in SAM template isGetAll_Accounts, usegetall-accounts.[project.optional-dependencies]lambda1=["pyaml"]lambda2=["request","pydantic"]Specify additional paths(source/destination) you want to copy to the build folder. Destination is relative to a build directory (.aws-sam/buildby default). You can use glob*to copy common to all lambda functions.[tool.hatch.build.force-include]"src/batman/common"="*/batman/common"# copy to all lambda functions".editorconfig"=".editorconfig.txt""CHANGELOG.md"="../CH.txt""images/"="*/images"Set theCodeUriandHandlerparameter pointing to your lambdas in SAM template. Only resources withRuntime: python{version}are supported. The rest is ignored.Resources:Lambda1:Type:AWS::Serverless::FunctionProperties:Runtime:python3.9FunctionName:lambda1-functionCodeUri:srcHandler:my_app.lambdas.lambda1.main.app...Lambda2:Type:AWS::Serverless::FunctionProperties:Runtime:python3.9FunctionName:lambda2-functionCodeUri:srcHandler:my_app.lambdas.lambda2.main.app...OptionsFollowing table contains available customization of builder behavior. You can find example ofpyproject.tomlintests/assets/pyproject.toml.OptionTypeDefaultDescriptiontemplatestrtemplate.ymlSAM template filename.use-samboolfalseUse onlysam buildcommand without any custom actions.sam-execstrsamPath tosamexecutable. Env var:HATCH_SAM_EXEC.sam-paramsarrayAdditionalsam buildargs.LicensePluginhatch-awsis distributed under the terms of theMITlicense.
Package: hatch-aws-publisher
hatch-aws-publisherAWS publisher plugin forHatch 🥚🐍.Hatch is modern, extensible Python project manager.Table of Contentshatch-aws-publisherTable of ContentsHow to enableHow to use itOptionssectiontool.hatch.publish.awssectiontool.hatch.publish.aws.samsectiontool.hatch.publish.aws.sam.env.<env-name>LicenseHow to enablePlugin must be installed in the same environment asHatchitself.python-mvenv.venv
.venv/bin/pipinstallhatch-aws-publisherHow to use itThepublisher pluginname is calledaws.Build you app withSAM. You can use my Hatch pluginhatch-aws.Put your SAM config topyproject.toml(stack name is by default name of your project):[project]name="my-app"[tool.hatch.publish.aws.sam]region="us-west-1"confirm_changeset=falsefail_on_empty_changeset=falseforce_upload=truecapabilities="CAPABILITY_IAM"s3_bucket="my-bucket"parameter_overrides=["stage=dev"][tool.hatch.publish.aws.sam.tags]job="batman"name="bruce"Publish (deploy) your app.hatchpublish-pawsOptionssectiontool.hatch.publish.awsThis section allows to modify behavior of the plugin. Available options:[tool.hatch.publish.aws]stack_name_append_env=truestack_name_prefix="super-"stack_name_suffix="-man"deploy=trueAll above options can be overwritten using a CLI parameter.venv/hatch/bin/hatchpublish-paws-ostack_name_prefix="bat-"stack_name_prefix: adds a prefix to a stack name ->bat-my-appstack_name_suffix: adds a suffix to a stack name ->bat-my-app-manstack_name_append_env: adds a selected environment to a stack name ->bat-my-app-man-devdeploy: if it'sfalse, only sam config will be generated, butsam deploywill not be executedsectiontool.hatch.publish.aws.samDefault values for SAM. You can use any key:value pair available inSAM config.Only difference is format of tags (they use separate section):[tool.hatch.publish.aws.sam.tags]job="batman"name="bruce"sectiontool.hatch.publish.aws.sam.env.<env-name>You can define specific deployment environments. They inherit values fromtool.hatch.publish.aws.sam.Environment settings inpyproject.toml:[tool.hatch.publish.aws.sam]region="us-west-1"confirm_changeset=falsefail_on_empty_changeset=falseforce_upload=truecapabilities="CAPABILITY_IAM"[tool.hatch.publish.aws.sam.env.dev]region="us-west-2"s3_bucket="dev-bucket"parameter_overrides=["stage=dev"][tool.hatch.publish.aws.sam.env.prd]s3_bucket="prd-bucket"parameter_overrides=["stage=prd"]fail_on_empty_changeset=trueYou need to specify an environment using a CLI parameter:hatchpublish-paws-oenv=devLicensePluginhatch-aws-publisheris distributed under the terms of theMITlicense.
Package: hatch-build-scripts
Hatch Build ScriptsA plugin forHatchthat allows you to run arbitrary
build scripts and include their artifacts in your package distributions.InstallationTo set uphatch-build-scriptsfor your project you'll need to configure it in your
project'spyproject.tomlfile as abuild-systemrequirement:[build-system]requires=["hatchling","hatch-build-scripts"]build-backend="hatchling.build"UsageNow you'll need to configure the build scripts you want to run. This is done by adding
an array of scripts to thetool.hatch.build.hooks.build-scripts.scriptskey in yourpyproject.tomlfile. Each script is configured with the following keys:KeyDefaultDescriptioncommandsrequiredAn array of commands to run. Each command is run in a separate shell.artifactsrequiredAn array of artifact patterns (same as.gitignore) to include in your package distributions.out_dir"."The directory to copy artifacts into.work_dir"."The directory to run the commands in. All artifact patterns are relative to this directory.clean_artifactstrueWhether to clean files from theout_dirthat match the artifact patterns before running the commands.clean_out_dirfalseWhether to clean theout_dirbefore running the commands.In practice this looks like:[[tool.hatch.build.hooks.build-scripts.scripts]]out_dir="out"commands=["echo 'Hello, world!' > hello.txt","echo 'Goodbye, world!' > goodbye.txt",]artifacts=["hello.txt","goodbye.txt",][[tool.hatch.build.hooks.build-scripts.scripts]]# you can add more scripts here...You can configure script defaults for scripts by adding a[tool.hatch.build.hooks.build-scripts]table to yourpyproject.tomlfile. The following keys are supported:KeyDefaultDescriptionout_dir"."The directory to copy artifacts into.work_dir"."The directory to run the commands in. All artifact patterns are relative to this directory.clean_artifactstrueWhether to clean files from theout_dirthat match the artifact patterns before running the commands.clean_out_dirfalseWhether to clean theout_dirbefore running the commands.
Package: hatch-ci
hatch-ciThis is ahatch-vcsheavily inspired pluging, managing the
version information for a python wheel package.It gets version information from:version-fileentry in the tool.hatch.version toml entry (eg. 1.0.0) in the master branchaugments it with abNNNbuild number in creating the package foobar-1.0.0bNNNN (this can be sent toPyPi)if there's a tag v1.0.0 on the repo, it will build foobar-1.0.0 release (this can be sent toPyPi)The last two steps are mean to be managed in a CI/CD system (github at the moment), to ensurehands-offreleases.In essence this pluging:manages the version informationallows version replacement in text files using build informationNOTE: this is heavily inspired fromhatch-vcsTable of ContentsGlobal dependencyVersion sourceVersion source optionsLicenseGlobal dependencyEnsurehatch-ciis defined within thebuild-system.requiresfield in yourpyproject.tomlfile.[build-system]requires=["hatchling","hatch-ci"]build-backend="hatchling.build"Version sourceTheversion source pluginname isci.This will enable the hatch-ci pluging:pyproject.toml[project]..dynamic=["version"]# this rerieves the version dynamically..Version source optionspyproject.toml[tool.hatch.version]source="ci"# this pulls the version using the hatch-ci hook# this will put/update __version__ and __hash__ info in version-fileversion-file="src/hatch_ci/__init__.py"# these files will be jinja2 processed, the environment will# contains variables as: branch, build, current, ref, runid,# sha, version, workflow etc.paths=["README.md"]# the listed paths will undergo replacement before jinja2 processing and# the strings 'a' & 'b' wil be replacedfixers=[{'a':'{ctx.workflows}'},{'d':'{ctx.branch}'}]OptionTypeDefaultDescriptionversion-filestrNoneA file where to writeversion/hashvariablespaths`list[str]str`Nonefixerslist[dict[str,str]]NoneA list of dict, each key is a string to replace with the valueLicensehatch-ciis distributed under the terms of theMITlicense.
Package: hatch-conda
hatch-condaCI/CDPackageMetaThis provides a plugin forHatchthat allows the use of condaenvironments.This project is a copied and modified version of thehatch-containersplugin by Ofek Lev.Table of ContentsInstallationConfigurationPythonCommandConda-forgeEnvironment fileNotesLicenseInstallationpip install hatch-condaConfigurationTheenvironment pluginname isconda.pyproject.toml[tool.hatch.envs.<ENV_NAME>]type="conda"hatch.toml[envs.<ENV_NAME>]type="conda"PythonIf thePython versionis set to a multi-character integer like310then it will be interpreted as its<MAJOR>.<MINOR>form e.g.3.10.If not set, then the<MAJOR>.<MINOR>version of the firstpythonfound along yourPATHwill be used, defaulting to the Python executable Hatch is running on.CommandThecommandoption specifies the command that will be used to setup the environment. The possible options areconda,mambaandmicromamba.Default:[envs.<ENV_NAME>]command="conda"Conda-forgeIndicates if the conda-forge index should be used.Default:[envs.<ENV_NAME>]conda-forge=trueEnvironment fileBy default packages will be installed using pip. However, to install packages using conda, conda-forge, or any other channel, you can specify a conda environment file:[envs.<ENV_NAME>]environment-file="environment.yml"When using an environment file, the channel and python version specified in the environment file will be used. After installing the environment, any extra packages specified in the dependencies will be installed, as well as the local package.Prefix environmentsIt's possible to identify environment py prefix (the path in the filesytem) rather than by name.[envs.<ENV_NAME>]prefix=.venv/Will create a conda environment in the.venv/folder. This is useful because a text editor might check for this location to use the virtual environment.NotesThere must be aconda,mamba, ormicromambaexecutable along yourPATH.Theenv-excludeenvironment variable filterhas no effect.Licensehatch-condais distributed under the terms of theMITlicense.
Package: hatch-conda-build
hatch-conda-buildConda package builder forHatch. Hatch is modern, extensible Python project manager.UsageAddhatch-conda-buildwithin the build-system.requires field in your pyproject.toml file.[build-system]requires=["hatchling","hatch-conda-build"]build-backend="hatchling.build"Additionallyconda-buildmust be in your current path when running a
hatch build.OptionsAdditional builder configuration can be set in the following toml
header.[tool.hatch.build.targets.conda]...Following table contains available customization of builder behavior.OptionTypeDefaultDescriptionchannelslist[str]['conda-forge']Channels used for package build and testingdefault_numpy_versionstr"1.22"Default numpy version for buildBuilding Conda PackageThebuilder pluginname is calledconda.To start build process, runhatch build -t conda:$hatchbuild-tconda[conda]...LicensePlugin hatch-conda-build is distributed under the terms of theMITlicense.