Saravanan666/pypi-org huggingface dataset:
Package: ynabintegrationslib
A library implementing integrations for ABN Amro accounts, ICS credit cards and RABO Bank csv exports with YNABDocumentation:https://ynabintegrationslib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (26-06-2019)First code creation0.1.0 (10-10-2019)first release of library0.1.1 (10-10-2019)Exposed objects and exceptions at the package level0.1.2 (09-12-2019)Bumped dependency and commented for linting.0.1.3 (10-12-2019)Bumped dependency.0.1.4 (26-10-2020)Fixed a bug with a new header cookie introduced by ICS.0.2.0 (06-07-2021)Made comparison on ynab transactions a little more loose.0.2.1 (07-07-2021)Added pipeline and bumped dependencies.
Package: ynabinterfaceslib
A library implementing interfaces for institution (banks, other organizations) integrations to YNABDocumentation:https://ynabinterfaceslib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (16-08-2019)First code creation0.1.0 (16-08-2019)Renamed from bankinterfaceslib0.2.0 (17-08-2019)Made timeout on click event configurable1.0.0 (13-09-2019)Removed selenium authenticator1.0.1 (16-04-2021)Updated an abstract method to property and bumped dependencies.1.0.2 (06-07-2021)Bumped dependencies and renamed main branch.1.0.3 (06-07-2021)Bumped dependencies and renamed main branch.1.0.4 (07-07-2021)Added pipeline and bumped dependencies.
Package: ynablib
A library implementing basic interaction with the YNAB serviceDocumentation:https://ynablib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (26-07-2019)First code creation0.1.0 (26-07-2019)Initial implementation0.1.1 (28-07-2019)Made retrieving of objects safe and added some logging0.1.2 (30-07-2019)Extended logging0.2.0 (13-09-2019)Added transaction objects under budgets and accounts0.2.1 (06-07-2021)Linted and bumped dependencies.0.2.2 (07-07-2021)Added pipeline and bumped credentials.
Package: ynab-memo-parser
ynab-memo-parserThis library helps you to use original memo and payee information from your bank transactions to either show additional
details or substitute/change the current one in YNAB. It can be helpful for cases in which YNAB import does not handle the
information coming from the bank well (e.g. not showing the actual bank memo or populating a wrong payee name).PreparationsCreate a personal access token for YNAB as describedhereGet the IDs of your budget and account which records are faulty. You can find both IDs if you go tohttps://app.ynab.com/and open the target account by clicking on the name on the left hand side menu.
The URL does now contain both IDshttps://app.ynab.com/<budget_id>/accounts/<account_id>Basic Usage1. Install library from PyPIpipinstallynab-memo-parser2. Check your original memo and payee values for potential things to useAll records in YNAB come with their original memo and payee information attached. You can see both values if you use
the `fetch records' function of this library and look at a couple sample records.fromynabmemoparserimportYnabMemoParserynab_memo_parser=YnabMemoParser(token='<token>',budget='<budget>',account='<account>')ynab_memo_parser.fetch_record_dicts()You will get back a dictionary with all data stored for the transaction. The library uses the following keys with the
stated labelsimport_payee_name_originalasoriginal_memoimport_payee_nameasoriginal_payeepayeeascurrent_payeememoascurrent_memo3. Create aParserchild class which implements your logicThe class needs to implement a logic forparse_payee()andparse_memo()based on the values coming from the four
fields above. If you don't want to change anything in the field you e.g. justreturn current_payeeinside theparse_payee()function.fromynabmemoparserimportParserclassMyParser(Parser):defparse_payee(self,original_payee:str,current_payee:str,original_memo:str,current_memo:str)->str:# your implementationdefparse_memo(self,original_payee:str,current_payee:str,original_memo:str,current_memo:str)->str:# your implementation3. Test your parser on some recordsfromynabmemoparserimportYnabMemoParserynab_memo_parser=YnabMemoParser(token='<token>',budget='<budget>',account='<account>')record_dicts=ynab_memo_parser.fetch_record_dicts()parsed_records=ynab_memo_parser.parse_records(records_dicts=record_dicts,parser=MyParser())You will get back a list ofYnabRecordobjects. Check thepayeeandmemofields in these objects to see the result
of your parser.4. Update your records in YNABIf you are satisfied with your parsing results you can pass the list ofYnabRecordto theupdate_records()function.
It will update thepayeeandmemovalues in YNAB with the values in theYnabRecordobjectynab_memo_parser.update_records(parsed_records)If the insert is successful you get back an integer with the number of records which have been updated.
Package: ynd-geosoft-demo
ynd_geosoft_demoPython package to test my skill on geosoft courseFree software: MIT licenseDocumentation:https://YOUNKAP.github.io/ynd_geosoft_demoFeaturesTODOTODOTODO 3CreditsThis package was created withCookiecutterand thegiswqs/pypackageproject template.
Package: yndx-parse
Yndx-parseYndx-parse is a Python library for parsing weather data.InstallationUse the package managerpipto install Yndx-parse.pipinstallyndx-parseUsagefromyndx-parseimportYndxParse# Create an instance of the class,# passing the argument as the name of the city.yp=YndxParse('London')print(yp.get_weather())# Create an instance of the class,# passing the argument as a tuple# containing longitude and latitude.coords=(54.341,43.8766)yp=YndxParse(coords)print(yp.get_weather())ContributingPull requests are welcome. For major changes, please open an issue first
to discuss what you would like to change.Please make sure to update tests as appropriate.LicenseMIT
Package: yni
yniA parser for the yni config file.Exampletest.pyfromyniimportYniparser=Yni.from_file('example.yni')# here we parse from a fileparser['foo']['bar']# get the value of the key "bar" from the header "foo", returns "spam"# orparser.foo.bar# returns "spam"Example 2test_2.pyfromyniimportYnistring="""#foo[bar: spam]"""parser=Yni.from_string(string)# here we parse from a stringparser['foo']['bar']# get the value of the key "bar" from the header "foo", returns "spam"# orparser.foo.bar# returns "spam"yni file structureexample.yni#foo
[
    bar: spam
]
Package: ynj
ynjCompileJinjatemplates usingYAMLvariables!Installationpip install ynjUsageTo useynjyou need yaml file with the variables, and a jinja template.
An examplevalues.ymlfile:---
  name: John
  surname: Collins
  jobs:
    - name: "Python developer"
      technologies: [Pyton, SQL]
    - name: "Database administrator"
      technologies: [PostgreSQL, Oracle]A sample template:<h1>{{ name }} {{ surname }}</h2>
  <dl>
{% for job in jobs %}
      <dt>{{ job.name }}</dt>
      <dd>{{ ', '.join(job.technologies) }}</dd>
{% endfor %}
  </dl>To fill the values into the template, run:ynj < jobs.j2You can override values also from command line:ynj -t jobs.j2 -s "{name: Matt}"More info:ynj -h.
Package: yn-lantern
LanternLantern is a library that allows for control of Yongnuo YN-series Bluetooth-enabled video lights via Python.Currently, Lantern supports the following models:YN-360(purchasehere)Lantern has been tested on the following operating system(s):Ubuntu 16.10The protocol for communicating with the lights was reverse-engineered during a YouTube livestream:Reverse Engineering the Yongnuo YN 360 Bluetooth Protocol. The author uses the lights for studio lighting, and will be using the library in automation tools to ensure that each scene is properly lit.InstallationLantern requiresbluepy– an wrapper around the BTLE portions of Linux's official Bluetooth protocol stack,BlueZ. Although thebluepyinstallation usually goes smoothly, you may encounter issues. It is recommended that you visit thebluepyproject pageto review their installation instructions.Once you've gotbluepy's dependencies installed, you can run the following command from your virtual environment:$pipinstallyn-lanternNOTE: Lantern was written for Python 3, and has not been tested (and will most likely not work) in Python 2.x.Getting StartedGetting started with Lantern is simple. Once you've installed the library using the steps provided above, you may import and use Lantern in your code. Please keep in mind that, on some systems,rootprivileges will be required to manage the bluetooth interface.Lantern will attempt to render color temperatures from 1,000 to 40,000 kelvin. Color temperatures between 3,200 and 5,500 kelvin will be rendered using high-intensity, high-CRI LEDs when possible.fromlanternimportLightforlightinLight.discover():# connect to the lightlight.connect()# set the color temperature of the lightlight.color_temperature=4800# set the output of the light to 50% intensitylight.intensity=0.5# once we're done, disconnectlight.disconnect()For some types of lights (specifically, the YN-360), RGB colors can be rendered. In the following example, we connect to a specific light, and render RGB colors in two ways, pausing two seconds between each change.importtimefromlanternimportLightl=Light("e8:53:aa:45:db:c6")l.connect()# set an RGB color using a packed hex valuel.color=0xFF9900# sleep two seconds, as promisedtime.sleep(2)# set red, green, and blue components of the color individuallyl.color=(0xff,0x99,0x00)l.disconnect()ContributingPlease fork and open a PR to contribute. Feel free to submit issues if you run into issues. I'll do my best to help.LicenseThis project is licensed under theMIT License, and is Copyright 2017 Kenneth Keiter.
Package: ynm3k
ynm3k(文档)取名自”要你命3000”，目前的功能包括一个通过完全通过json进行配置的mock调试/反向代理服务器一个静态文件服务器（除静态目录外，还可以服务zip文件）安装方法通过pip安装sudo pip install ynm3k基本的使用方法在8080启动一个mock服务器，根据mock.json的规则进行转发和改写请求y3k --mock mock.json --port 8080mock.json的一些例子如下所示:根据前缀转发请求至不同服务器[
  ["/api/", "http://example.com/api/"],
  ["/static/my_work.html", "http://127.0.0.1/static/my_work.html"],
  ["/", "http://192.168.1.10:8080/"]
]为每个请求增加一个特殊的header，比如设置X-Forwarded-For[
 [{"type": "prefix",
   "path": "/",
   "headers": {"X-Forwarded-For": "1.2.3.4"}},
  {"type": "remote",
   "url": "https://ifcfg.cn/"}
 ]
]转发某个前缀下的请求到一个本地目录下，并且对于/prefix/dirname/这样的请求自动返回该目录下的index.html的内容[
["/prefix/", {"type": "static",
              "path": "examples/dir",
              "try_files": "index.html"}
]
]为每个请求的response，增加一个特殊的header，比如设置Cache-Control[
   [
      "/",
      {
         "type" : "remote",
         "url" : "https://ifcfg.cn/",
         "headers" : {
            "Cache-Control" : "private"
         }
      }
   ]
]改写特殊的请求(对于POST /test 这个请求，结果是文件test.json的内容)[
   [
 {
   "type": "exact",
   "path": "/test",
   "method": "POST"
 },
 {
   "type": "file",
   "body": "test.json",
   "headers": {"content-type": "json"}
 }
   ],
   ["/", "http://192.168.1.10:8080/"]
]
Package: ynot3
ynot3A simple image annotation program compatible with x11 and wayland.
Targetting an efficient workflow and minimal dependencies.can save to disk or copy to clipboard (requiresxcliporwl-copy).copy to clipboard on exitunlimited undoantialiasingsnapping for better alignments (override settingSNAPPINGenvironment variable, defaults to 8)very simple user interfaceSupported shapes:enumerated bulletsrectanglesarrowsDocumentation / annotation exampleActive tool(4)rectangle(5)arrow(6)enumerated bulletActive colorAction buttons(7)undo (shorcut: backspace)(8)copy to clipboard (automatic on exit)(9)save to/tmp/annotated.jpg(shortcut: "s")override setting theANNOTATEDenvironment variable(10)toggle large mode (everything is magnified)(11)clear changes (remove all annotations) (shortcut: "c")Installationpip install ynot3Or, on Archlinux:yay -S ynot3Example usageEdit an existing imageynote3 ~/Images/example.jpgEdit a screenshotA simple script for Wyland usinggrimshot:#!/bin/shFN="/tmp/shot.png"grimshotsavearea"${FN}"execynote3"${FN}"
Package: ynot-astro
ynotDOI coming soon?Why not just forward model the 2D focal plane array?  An experimental approach to echellogram modeling, in early development.  The baseline PyTorch code and project scaffolding is based off of Ian Czekala'sMPoL project.CitationThere is no citation for this software yet.  You can cite theMPoL projectwhen discussing the heritage and convolutional technology.Copyright M. Gully-Santiago and contributors 2020Version :
0.0.1
Package: yo
yo - fast and simple OCI clientyo is a command-line client for managing OCI instances. It makes launching OCI
instances as simple as rudely telling your computer "yo, launch an instance".
Its goals are speed, ease of use, and simplicity. It was originally designed to
help developers in the Oracle Linux team quickly launch disposable VMs for
testing, but is slowly gaining users outside of OL. Here are some examples of
how yo tries to improve on the OCI command line and browser tools:yo hides other people's VMs from you, so you can just manage your own
instances.yo doesn't make you type any more than you need. Compartment IDs, common shape
configurations, etc can all be stored in your config. It really can be as
simple asyo launch(or, for the lazier,yo la).yo lets you refer to your instances by name. You should never need to memorize
an IP address again.yo aggressively caches data to make operations as quick as possible.InstallationA minimum of Python 3.6 is required in order to use Yo.Via Pip:pip install yo oci-cliThis will install the standard OCI CLI alongside Yo, which can be useful as
well.  After installation, you'll need to configure Yo to work with your OCI
tenancy.  Please see thedocumentationfor detailed instructions.DocumentationThedocumentationcontains information on the configuration file, as well as
a listing of sub-commands and features offered.Examples# Launch an instance based on your default settings, and SSH into ityolaunch-s# Launch a flexible instance with given shape, size, and nameyolaunch-SVM.Standard.E4.Flex--cpu3--mem12-nmy-vm# SSH into my-vmyosshmy-vm# Copy files to my-vmyoscp./filesmy-vm:# Terminate my-vmyoterminatemy-vmHelpWe hope you can find all the answers to your questions in our documentation. But
if you're still having trouble, feel free to open a Github issue and we'll try
our best to help!ContributingWe welcome contributions from the community. Before submitting a pull request,
pleasereview our contribution guide.SecurityPlease consult thesecurity guidefor our responsible security
vulnerability disclosure process.LicenseCopyright (c) 2023 Oracle and/or its affiliates.Released under the Universal Permissive License v1.0 as shown athttps://oss.oracle.com/licenses/upl/.
Package: yoapi
YoApi docs -https://medium.com/@YoAppStatus/yo-developers-api-e7f2f0ec5c3cYou will need a YoApi API key to use this library, obtain one here -http://yoapi.justyo.co/UsageUsage is simple:#!/usr/bin/env python

from yoapi import yo

yo = yo.api(API_KEY)
yo.yoall()
yo.yo('BRADC')
Package: yob
Yobs: Python dictionaries that you can easily save, restore and edit as filesA Yob (yaml file object) is a python dictionary that you can easily save, restore and edit as a file.Yobs also come with an optional simple but powerful file oriented database.Yobs can be arbitrarily complex and may leverage the serialization/deserialization capabilities ofPyYAMLif needed.While yobs are reasonably performant they are individualyamlfiles at heart.Specialize yobs to serve up JSON or models with any behavior based upon their data that you fancy.Not tested on Windows.Use a lonely yob for configurationIn [1]: from yob import Yob

In [2]: y = Yob('/tmp/yobs/A')

# Use a context manager to automatically save any changes
In [3]: with y:
   ...:     y['base_path'] = '/tmp/yobs'
   ...: 

In [4]: y
Out[4]: {'base_path': '/tmp/yobs'}

# ...or explicitly save after changes
In [5]: y['max'] = 99

In [6]: y.save()

In [7]: y
Out[7]: {'base_path': '/tmp/yobs', 'max': 99}

# Use it like any other dictionary
In [8]: y['max']
Out [8]: 99You can also edit the file directly - it is justyaml.Or put convivial yobs together as a file based databaseThe database is created from a root folder. Sub folders are generated from the unique identifier used for each yob in the database to make listing and filtering easy.In [1]: animal_init = {'age': 0}

In [2]: cats_and_dogs = {'dog': ['fido', 'rover', 'spud'],
   ...:                  'cat': ['puss', 'ginger', 'oscar']}  # using <type>/<name> as uids
   
In [3]: from yob_database import YobDatabase

In [4]: !mkdir /tmp/test_yobs

In [5]: db = YobDatabase('/tmp/test_yobs')

In [6]: for animal_type, animal_names in cats_and_dogs.items():
   ...:     for name in animal_names:
   ...:         uid = f"{animal_type}/{name}"
   ...:         data = {**animal_init, 'type': animal_type, 'name': name}
   ...:         db.create(uid, data)
   ...:
In [7]: with db.get('dog/fido') as fido:
   ...:     fido['age'] = 10
   ...: 

In [8]: db.list()
Out[8]: 
[{'age': 0, 'name': 'oscar', 'type': 'cat'},
 {'age': 0, 'name': 'puss', 'type': 'cat'},
 {'age': 0, 'name': 'ginger', 'type': 'cat'},
 {'age': 0, 'name': 'rover', 'type': 'dog'},
 {'age': 0, 'name': 'spud', 'type': 'dog'},
 {'age': 10, 'name': 'fido', 'type': 'dog'}]

In [9]: db.filter(lambda y: y['name'].endswith('r'))
Out[9]: 
[{'age': 0, 'name': 'oscar', 'type': 'cat'},
 {'age': 0, 'name': 'ginger', 'type': 'cat'},
 {'age': 0, 'name': 'rover', 'type': 'dog'}]

In [10]: db.filter(lambda y: y['name'].endswith('r'), 'cat')
Out[10]: 
[{'age': 0, 'name': 'oscar', 'type': 'cat'},
 {'age': 0, 'name': 'ginger', 'type': 'cat'}]

In [11]: db.filter(lambda y: y['age'] > 5)
Out[11]: [{'age': 10, 'name': 'fido', 'type': 'dog'}]The file structure is simple and easy to work with directly too:(yob) test_yobs $ tree
.
├── cat
│   ├── ginger
│   ├── oscar
│   └── puss
└── dog
    ├── fido
    ├── rover
    └── spud

2 directories, 6 files
(yob) test_yobs $ cat cat/ginger
age: 0
name: ginger
type: cat