Saravanan666/pypi-org huggingface dataset:
Package: dotenv-cli
dotenv CLIDotenv-CLI is a simple package that provides thedotenvcommand. It reads the.envfile from the current directory puts the contents in the environment and
executes the given command.dotenvsupports alternative.envfiles like.env.developmentvia the-eor--dotenvparametes.dotenvprovides bash completion, so you can usedotenvlike this:$dotenvmake<TAB>
allcleandocslintreleasetestInstallUsing PyPidotenv-cli isavailable on PyPi, you can install it via:$pipinstalldotenv-cliOn Debian and UbuntuAlternatively, you can install dotenv-cli on Debian based distributions via:# apt-get install python3-dotenv-cliUsageCreate an.envfile in the root of your project and populate it with some
values like so:SOME_SECRET=donttrythisathomeSOME_CONFIG=fooJust prepend the command you want to run with the extra environment variables
from the.envfile withdotenv:$dotenvsome-commandand those variables will be available in your environment variables.RulesThe parser understands the following:Basic unquoted values (BASIC=basic basic)Lines starting withexport(export EXPORT=foo), so you cansourcethe
file in bashLines starting with#are ignored (# Comment)Empty values (EMPTY=) become empty stringsInner quotes are maintained in basic values:INNER_QUOTES=this 'is' a testorINNER_QUOTES2=this "is" a testWhite spaces are trimmed from unquoted values:TRIM_WHITESPACE=  fooand
maintained in quoted values:KEEP_WHITESPACE="  foo  "Interpret escapes (e.g.\n) in double quoted values, keep them as-is in
single quoted values.Example.envfile:BASIC=basicbasicexportEXPORT=fooEMPTY=INNER_QUOTES=this'is'atestINNER_QUOTES2=this"is"atestTRIM_WHITESPACE=fooKEEP_WHITESPACE="  foo  "MULTILINE_DQ="multi\nline"MULTILINE_SQ='multi\nline'MULTILINE_NQ=multi\nline## some commentbecomes:$dotenvenvBASIC=basicbasicEXPORT=fooEMPTY=INNER_QUOTES=this'is'atestINNER_QUOTES2=this"is"atestTRIM_WHITESPACE=fooKEEP_WHITESPACE=fooMULTILINE_DQ=multi
lineMULTILINE_SQ=multi\nlineMULTILINE_NQ=multi\nline
Package: dotenver
A Python app to generate dotenv (.env) files from templates.FeaturesAutomatic .env file generation from .env.example filesUseful for CI or Docker deploymentsUsesJinja2as rendering engineUsesFakerfor value generationQuickstartInstallPython DotEnver$pipinstalldotenverCreate a.env.examplefollowing this example# Full line comments will be kept# Simple usageNAME=## dotenver:first_name# Pass parameters to fakersENABLED=## dotenver:boolean(chance_of_getting_true=50)# Name your valuesMYSQL_PASSWORD=## dotenver:password:my_password(length=20)# And get the same value again, when the name is repeated.DB_PASSWORD=## dotenver:password:my_password()# Output your values within double or single quotesDOUBLE_QUOTED=## dotenver:last_name(quotes='"')SINGLE_QUOTED=## dotenver:last_name(quotes="'")# Literal values are possibleSTATIC_VARIABLE=static value# export syntax can be usedexport EXPORTED_VARIABLE=exportedRun pythonDotEnverform the CLI$dotenver-rYou now have a new.envfile ready to use.For more usage options run$dotenver-hDockerA Docker imageis provided. To use it, mount your source code to/var/lib/dotenver/and run the container.$dockerrun-ti--rm-v"${PWD}:/var/lib/dotenver/"jmfederico/dotenver
Package: dotenv-flow
dotenv_flowHierarchically load different dotenv files based on the value of thePY_ENVvariable. Dotenv files will be searched
by name, by decreasing order of priority (specificity) to the selected environment.As dotenv files are loaded, the process' environment (os.environ) is enriched with the variables found in those files.
Environment values that already exist will be left untouched.Files have 2 flavors:public (ex: .env.dev) that should be committed to version controlprivate (ex: .env.dev.local) that has preference over the previous one if present, and shouldNOTThis is the python version of Node'sdotenv-flow.dotenv files are loaded withpython-dotenvThis should be added to version control ignore file:# local .env* files
.env.local
.env.*.localIt's probably a good idea to also ignore plain.envfiles, as most tools will warn you
that it's a potential security risk.
Instead, including a.env-exampleseems to be a popular way to document the environment variables in use.
Package: dotenvhub
dotenvhubYour Terminal App to manage your .env filesIntroductionDotEnvHub helps storing and accessing your project specific .env files from a central place to setup your environment variables.
Supporting you to follow the12-factorprinciples when developing applications.FeaturesOrganizes files centrally underuser_data_dirfollowing theXDGBasedir SpecSaves your last selected shell automatically via a config file underuser_config_dirSupports Creating/Editing/Deleting files in your dotenvhubCurrently provides 3 ways to set your environment variables:Copy the Shell specific command to set the environment variables into your clipboardCreate a Copy of the selected file into your current working directoryCopy the path of the selected file to be used with e.g.python-dotenvwithout creating a copy in the projectInstallationYou can install dotenvhub with:python-mpipinstalldotenvhubOr usingpipxpipxinstalldotenvhubUsageUsing the Graphical UIAfter Installation the Interface can be opened with:dotUseCtrl+cto close the interface.Using the CLIThe Creation of a Copy in the CWD and copying the Shell String
to set the environment variables can also be done directly in the CLI:To create a copy ofFOLDER/FILEfrom DotEnvHub and save it asSAVENAMEin your CWD:dotcopy<FOLDER/FILE>-N<SAVENAME>To copy the string to clipboard to setFOLDER/FILEfrom DotEnvHub in yourShellof Choice:dotshell<FOLDER/FILE>-S<SHELL>Feedback and/or IssuesIf you have feedback or find bugs, feel free to open an Issue.:warning: DotEnvHub usespyperclipto handle copy/paste actions.
Based on the pyperclips documentation, you might need additional packages installed
on linux systems likexcliporxselwhich can be installed with:sudoapt-getinstallxclip
sudoapt-getinstallxsellike mentionedhere
Package: dotenv-linter
dotenv-linterSimple linter for.envfiles.While.envfiles are very simple it is required to keep them consistent.
This tool offers a wide range of consistency rules and best practices.And it integrates perfectly to any existing workflow.Readthe announcing post.Installation and usagepipinstalldotenv-linterAnd then run it:dotenv-linter.env.env.templateSeeUsagesection for more information.ExamplesThere are many things that can go wrong in your.envfiles:# Next line has leading space which will be removed:SPACED=# Equal signs should not be spaced:KEY=VALUE# Quotes won't be preserved after parsing, do not use them:SECRET="my value"# Beware of duplicate keys!SECRET=Already defined;(# Respect the convention, use `UPPER_CASE`:kebab-case-name=1snake_case_name=2And much more! You can find thefull list of violations in our docs.Pre-commit hooksdotenv-lintercan also be used as apre-commithook.
To do so, add the following to the.pre-commit-config.yamlfile at the root of your project:repos:-repo:https://github.com/wemake-services/dotenv-linterrev:0.2.0# Use the ref you want to point athooks:-id:dotenv-linterFor the more detailed instructions on the pre-commit tool itself,
please refer toits website.GratisSpecial thanks goes toIgnacio Toledofor creating an awesome logo for the project.
Package: dotenv-manager
dotenv-managerA decorator for defining a set of environment variables.
Uses the python-dotenv package to load additional variables from .envThe dotenv manager ensures the environment variables used in the project are set and have the correct types.Getting Startedpipinstalldotenv-managerfromdotenv_managerimportEnvManager@EnvManager()classCONFIG:KEY1:strKEY2:strINT_KEY:int>>>print(CONFIG.KEY1)"<KEY1>"Using theprefixparameter, it is possible to use a common prefix and separate the variables in groups.@EnvManager(prefix="AWS_")classAWS_CONFIG:SECRET:strENDPOINT:str@EnvManager(prefix="AZURE_")classAZURE_CONFIG:SECRET:strENDPOINT:strUsing strict=False, an error message is printed to the terminal, instead of throwing an error.@EnvManager(strict=False)classCONFIG:NOT_FOUND_KEY:strENDPOINT:str
Package: dotenvreader
DotENV-ReaderA Package for PiP that will read dotenv files.How to useCreate a new .env file (will throw an error if not found, it must be in the workspace where the package was imported) Copy the code below into one of your python files to start reading a dotenv.fromdotenvreaderimportmainasdotenvdotenv.config()# Configuring the dotenvprint(dotenv.get_value("example"))# Returns "Example"print(dotenv.exists("example"))# Returns "True"
Package: dotenv-stripout
:see_no_evil: dotenv-stripoutAn easily-installable git filter which hides your projects' sensitive data, while maximising collaboration and reproducibility.It's likenbstripoutfor your.envfiles.Eg. your local.envlooks like thisMY_SECRET_USERNAME=something-very-secret
MY_SECRET_PASSWORD=IqLTLrFviwHTDKWGZoR7uB2JtM1wjwE34MBwoztEbut your.envon GitHub looks like thisMY_SECRET_USERNAME=
MY_SECRET_PASSWORD=If you want to know more, I've written ablog postabout how and why I created this package.Installation & UseFirst, install the python package which does the stripping and manages the git filter.pipinstalldotenv-stripoutThen, to install the filter in the current repo, rundotenv-stripoutinstallTo remove the filter from the current repo, rundotenv-stripoutuninstallYou can check whether the filter is installed in a repo by runningdotenv-stripoutstatusAdding the--globalflag to any command will point them to yourglobalgit config instead, with the installed filter applying to commits in any repo.You can also use the CLI to strip your actual working.envfiles in the current repo. Just rundotenv-stripout
Package: dotenvy
Dotenv handler for PythonusagesInstallingpip install dotenvyCommon usage as libraryfrom dotenvy import load_env, read_file
from os import environ

