Saravanan666/pypi-org huggingface dataset:
Package: allurlstatus
pypi package for checking all url statususage:python
>>> import allurlstatus
>>> allurlstatus.getStatus( [ “https://www.google.com”, “http://someExampleNonExistingUrl”, “etc - but this should be in valid url format” ] )bash
$ getallurlstatus < file_with_url_list.txtprojectUrl:https://github.com/jogind3r/allurlstatus
Package: allusgov
OverviewThis project attempts to map the organization of the US Federal Government by gathering and consolidating information from various directories.Current sources:SAM.gov Federal Hierarchy Public APIFederal Register Agencies APIUSA.gov A-Z Index of U.S. Government Departments and AgenciesOPM Federal Agencies ListCISA .gov dataFY 2024 Federal Budget OutlaysUSASpending API Agencies & Sub-agenciesEach source is scraped (seeoutdirectory) in raw JSON format, including fields for the organizational unit name/parent (if any), unique ID/parent-ID fields (if the names are not unique) as well as any other attribute data for that organization available from that source.A normalized name (still WIP) is then added, which corrects letter case, spacing and expands acronyms. Acronyms are selected and verified manually using data fromUSCD GovSpeakand theDOD Dictionary of Military and Associated Termsas well as manual entry when needed.Each source is them imported into a tree and exported into the following formats for easy consumption:Plain text treeJSON flat format (with path to each element)JSON nested tree formatCSV format (with embedded JSON attributes)Wide CSV format (with flattened attributes)DOT file(does not include attributes)GEXF graph file(includes flattened attributes)GraphQL graph file(includes flattened attributes)Cytoscape.js JSON format(includes flattened attributes)To merge the lists, each tree is merged into a selected base tree by comparing the normalized names of each node in the tree to the names of each node in the base tree using a fuzzy matching algorithm. Similarity scores between each pair of parents are incorporated into the score to more correctly identify cases where the same/similar office or program name is used for different organizations.Note that the fuzzy matching is imperfect and may have some inaccurate mappings (although most appear OK) and will certainly have some entries which actually should be merged, but aren't.The final merged dataset is written in the above formats to thedata/mergeddirectory.SetupRequirementsPython 3.10+PoetryInstallationCheck out this repository, then from the repository root, install dependencies:$ poetry installSee command line usage:poetry run allusgov --helpRun a complete scrape and merge:poetry run allusgov
Package: alluvium
alluvium - interactive bindings visualizer for i3alluvium guides you through your keybindings and modes in i3 as you enter them. It is
heavily inspired byremontoireand reuses
its comment syntax in thei3/configfile to learn about keybindings, modes and their
description.Default overlayAfter entering Settings modeAfter entering Session modeUsageInstall alluvium, for example viapip install alluvium, and run it manually. It will
connect to i3 and show your bindings - if you put remontoire annotations into your config.To use alluvium in i3, ensure that thealluviumexecutable is callable by i3. So if you
installed it in pyenv, you might need to put a symlink to$(pyenv which alluvium)into
your.local/bin, so that i3 can find the executable without knowing about pyenv.## Launch // Toggle alluvium // <> ? ##
bindsym $mod+Shift+question $run alluvium --toggle

## Settings // Enter Settings Mode // <> F11 ##
mode "Settings" {
    ## Settings // Control Center // c ##
    bindsym c exec gnome-control-center; mode "default"

    ## Settings // Display // d ##
    bindsym d exec gnome-control-center display; mode "default"

    ## Settings // Wifi // w ##
    bindsym w exec gnome-control-center wifi; mode "default"

    ## Settings // Bluetooth // b ##
    bindsym b exec gnome-control-center bluetooth; mode "default"

    ## Settings // Exit Settings Mode // Escape or <Ctrl> g ##
    bindsym Escape mode "default"
    bindsym Ctrl+g mode "default"
}
bindsym $mod+F11 mode "Settings"; $run alluvium --mode Settings --quit-on-defaultThe first binding toggles the overlay while the binding to$mod+F11enters the settings
mode with an overlay showing the bindings available in that mode.--quit-on-defaultmakes the overlay disappear when you return to default mode. This is most helpful for
rarely used modes such as system settings as above or a mode to manage i3 itself.SyntaxThe config syntax is the same as in remontoire, that is## <Group> // <Label> // <Keys> ##with an extension to define modes. If a group contains a binding with a label ofEnter ... Mode, alluvium recognizes the group as a mode. The enter binding shows up in theModesgroup in the top level display while the other bindings of the group are shown
when you enter the mode.
Package: allways
allwaysAutomatically update__all__statements.InstallationpipinstallallwaysCommand line interfaceallways<file1.py><file2.py>...As a pre-commit hookSeepre-commitfor instructions.Sample.pre-commit-config.yaml-repo:https://github.com/tjsmart/allwaysrev:v0.0.2hooks:-id:allwaysNote: by default the pre-commit hook will run only against__init__.pyfiles.What does it do?Add__all__statements to your python filesfrom._fooimportbarfrom._ximportyaszdeffoo():...becomesfrom._fooimportbarfrom._ximportyaszdeffoo():...# allways: start__all__=["bar","foo","z",]# allways: endIgnore private variablesfrom.import_foofrom.importbarbecomesfrom.import_foofrom.importbar# allways: start__all__=["bar",]# allways: endUpdate pre-existing__all__statementsfrom.importbarfrom.importbaz# allways: start__all__=["bar","foo",]# allways: endbecomesfrom.importbarfrom.importbaz# allways: start__all__=["bar","baz",]# allways: endWhy?the problemI choose to organize python libraries with:PEP 561complianceprivate module files, public (sub-)package  foldersusing__init__.pyto define the public interface of a (sub-)packageFor example, I might layout my project as such:pkg/
├── bar/
│   ├── _bar.py
│   └── __init__.py
├── _foo.py
├── __init__.py
└── py.typedContained in the filespkg/_foo.pyandpkg/bar/_bar.pythere will be some portion that I would like to expose publicly viapkg/__init__.pyandpkg/bar/__init__.py, respectively.For example, perhaps I would like to expose a functiondo_somethingfrom the module filepkg/_foo.pyby adding the following line topkg/__init__.py:from._fooimportdo_somethingAnd here is where the problem arises!(Iknow... a lot of setup...)When a user of our package turns to usedo_somethingthey will be slapped on the wrist by the type-checker.pyrightoutput:t.py:1:18 - error: "do_something" is not exported from module "pkg"
Import from "pkg._foo" instead (reportPrivateImportUsage)mypy --strictoutput:t.py:1: error: Module "pkg" does not explicitly export attribute "do_something"  [attr-defined]And if you aren't concerned that users will have to ignore this type error, know that it get's worse! Language servers will not display any hint that the objectpkg.do_somethingexists. 😱For small projects maintaining this by hand is no big deal. But for large projects with several contributors this becomes a complete wast of time! 😠the solutionAccording topyright documentation, a typed library can choose to explicitly re-export symbols by adding it to the__all__of the corresponding module.allwaysmission is to automate the process of updating__all__statements in__init__.pyfiles. 🤗but alsoMy personal goal here is to contribute something to open source and write some more rust! 🦀
Package: allwhatspy-awp
AllWhatsPy: Automatize o WhatsApp com FacilidadeO AllWhatsPy Ã© uma biblioteca Python revolucionÃ¡ria que oferece um controle sem precedentes sobre o WhatsApp. Seja para fins profissionais ou pessoais, essa ferramenta versÃ¡til e poderosa foi projetada para otimizar sua experiÃªncia de automaÃ§Ã£o no aplicativo de mensagens mais popular do mundo.Por que AllWhatsPy? Ã€ medida que nossa dependÃªncia do WhatsApp se torna incontestÃ¡vel, surge a necessidade de aprimorar a maneira como utilizamos essa ferramenta essencial. O AllWhatsPy Ã© a resposta a essa demanda crescente. Inspirado por projetos notÃ¡veis como o PyWhatsapp e o PyWhatKit, o AllWhatsPy Ã© o resultado de uma jornada de exploraÃ§Ã£o e pesquisa profunda em bots e APIs do WhatsApp.O desenvolvimento do AllWhatsPy envolveu milhares de linhas de cÃ³digo e testes meticulosos para garantir um desempenho perfeito. O resultado? Uma biblioteca versÃ¡til e flexÃ­vel que permite que vocÃª faÃ§a praticamente qualquer coisa no WhatsApp, proporcionando um novo nÃ­vel de eficiÃªncia e automaÃ§Ã£o.Principais Recursos:Criptografia de Mensagens:Proteja suas mensagens com a clÃ¡ssica criptografia de Cifra de Caesar, garantindo que apenas os destinatÃ¡rios certos possam lÃª-las.
Cifra de VigenÃ¨re: Aumente a seguranÃ§a de suas comunicaÃ§Ãµes com a sofisticada criptografia de Cifra de VigenÃ¨re.Envio de Mensagens:Envio de Mensagens com 4 meios diferentes de realizaÃ§Ã£o. Cada uma delas com seu foco especÃ­fico.AnÃ¡lise de Mensagens:AnÃ¡lise de Mensagens Recebidas: Obtenha insights valiosos a partir da anÃ¡lise de mensagens recebidas, facilitando o entendimento do conteÃºdo.AgendamentosAgendamento de Tarefas: Programe mensagens e aÃ§Ãµes para serem executadas em horÃ¡rios especÃ­ficos, aumentando a eficiÃªncia de suas comunicaÃ§Ãµes.ContatosGerenciamento de Contatos: Controle seus contatos com facilidade, localize usuÃ¡rios, arquive conversas e marque mensagens como nÃ£o lidas.Flexibilidade e PersonalizaÃ§Ã£o: O AllWhatsPy oferece diversas opÃ§Ãµes de configuraÃ§Ã£o para atender Ã s suas necessidades especÃ­ficas, desde a geraÃ§Ã£o de JSON atÃ© a geraÃ§Ã£o de logs detalhados.Quer saber mais?Acesse meu GitHubpara explorar todas as possibilidades que o AllWhatsPy oferece. Automatize suas interaÃ§Ãµes no WhatsApp e leve a eficiÃªncia da automaÃ§Ã£o para um novo nÃ­vel!
Package: allwhois
All WhoisA Python package for retrieving WHOIS information of domains.Description/FeaturesPython wrapper for Linux "whois" commandGetparsed&rawWHOIS data for a given domainExtract data foranyTLD.No TLD regex'sDate's asdatetime objectsorstringsCaching of resultsRequirementsPython 3.6+Support for python 3.6+ only. Works onmacos&linuxonlyIssuesIf there is something that is not parsing well, open a issue, and i will look into it.
Or if you fixed it, do make a pull request, and i can merge it.InstallationpipinstallallwhoisPre-requisite installationmacOSbrewinstallwhoisLinuxaptinstallwhoisUsageimportsysfromallwhoisimportwhoisfrompprintimportpprintif__name__=="__main__":domain=Nonetry:domain=sys.argv[1]except:exit(f"Usage:{sys.argv[0]}<domain_name>")response=whois.query(domain)pprint(response)Authors:Sriram:marirs
Package: allya.nestedconfigparser
By default, configparser only loads values from ‘vars’, ‘section’, and then ‘default_section’. This extension allows for nested sections by use of a section splitter (default ‘.’) and attempts to find values from ‘vars’, then ‘section’, then its logical parents, and finally ‘default_section’.For example, given the configuration below:[DEFAULT]
alpha=first level

[section]
beta=second level

[section.subsection]
gamma=third levelthe default configparser would behave like:>>> settings = configparser.ConfigParser()
>>> settings.read('config.ini')
['config.ini']
>>> settings.get('section.subsection', 'alpha')
first level
>>> settings.get('section.subsection', 'beta')
None
>>> settings.get('section.subsection', 'gamma')
third levelInstead, in this extension, the behaviour would be:>>> settings = nestedconfigparser.NestedConfigParser()
>>> settings.read('config.ini')
['config.ini']
>>> settings.get('section.subsection', 'alpha')
first level
>>> settings.get('section.subsection', 'beta')
second level
>>> settings.get('section.subsection', 'gamma')
third levelThis extensions supports theoretically unlimited levels of nesting. It also does not require each level of the subsection to exist for the case where a section has no additional configurations.Note: this extension intentionally does not raise a NoSectionError if a section does not exist when using ‘nestedconfigparser.NestedConfigParser().get(section, option)’. This is because it will attempt to fallback to higher sections and avoids potentially empty sections that don’t have any added configurations at the highest subsection.
Package: allyourbase
All Your Base is a python library for converting number strings from any base to number strings of any other base.This library was created to make the following improvements on existing base conversion libraries out there:Can convert both integers and floatsUses Decimal package to allow for arbitrary precision / number of digitsUses Decimal package to avoid binary rounding errorsIs not limited to base 36, 62, 64 due to available characters. Can convert to/from any integer base from 2 to whatever you like. (higher bases use delimited decimal format)
Package: alma-cdk.aws-interface-endpoints
npmi-D@alma-cdk/aws-interface-endpointsL3 construct helping with PrivateLink-powered VPC Interface Endpoints for AWS Services.🚧   Project StabilityThis construct is still versioned withv0major version and breaking changes might be introduced if necessary (without a major version bump), though we aim to keep the API as stable as possible (even withinv0development). We aim to publishv1.0.0soon and after that breaking changes will be introduced via major version bumps.Getting StartedEndpoint open to whole isolated subnetimport{AwsInterfaceEndpoints}from'@alma-cdk/aws-interface-endpoints';import*asec2from'aws-cdk-lib/aws-ec2';constvpc=newec2.Vpc();newAwsInterfaceEndpoints(this,'EcrInterfaceEndpoint',{vpc,services:[{id:'EcrDocker',ec2.InterfaceVpcEndpointAwsService.ECR_DOCKER},],});Session Manager connection endpointsimport{AwsInterfaceEndpoints}from'@alma-cdk/aws-interface-endpoints';import*asec2from'aws-cdk-lib/aws-ec2';constvpc=newec2.Vpc();newAwsInterfaceEndpoints(this,'SessionManagerInterfaceEndpoint',{vpc,services:AwsInterfaceEndpoints.SessionManagerConnect,});Explictly opened endpointsIn your VPC creation stackimport{AwsInterfaceEndpoints}from'@alma-cdk/aws-interface-endpoints';import*asec2from'aws-cdk-lib/aws-ec2';constvpc=newec2.Vpc();newAwsInterfaceEndpoints(this,'EcrInterfaceEndpoint',{vpc,open:false,services:[{id:'EcrDocker',ec2.InterfaceVpcEndpointAwsService.ECR_DOCKER},],});In some other stack (maybe on a completely different CDK application):import{AwsInterfaceEndpoints}from'@alma-cdk/aws-interface-endpoints';import*asec2from'aws-cdk-lib/aws-ec2';defineinstance:ec2.Instance;constendpoints=AwsInterfaceEndpoints.fromAttributes(this,'EcrInterfaceEndpoint',{services:[{id:'EcrDocker',ec2.InterfaceVpcEndpointAwsService.ECR_DOCKER},],});endpoints.allowDefaultPromFrom(instance);https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-create-vpc.htmlhttps://aws.amazon.com/privatelink/pricing/https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html
Package: alma-cdk.cross-region-parameter
npmi-D@alma-cdk/cross-region-parameterStoreAWS SSM Parameter StoreParameters into another AWS Region with AWS CDK.🚧   Project StabilityThis construct is still versioned withv0major version and breaking changes might be introduced if necessary (without a major version bump), though we aim to keep the API as stable as possible (even withinv0development). We aim to publishv1.0.0soon and after that breaking changes will be introduced via major version bumps.Getting Startedimport{CrossRegionParameter}from"@alma-cdk/cross-region-parameter";newCrossRegionParameter(this,'SayHiToSweden',{region:'eu-north-1',name:'/parameter/path/message',description:'Some message for the Swedes',value:'Hej då!',});
Package: alma-cdk.domain
npmi-D@alma-cdk/domainSimplifies creation of subdomain with a TLS certificate and configuration with services like AWS CloudFront.🚧   Project StabilityThis construct is still versioned withv0major version and breaking changes might be introduced if necessary (without a major version bump), though we aim to keep the API as stable as possible (even withinv0development). We aim to publishv1.0.0soon and after that breaking changes will be introduced via major version bumps.Getting Startedimport{Domain}from'@alma-cdk/domain';import*ascloudfrontfrom'aws-cdk-lib/aws-cloudfront';constdomain=newDomain(this,'Domain',{zone:'example.com',//retrievethezonevialookup,orprovideIHostedZonesubdomain:'foobar',//optionalsubdomain});constdistribution=newcloudfront.Distribution(this,'Distribution',{/*othercloudfrontconfigurationvaluesremovedforbrevity*/certificate:domain.certificate,//referencetocreatedICertificatedomainNames:[domain.fqdn],//foobar.example.comenableIpv6:domain.enableIpv6,//truebydefault–setenableIpv6proptofalseduringnewDomain()})//assignCloudFrontdistributiontogivenfqdnwithA+AAAArecordsdomain.addTarget(newtargets.CloudFrontTarget(distribution))CloudFront helperInstead of assigningcertificate,domainNamesandenableIpv6properties individually, you may choose to use the one-liner helper utility methodconfigureCloudFront()to set all three values at once – don't forget to use...object spread syntax:constdistribution=newcloudfront.Distribution(this,'Distribution',{/*othercloudfrontconfigurationvaluesremovedforbrevity*///one-linertoconfigurecertificate,domainNamesandIPv6support...domain.configureCloudFront(),})//assignCloudFrontdistributiontogivenfqdnwithA+AAAArecordsdomain.addTarget(newtargets.CloudFrontTarget(distribution))Note: The returned domain names configuration isdomainNames: [domain.fqdn], meaning this only works in scenarios where your CloudFront distribution has only single domain name.
Package: alma-cdk.origin-verify
npmi-D@alma-cdk/origin-verifyEnforce API Gateway REST API, AppSync GraphQL API, or Application Load Balancer traffic via CloudFront by generating a Secrets Manager secret value which is used as a CloudFront Origin Custom header and a WAFv2 WebACL header match rule.Essentially this is an implementation ofAWS Solution“Enhance Amazon CloudFront Origin Security with AWS WAF and AWS Secrets Manager” without the secret rotation.🚧   Project StabilityThis construct is still versioned withv0major version and breaking changes might be introduced if necessary (without a major version bump), though we aim to keep the API as stable as possible (even withinv0development). We aim to publishv1.0.0soon and after that breaking changes will be introduced via major version bumps.Getting Startedimport{OriginVerify}from'@alma-cdk/origin-verify';import{Distribution}from'aws-cdk-lib/aws-cloudfront';constapi:RestApi;//TODO:implementtheRestApiconstapiDomain:string;//TODO:implementthedomainconstverification=newOriginVerify(this,'OriginVerify',{origin:api.deploymentStage,});newDistribution(this,'CDN',{defaultBehavior:{origin:newHttpOrigin(apiDomain,{customHeaders:{[verification.headerName]:verification.headerValue,},protocolPolicy:OriginProtocolPolicy.HTTPS_ONLY,})},})For more detailed example usage see/examplesdirectory.Custom Secret ValueAdditionally, you may pass in customsecretValueif you don't want to use a generated secret (which you should use in most cases):constmyCustomValue=SecretValue.unsafePlainText('foobar');constverification=newOriginVerify(this,'OriginVerify',{origin:api.deploymentStage,secretValue:myCustomValue,});NotesUseOriginProtocolPolicy.HTTPS_ONLY!In your CloudFront distribution Origin configuration useOriginProtocolPolicy.HTTPS_ONLYto avoid exposing theverification.headerValuesecret to the world.WhysecretValue.unsafeUnwrap()?Internally this construct creates theheaderValueby using AWS Secrets Manager but the secret value is exposed directly by usingsecretValue.unsafeUnwrap()method: This is:required, because we must be able to set it into the WAFv2 WebACL rulerequired, because you must be able to set it into the CloudFront Origin Custom Headerokay, because it's meant to protect the API externally and it'snotconsidered as a secret that should be kept – well – secret withinyourAWS account
Package: alma-client
alma-python-clientPython API Client for the Alma API.Support Python >= 3.8Installpipinstallalma-clientDemoWe support both a sync and async client.Synchronous clientfromalma_clientimportClientalma_client=Client.with_api_key("sk_test..")payments=alma_client.payments.fetch_all()forpinpayments:print(f"{p.id}: Paiement en{len(p.payment_plan)}fois")payment_data={"payment":{"purchase_amount":10000,"return_url":"http://merchant.com/payment-success","shipping_address":{"first_name":"Martin","last_name":"Dupond","line1":"1 rue de Rivoli","postal_code":"75004","city":"Paris"}}}eligibility=alma_client.payments.eligibility(payment_data)ifeligibility.eligible:payment=alma_client.payments.create(payment_data)print(payment.raw_data)Asynchronous clientfromalma_clientimportAsyncClientalma_client=AsyncClient.with_api_key("sk_test..")payments=awaitalma_client.payments.fetch_all()forpinpayments:print(f"{p.id}: Paiement en{len(p.payment_plan)}fois")payment_data={"payment":{"purchase_amount":10000,"return_url":"http://merchant.com/payment-success","shipping_address":{"first_name":"Martin","last_name":"Dupond","line1":"1 rue de Rivoli","postal_code":"75004","city":"Paris"}}}eligibility=awaitalma_client.payments.eligibility(payment_data)ifeligibility.eligible:payment=awaitalma_client.payments.create(payment_data)print(payment.raw_data)Changelog3.0.2 (2022-12-07)Fix dump for null-body requests.3.0.1 (2022-12-05)Configure credentials later in the flow.3.0.0 (2022-06-29)Breaking changeMove the code from thealmanamespace into thealma_clientnamespace.Remove support for Python 3.6 and Python 3.72.0.2 (2022-06-22)Fixpotential-fraudmethod URLs (#27)2.0.1 (2022-06-17)Addsinclude_child_accountsandcustom_fieldsparams to the DataExport creation endpoint2.0.0 (2021-08-12)Breaking changesMove from requests to HTTPXHandle both sync and async python clientsRemove support for Python 3.5Add support for Python 3.91.2.0 (2020-09-01)Add support for different authentication methodsAdd Black & isort checks on pull requests1.1.0 (2020-03-25)Add support for Python 3.5+1.0.1 (2020-03-24)Automatically detects the API mode from the api_key.1.0.0 (2020-03-24)Create a Python client for AlmaHandle Order entity for PaymentHandle the refund endpointHandle pagination for ordersHandle the send-sms API for payments.