load_env(read_file('.env'))
my_var = environ.get('MY_VAR')Loading dotenv file to a dict with type castingfrom dotenvy import read_file, truthy

config = read_file('.env', schema={
  'HOSTNAME': str,
  'PORT': int,
  'IS_DEBUG': bool,  # either [1/true/on/yes] or [0/false/off/no]
})Using it as a CLI tool# default dotenv file is '.env'
dotenvy ./mywebapp run

# using alternate dotenv file
dotenvy --file=prod.env ./mywebapp rundevelopmentChecking codestyle./setup.py stylecheckRunning tests./setup.py testRunning tests on all supported python versionspip install tox
tox
Package: dotest
VTESTdotest是一个基于pytest拓展的测试框架，完全兼容pytest功能，并增加更多易用性功能。主要功能支持指定测试case执行顺序： 顺序执行、并发执行、乱序执行支持测试case参数化设置支持测试case结果报告实时查看一键安装pip install dotest简易样例执行顺序testset 描述文件参考testset.yaml执行命令cd docs/example
dotest --testset testset/testset.yaml -v
Package: dotfigure
This package provides a docutils directive that integrates DOT graphs into the reST text.reST example:.. dotfigure::

   digraph G {
       id1 -> id1;
       id2 -> id2;
       id1 -> id3;
       id2 -> id3;
       id3 -> id4;
   }This directive requires a working Graphviz (http://www.graphviz.org) installation.Please see README.txt for examples.
Package: dotfile
dotdotis a git wrapper for managing dotfilesInstallationpip install dotfileHow it worksThe basics ofdotis that it runs this git command:git --git-dir=$HOME/.dotfiles --work-tree=$HOMEYou can easily specify where your git-dir is and what your work-tree is withdot.Why usedotinstead of aliasing this command?dotcomes with a few handy custom git commands that are specific with managing dotfiles.dot cwf(short for commit-with-filenames) will create a nice commit message showing which files you added/deleted/modified. You can also add your own description with the-mflag.dot sstatus of tracked files onlydot auadd/update currently tracked filesdot listlist all currently tracked filesUsageTo setup your dotfile repository, rundot initand it will walk you through the setup.
You can setup a new repository, or use an existing repository already on your machine.New repository setup[~]$ dot init
===== dotfile setup =====
Choose how you want to initialize your dotfiles:
[0] Create new dotfile repository
[1] Use existing dotfile repository
 > 0
New repository setup
--------------------
Repository name: [.dotfiles]
Default work tree: [/Users/kyle]

Generated configs: /Users/kyle/.config/dot/config.toml

[dot]
git-dir=/Users/kyle/.dotfiles/.git
work-tree=/Users/kyle

Do you wish to continue? (y/n [y]) y

Created config file at /Users/kyle/.config/dot/config.toml
Initialized empty Git repository in /Users/kyle/.dotfiles/.git/
Dotfile repository created at /Users/kyle/.dotfilesExisting repository setup[~]$ git clone https://github.com/kylepollina/.dotfiles
Cloning into '.dotfiles'...
remote: Enumerating objects: 65, done.
remote: Counting objects: 100% (65/65), done.
remote: Compressing objects: 100% (45/45), done.
remote: Total 2101 (delta 39), reused 43 (delta 20), pack-reused 2036
Receiving objects: 100% (2101/2101), 1.18 MiB | 1.89 MiB/s, done.
Resolving deltas: 100% (577/577), done.
[~]$
[~]$ dot init
===== dotfile setup =====
Choose how you want to initialize your dotfiles:
[0] Create new dotfile repository
[1] Use existing dotfile repository
 > 1
Existing repository setup
-------------------------
Repository name: .dotfiles
Work tree directory: [/Users/kyle]

Generated configs: /Users/kyle/.config/dot/config.toml

[dot]
git-dir=/Users/kyle/.dotfiles/.git
work-tree=/Users/kyle

Do you wish to continue? (y/n [y]) y

Created config file at /Users/kyle/.config/dot/config.toml
Dotfiles setup at /Users/kyle/.dotfiles

Analyzing dotfile repository...
There is 2 files and 0 directories in /Users/kyle/.dotfiles

Files
-----
.zprofile
.bash_profile

Would you like to move these into your work tree? (y/n [y]) y

Moving file /Users/kyle/.dotfiles/.zprofile to /Users/kyle
overwrite /Users/kyle/.zprofile? (y/n [n]) y
/Users/kyle/.dotfiles/.zprofile -> /Users/kyle/.zprofile

Moving file /Users/kyle/.dotfiles/.bash_profile to /Users/kyle
overwrite /Users/kyle/.bash_profile? (y/n [n]) n
not overwrittenLicenseMIT License
Package: dotfile-manager
Dotfile ManagerA dotfile manager to easily reuse configurations between linux and macOS.Installationpip install dotfile-managerUsageMake sure your dotfiles are organized as described below.cdinto your dotfiles repo.Installing the dotfiles: This will install all the necessary dependencies for
your dotfiles.dotfile_managerinstallSetting up the dotfiles: This will set up symbolic links for the config files,
symlink binaries and create a script to source everything.dotfile_managersetupOrganize your dotfiles for use with the dotfile managerA minimal example of how to organize your dotfiles can be seenhere,
a real-life examplehere.The dotfiles are organised by project, where each project has its own top-level
folder. A project has to contain a filedotfile_manager.yamlwhich configures the
dotfile manager. It is setup as follows:install_macos:-install_macos.shinstall_ubuntu:-install_ubuntu.shsymlinks:zshrc.zsh:~/.zshrcbin:-do_something.shsource:-aliases.sh-helpers.shdisable:FalseThe entries ofinstall_macosconfigure what scripts are used to install this project on macos.install_ubuntudoes the same for ubuntu. Multiple scripts can be provided and they are executed in
the order as specified in the yaml file.The entries ofsymlinksconfigure where the files will be symlinked to, the key is the path of the
file inside the topic folder, the value is the global path where the file will be symlinked to. Use
this to setup configuration files that need to be at a specific location (for example.bashrcwhich has to be in~/). It is possible to use~to specify the path of files that need to go to
a user's ``$HOME` folder.The entries ofbinwill be symlinked to${DOTFILES}/generated/bin/. Add the latter to your$PATHto easily execute these binaries from everywhere.The entries ofsourcewill be added to a script in${DOTFILES}/generated/sources.zsh, such that you only have to source this file
instead of sourcing all files individually.Lastlydisablecan be used to disable a dotfile project. If this is set to true this project will
be skipped during installation and setup.All these entries are optional. If you don't need them you can simply omit them.AdvancedTo work correctly the dotfile manager needs to know where the repo with all your
dotfiles is stored. Thus you need to run thedotfile_manager [install|setup]command from the directory where your dotfiles are stored. If you want to be
able to run the dotfile manager from anywhere there are two options:Use a command line argument:dotfile_manager-d<path/to/dotfiles/>installUse an environment variable:exportDOTFILES=<path/to/dotfiles>
dotfile_managerinstall
Package: dotflz
dotflzUtility to keep copies of dotfiles in one placeRequirementsPython 3Installationpip install dotflzUsageUsage: dotflz [OPTIONS] COMMAND [ARGS]...

  Utility to keep copies of dotfiles in one place.

Options:
  --help  Show this message and exit.

Commands:
  backup   Backup original files into backup directory.
  copy     Copy files by specified configuration file
  paste    Replace original files with ones from configured directory.
  restore  Restore original files with specified backup directory.
  verify   Verify configuration file.Example configurations can be foundhere.
Package: dotgen
How to Create your Own Data Structures LibraryCreate a virtual environment:python3 -m venv venvActivate the environment by using:source venv/bin/activateUtility our Python library:pip3 install wheel
pip3 install setuptools
pip3 install twineRun test-runner:python3 setup.py pytestBuild Library:python3 setup.py bdist_wheelWheel file is stored in the “dist” folder that is now created.
You can install your library by using:pip3 install dist/*.whlTest your import 🚀:from dotstruct import Stack
Package: dotgit
dotgitA comprehensive and versatile dotfiles managerdotgit allows you to easily store, organize and manage all your dotfiles for
any number of machines. Written in python with no external dependencies besides
git, it works on both Linux and MacOS (should also work on other *nix
environments).Project goalsShare files between machines or keep separate versions, all in the same repo
without any funny shenanigansMake use of an intuitive filelist which makes organization easyMake git version control convenient and easy to useWhy use dotgit?You can very easily organize and categorize your dotfiles, making it easy to
store different setups in the same repo (e.g. your workstation and your
headless server dotfiles, stored and managed together)Ease-of-use is baked into everything without hindering more advanced users.
For instance, dotgit can automatically commit and push commits for you should
you want it to, but you can just as easily make the commits yourselfdotgit has an automated test suite that tests its functionality with several
versions of Python on Linux and MacOS to ensure cross-platform compatibilitySupport for both symlinking or copying dotfiles to your home directory.
Copying allows you to quickly bootstrap a machine without leaving your repo
or dotgit on itNo external dependencies apart from git allowing you to install and use
dotgit easily in any environment that supports PythonEncryption using GnuPG supported to allow you to store sensitive dotfilesGetting startedTo get started with dotgit have a look at dotgit's documentation athttps://dotgit.readthedocs.io/.Future goalsThe following features are on the wishlist for future releases (more
suggestions welcome):Encryption using GnuPGConfig file for default behaviour (e.g. verbosity level, hard mode)TemplatingMigration from v1.xIf you used the previous bash version of dotgit (pre-v2) you need to follow the
migration guidehereto make your
dotfiles repo compatible with the new version.ContributingContributions to dotgit are welcome, just open a PR here on the repo. Please
note that your contributions should be linted with Flake8 (you can check for
linting errors locally by runningmake lintin the repo) and should also be
covered using unit tests using the pytest framework.
Package: dothebackup
A small tool to run backups in different ways. Its pluggable. Read more in thedocs.Usage: dothebackup [OPTIONS] CONFIGFILE

  Commandline interface.

Options:
  -n, --name TEXT       Run a specific job from the config.
  -t, --test            Only prints the created commands that would be used.
  --debug [debug|info]  Debug or verbose messages.
  --version             Show the version and exit.
  --help                Show this message and exit.
Package: do-the-webp
Converts cbz/cbr comic files to webpUsagedo-the-webp <dir>.This will overwrite your files!Installationpip install do-the-webpRequirementsunrar. Note thatunrar-freedoesn’t seem to work properly under Linux.CompatibilityLicenceGPLv3Authorsdo_the_webpwas written byPedro Vanzella.
Package: dothub
dothubStop managing your github configuration through an UI like a mere human
and do everything through beautiful config YAML files.dothub allows you to declare your configuration in a config file and
update it by just updating the file. This way you can configure your
labels, collaborators, default repo and organization parameters and
other as code and have them version controlled.If you are not sure how to configure something through the config file
just change it in the UI and sync it locally with your file, you will
see the changes! Next time you wont need to do any clicks!Installpip install dothubUsageThe first time you run dothub it will run a wizard to help you configure
your credentials.Repository configurationRetrieve locally:$dothubpullmariocj89/dothub.dothub.repo.ymlupdatedThis creates a file that represents your repo configurationUpdating from local changes:dothubpushmariocj89/dothubChanges:+root['collaborators']['dnaranjo89']+root['labels']['new-tag']Croot['hooks']['travis']['active'](True->False)Applychanges?[Y/n]:YUpdated!You can check the repo configuration in github. dnarnajo89 has been
invited as a collaborator, travis hooks have been disabled and you have
a new awesome “new-tag”Organization ConfigurationRetrieve locally:dothub pull <org_name>Updating from local changes:dothub push <org_name>Updating all repositories within an organizationYou can update all the repositories of an organization from your
.dothub.repo.yml file.To make a repo configuration be a template for all the repositories
of your org you can use dothub as follows:dothubpull<org/repo>.dothub.org.repos.ymldothubpush--bulkorg/*Note that some repository specific options like the name or the
description will be ignored on the update.Future featuresThis is justa prototype, dothub aims to be the configuration tool for
your whole github seeherefor the features that are going to come available soon.FAQHow can I retriger the reconfigure step?Just run dothub configureHow can I use the tool if I am need to provide a custom SSL certificate?Pass the envvar REQUESTS_CA_BUNDLE=YOURCERTPATH.cer before running
dothubI don’t want the tool to manage a part of the configJust remove that part! If there is full section missing (hooks, options,
members, etc.). It will be ignored
Package: dotify
Example Usage>>>fromdotifyimportDotify,Track>>>withDotify(SPOTIFY_ID,SPOTIFY_SECRET):>>>result=next(Track.search("SAINt JHN 5 Thousand Singles",limit=1))>>>result<Track"SAINt JHN - 5 Thousand Singles">>>>result.url'https://open.spotify.com/track/0fFWxRZGKR7HDW2xBMOZgW'>>>result.download("SAINt JHN - 5 Thousand Singles.mp3")PosixPath('SAINt JHN - 5 Thousand Singles.mp3')Feel free to check theexamplesfolder for more use cases!FeaturesSearching forTracksPlaylistsAlbumsDownloadingTracksPlaylistsAlbumsDocumentationThe project's documentation can be foundhere.InstallationpipinstalldotifySupporting the projectFeel free toBuy me a coffee! ☕.ContributingIf you would like to contribute to the project, please go through theContributing Guidelinesfirst.Contributors ✨Thanks goes to these wonderful people (emoji key):Vasilis Sioros🚧📆📖This project follows theall-contributorsspecification. Contributions of any kind welcome!