Saravanan666/pypi-org huggingface dataset:
Package: autohell
autohellautohellcontrols your monitor's brightness ("hell" means bright in German) automatically.
For now, it keeps your monitor at 60% brightness during the day, and then slowly dims your
monitor starting at 7 PM and ends at 5% brightness at 9:30 PM. Why these values? Because I like
them. These values are currently not configurable. PR's welcome :)If you change your monitors brightness at any time through any other means, autohell will stop
doing anything for 3 hours (or until you restart it).InstallationI recommend usingpipxto install
Python executables:pipx install autohellNote:autohellcurrently does not have any UI, if you run the executable from pipx,
it will just run in the background. You have to use your task manager to stop it.Licenseautohellis distributed under the terms of theMITlicense.
Package: autohook
Can be configured in any hgrc (system, user, repo) and trigger for
any event into any repository.
Can load external (Python) hooks that needs to accept parameters
repo, user, start revison, end revisionContains two built-in hooks, adds_branch and has_multiple_heads,
and users that can bypass hooks can be defined. Depends on hgapi (https://bitbucket.org/haard/hgapi).
Package: autohooks-plugin-autopep8
autohooks-plugin-autopep8Anautohooksplugin for python code
formatting viaautopep8.InstallationInstall using pipYou can install the latest stable release of autohooks-plugin-autopep8 from the
Python Package Index usingpip:pip install autohooks-plugin-autopep8Note thepiprefers to the Python 3 package manager. In a environment where
Python 2 is also available the correct command may bepip3.Install using pipenvIt is highly encouraged to usepipenvfor
maintaining your project's dependencies. Normally autohooks-plugin-autopep8 is
installed as a development dependency.pipenv install --dev autohooks-plugin-autopep8UsageTo activate the autopep8 autohooks plugin please add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.autopep8"]Customizing theautopep8behaviorTo pass options toautopep8, you have to add an additional[tool.autohooks.plugins.autopep8]option=valueblock to yourpyproject.tomlfile. Possible options are explained in the following.Included filesBy default, autohooks plugin autopep8 checks all files with a.pyending. If only
files in a sub-directory or files with different endings should be formatted,
just add the following setting:include=['foo/*.py','*.foo']Experimentalautopep8featuresExperimental features can be enabled by adding the following setting:experimental-features=trueThe are disabled by default.Ignored errorsYou can specificy which errors should be ignored as follows:ignore_errors=['E101',...]where the errors should match to thelist of errors fixed byautopep8.The default is['E226', 'E24', 'W50', 'W690'].Maximum line lengthThe maximum allowed line length can be set withmax_line_length=79The default is 79.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseLicensed under theGNU General Public License v3.0 or later.
Package: autohooks-plugin-black
autohooks-plugin-blackAnautohooksplugin for python code
formatting viablack.InstallationInstall using pipYou can install the latest stable release of autohooks-plugin-black from the
Python Package Index usingpip:python3 -m pip install autohooks-plugin-blackInstall using poetryIt is highly encouraged to usepoetryfor
maintaining your project's dependencies. Normally autohooks-plugin-black is
installed as a development dependency.poetry add --dev autohooks-plugin-blackUsageTo activate the black autohooks plugin please add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.black"]By default, autohooks plugin black checks all files with a.pyending. If only
files in a sub-directory or files with different endings should be formatted,
just add the following setting:[tool.autohooks]pre-commit=["autohooks.plugins.black"][tool.autohooks.plugins.black]include=['foo/*.py','*.foo']Also by default, autohooks plugin black executes black with the-qargument.
If e.g. the generated patch should be shown the following setting can be used:[tool.autohooks]pre-commit=["autohooks.plugins.black"][tool.autohooks.plugins.black]arguments=["-q","--diff"]MaintainerThis project is maintained byGreenbone AG.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseCopyright (C) 2019-2023Greenbone AGLicensed under theGNU General Public License v3.0 or later.
Package: autohooks-plugin-flake8
autohooks-plugin-flake8Anautohooksplugin for python code
linting viaflake8.InstallationInstall using pipYou can install the latest stable release of autohooks-plugin-flake8 from the
Python Package Index usingpip:python3 -m pip install autohooks-plugin-flake8Install using poetryIt is highly encouraged to usepoetryfor
maintaining your project's dependencies. Normally autohooks-plugin-flake8 is
installed as a development dependency.poetry installUsageTo activate the flake8 autohooks plugin please add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.flake8"]By default, autohooks plugin flake8 checks all files with a.pyending. If
only files in a sub-directory or files with different endings should be
formatted, just add the following setting:[tool.autohooks]pre-commit=["autohooks.plugins.flake8"][tool.autohooks.plugins.flake8]include=['foo/*.py','*.foo']To configure flake8 you can specify command-line options in the default flake8
configuration file.flake8in the root directory of the git repository.
To learn more about flake8 configuration see the configuration file or
the flake8 documentation. You can specify your own configuration file usingarguments = ["--config=/path/to/flake8config"]inside the[tool.autohooks.plugins.flake8]section of your projectspyproject.toml.Seeflake8 --helpfor more details.MaintainerThis project is maintained byGreenbone AG.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseCopyright (C) 2019 - 2023Greenbone AGLicensed under theGNU General Public License v3.0 or later.SPDX-License-Identifier: GPL-3.0-or-later
Package: autohooks-plugin-isort
autohooks-plugin-isortAnautohooksplugin for Python code
formatting viaisort.InstallationInstall using pipYou can install the latest stable release of autohooks-plugin-isort from the
Python Package Index usingpip:python3 -m pip install autohooks-plugin-isortInstall using poetryIt is highly encouraged to usepoetryfor
maintaining your project's dependencies. Normally autohooks-plugin-isort is
installed as a development dependency.poetry add --dev autohooks-plugin-isort

poetry installUsageTo activate the isort autohooks plugin please add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.isort"]By default, autohooks plugin isort checks all files with a.pyending. If only
the imports of files in a sub-directory or files with different endings should
be sorted, just add the following setting:[tool.autohooks]pre-commit=["autohooks.plugins.isort"][tool.autohooks.plugins.isort]include=['foo/*.py','*.foo']When usingautohooks-plugins-isortin combination withautohooks-plugin-black,
the following configuration is recommended to ensure a consistent formatting:[tool.isort]profile="black"MaintainerThis project is maintained byGreenbone AG.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseCopyright (C) 2019 - 2023Greenbone AGLicensed under theGNU General Public License v3.0 or later.
Package: autohooks-plugin-mypy
autohooks-plugin-mypyAnautohooksplugin for python code
static typing check viamypy.InstallationInstall using pipYou can install the latest stable release of autohooks-plugin-mypy from the
Python Package Index usingpip:python3 -m pip install autohooks-plugin-mypyInstall using poetryIt is highly encouraged to usepoetryfor
maintaining your project's dependencies. Normally autohooks-plugin-mypy is
installed as a development dependency.poetry installUsageTo activate the mypy autohooks plugin please add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.mypy"]By default, autohooks plugin mypy checks all files with a.pyending. If
only files in a sub-directory or files with different endings should be
formatted, just add the following setting:[tool.autohooks]pre-commit=["autohooks.plugins.mypy"][tool.autohooks.plugins.mypy]include=['foo/*.py','*.foo']By default, autohooks plugin mypy executes mypy without any arguments.
To change specific settings or to define a mypy config file the following plugin configuration can be used:[tool.autohooks]pre-commit=["autohooks.plugins.mypy"][tool.autohooks.plugins.mypy]arguments=["--ignore-missing-imports","--config-file=/path/to/.mypy.ini"]MaintainerThis project is maintained byGreenbone AG.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseCopyright (C) 2021Vincent Texier.
Copyright (C) 2023Greenbone AGLicensed under theGNU General Public License v3.0 or later.
Package: autohooks-plugin-pylint
autohooks-plugin-pylintAnautohooksplugin for python code
linting viapylint.InstallationInstall using pipYou can install the latest stable release of autohooks-plugin-pylint from the
Python Package Index usingpip:python3 -m pip install autohooks-plugin-pylintInstall using poetryIt is highly encouraged to usepoetryfor
maintaining your project's dependencies. Normally autohooks-plugin-pylint is
installed as a development dependency.poetry installUsageTo activate the pylint autohooks plugin please add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.pylint"]By default, autohooks plugin pylint checks all files with a.pyending. If
only files in a sub-directory or files with different endings should be
formatted, just add the following setting:[tool.autohooks]pre-commit=["autohooks.plugins.pylint"][tool.autohooks.plugins.pylint]include=['foo/*.py','*.foo']By default, autohooks plugin pylint executes pylint without any arguments and
pylint settings are loaded from the.pylintrcfile in the root directory of
git repository. To change specific settings or to define a different pylint rc
file the following plugin configuration can be used:[tool.autohooks]pre-commit=["autohooks.plugins.pylint"][tool.autohooks.plugins.pylint]arguments=["--rcfile=/path/to/pylintrc","-s","n"]MaintainerThis project is maintained byGreenbone AG.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseCopyright (C) 2019 - 2023Greenbone AGLicensed under theGNU General Public License v3.0 or later.
Package: autohooks-plugin-pytest
autohooks-plugin-pytestAnautohooksplugin forpytest.InstallationInstall using pipYou can install the latest stable release of autohooks-plugin-pytest from the
Python Package Index usingpip:python3 -m pip install autohooks-plugin-pytestInstall using poetryIt is highly encouraged to usepoetryfor
maintaining your project's dependencies. Normally autohooks-plugin-pytest is
installed as a development dependency.poetry installUsageTo activate the pytest autohooks plugin please add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.pytest"]By default, autohooks plugin pytest checks all files with a.pyending. If
only files in a sub-directory or files with different endings should be
tested, just add the following setting:[tool.autohooks]pre-commit=["autohooks.plugins.pytest"][tool.autohooks.plugins.pytest]include=['foo/*.py','*.foo']By default, autohooks plugin pytest executes pytest without any arguments and
pytest settings are loaded from the.pytestrcfile in the root directory of
git repository. To change specific settings or to define a different pytest rc
file the following plugin configuration can be used:[tool.autohooks]pre-commit=["autohooks.plugins.pytest"][tool.autohooks.plugins.pytest]arguments=["--rcfile=/path/to/pytestrc","-s","n"]MaintainerThis project is maintained byGreenbone AG.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseCopyright (C) 2021-2023Greenbone AGLicensed under theGNU General Public License v3.0 or later.
Package: autohooks-plugin-ruff
autohooks-plugin-ruffAnautohooksplugin for python code
formatting viaruff.InstallationInstall using pip[!NOTE] Thepip installcommand does no longer work out-of-the-box in newer
distributions like Ubuntu >= 23.04 because ofPEP 668.You can install the latest stable release of autohooks-plugin-ruff from the
Python Package Index usingpip:python3 -m pip install --user autohooks-plugin-ruffInstall using poetryIt is highly encouraged to usepoetryfor
maintaining your project's dependencies. Normally autohooks-plugin-ruff is
installed as a development dependency.poetry add --group dev autohooks-plugin-ruffUsageTo activate the ruff autohooks plugin please runpoetryrunautohookspluginsaddautohooks.plugins.ruffor alternatively add the following setting to yourpyproject.tomlfile.[tool.autohooks]pre-commit=["autohooks.plugins.ruff"]What the plugin actually does isruff check .on git commit, so you should be
able to use the exact same settings as inruff's docs.NotesThis project only runs ruff as a pre-commit hook, so, all features from ruff
should be available too.To activate this pre-commit hook remember to run this command before you start:poetryrunautohooksactivate--modepoetryMaintainerThis project is maintained byGreenbone AG.ContributingYour contributions are highly appreciated. Pleasecreate a pull requeston GitHub. Bigger changes need to be discussed with the development team via theissues section at GitHubfirst.LicenseCopyright (C) 2023 - 2024Greenbone AGLicensed under theGNU General Public License v3.0 or later.
Package: autohyp
Data AnalysisWhy did I write this code?I'm often handed a dataset and asked to do the same thing - determine if the experimental group is different than the control group, and generate some descriptive statistics along the way. As an alternative to writing all operations manually for each project I've created a Python module using Object Oriented Programming (OOP). This eliminates the need to search for old projects, copy and paste long lines of code and cross my fingers that it works.What libraries does this code use?This code uses aScipy, a widely accepted statistical package, to perform hypothesis testing.I also usePandas, an extremely popular data analysis and manipulation library for organizing the data and providing descriptive statistics.For data visualization I use theSeabornlibrary (built on top of matplotlib)Hypothesis TestingMy main task is often to determine if the results are statistically significant. For this we need to implement a hypthesis test, however there are many tochoose from. The decision tree of this code looks something like this:Is the data Normally Distributed and do the experimental and control groups have Equal Variance? Student's t-testIs the data Normally Distributed but do the experimental and control groups have Unequal Variance? Welches' t-testIs the data not Normally Distributed? Mann-Whitney U testWhere to StartSeeThis Notebookfor a demo on the Breast Cancer Wisconsin (Diagnostic) Dataset foundHereautohyp
Package: auto-iap-enviroment
IApO IAp é um projeto que integra a plataforma OpenAI GPT-3 a um ambiente local do usuário, facilitando a criação de arquivos que seriam repetitivos mas exigissem um contexto maior da aplicaçãoInstalaçãoO pacote pode ser instalado via pip, utilizando o seguinte comando:pipinstallauto-iap-enviromentComo utilizarPara utilizar o IAp, digite o seguinte comando no terminal:iap[CAMINHO_ARQUIVO.py][EXTENÇÃO_MONITORADA]Onde[CAMINHO_ARQUIVO]é um caminho absoluto para o arquivo em que você deseja salvar a resposta gerada pelo GPT-3 e[EXTENÇÃO_MONITORADA]é o tipo de arquivo vigiado pelo IApDetalhe que  valor default de[EXTENÇÃO_MONITORADA]é a extenção de[CAMINHO_ARQUIVO]Após a execução do comando, você deverá digitar o prompt que deseja enviar para o GPT-3.A partir disso o IAp treinara o GPT-3 com todos os arquivos que contenham a extenção monitorada para que ele entenda o contexto do seu projéto e, dessa maneira, retornando uma melhor resposta, que é salva no arquivo especificado anteriormente.Comandos adicionais disponíveis:iap setToken:  Realiza a mudança do token openai que será utilizado pela api no funcionamento.Exemplo de utilizaçãolendo todos os .py e escrevendo o código em exemplo.pyiapexemplo.pylendo todos os .js e escrevendo o código em exemplo.pyiapexemplo_dois.pyjsVideo do funcionamentohttps://user-images.githubusercontent.com/66787949/235394544-02f41fd5-d7d2-4cba-bf2c-5ab26a9fdfed.mp4O usuário digita um prompt no terminal e o IAp envia, junto com as informações dos arquivos, esse prompt para o GPT-3. O GPT-3 gera uma resposta, que é enviada de volta para o IAp, que salva no arquivo especificado pelo usuário.Dependênciasopenai (1.10.0)setuptools (57.4.0)DesenvolvimentoO projeto pode ser encontrado emhttps://github.com/luisArthurRodriguesDaSilva/IAp/tree/main. Qualquer sugestão ou contribuição é bem-vinda!
Package: autoimp
The autoimp module makes usage of the interactive Python prompt more productive.With autoimp, all installed Python modules can be imported with the single statement "from autoimp import *".  The  imported modules are proxy objects which lazily load when first used.Install with 'sudo pip install autoimp'.Proper installation of autoimp involves placing "from autoimp import *" in yourPYTHONSTARTUP file. Once autoimp is properly installed, it is no longer necessary to use statements of the form "import X" at the interactive prompt.
Package: autoimport
AutoimportAutoimport missing python libraries.Throughout the development of a python program you continuously need to manage
the python import statements either because you need one new object or because
you no longer need it. This means that you need to stop writing whatever you
were writing, go to the top of the file, create or remove the import statement
and then resume coding.This workflow break is annoying and almost always unnecessary.autoimportsolves this problem if you execute it whenever you have an import error, for
example by configuring your editor to run it when saving the file.HelpSeedocumentationfor more details.InstallingpipinstallautoimportContributingFor guidance on setting up a development environment, and how to make
a contribution toautoimport, seeContributing to
autoimport.LicenseGPLv3
Package: autoinclude-blueprints
Flask Blueprint autoincludeA function to automatically register all flask-blueprints from a project.register_blueprintsfrom flask_bp_autoregister.blueprintsWhen using flask blueprints then after defining them you have to register them all this can possible look like this.# in some config.py or __init__.pydefregister_my_blueprints(used_flask_app:any):frommy_app.viewsimporthome_viewsfrommy_app.viewsimportpackage_viewsfrommy_app.viewsimportaccount_viewsused_flask_app.register_blueprint(home_views.app_bp)used_flask_app.register_blueprint(package_views.app_bp)used_flask_app.register_blueprint(account_views.app_bp)# and then in your run.py or similarfrommy_appimportflask_appfrommy_appimportregister_my_blueprintsregister_my_blueprints(flask_app)if__name__=='__main__':flask_app.run()The register_blueprints code can get really long and you always have to remember where your blueprints are.For this is had created a functionregister_blueprintswhich automatically will search for all blueprints in your project and register them.frommy_appimportflask_appfromflask_bp_autoregister.blueprintsimportregister_blueprintsregister_blueprints(flask_app,'my_project/src/my_app')if__name__=='__main__':flask_app.run()The path attribute is not really needed you can also use it without then all blueprints inside of the project will be registered automaticallyfrommy_appimportflask_appfromflask_bp_autoregister.blueprintsimportregister_blueprintsregister_blueprints(flask_app)if__name__=='__main__':flask_app.run()When you have somecommented Blueprintsinside of your project,register_blueprintswill try to register them toowhich will raise an AttributeError you can disable this withsilent=Truefrommy_appimportflask_appfromflask_bp_autoregister.blueprintsimportregister_blueprintsregister_blueprints(flask_app,silent=True)# will prevent raising AttributeErrorif__name__=='__main__':flask_app.run()Tested for Versions3.6, 3.7, 3.8Installingpip install git+https://github.com/FelixTheC/autoinclude_flask_blueprints.gitVersioningFor the versions available, see the tags on this repository.AuthorsFelix Eisenmenger - Initial workLicenseThis project is licensed under the MIT License - see the LICENSE.md file for details
Package: autoinit
autoinitPython decorator for automatic initialization instance attributesWhatimportautoinit# same as `from autoinit import autoinit`@autoinitclassX:def__init__(self,a,b,c,d:int,e=99.99,f='some_default_value'):print("__init__ do some another things")x=X(42,100,500,None)#  Output: "__init__ do some another things"print(x.__dict__)# Output: {'a': 42, 'b': 100, 'c': 500, 'd': None, 'e': 99.99, 'f': 'some_default_value'}How$pip install autoinitWhereTested in:CPython: 2.7, 3.5-3.11Pypy: 2.7, 3.5-3.9Jython: 2.7...but with a high probability will work with other implementations as well.WhyA lot of elementary assignments inside__init__are a fairly frequent and rather dull case.classFiveDimensionRecord:def__init__(self,x:int,y:int,z:int,u:int,v:int,dt:typing.Optional[datetime]=None,description:str=''):self.x=xself.y=yself.z=zself.u=uself.v=vself.dt=dtordatetime.now()self.description=descriptionDataclasses do not make it much more fun, mainly because you still cannot declare attributes in one line@dataclassclassFiveDimensionRecord:x:inty:intz:intu:intv:intdt:'typing.Any'=Nonedescription:str=''def__post_init__(self):self.dt=self.dtordatetime.now()Withautoinitit looks much more compact and minimalisticclassFiveDimensionRecord:@autoinitdef__init__(self,x:int,y:int,z:int,u:int,v:int,dt=None,description:str=''):self.dt=self.dtordatetime.now()Options@autoinit(exclude='attr')or@autoinit(exclude=['attr1', 'attr2]'): skip specified attributes. Default:[]@autoinit(no_warn=True): do not throw warning if decorator applied to non-__init__method. Default:False.@autoinit(reverse=True): invert the order of actions - first call the wrapped method (which is usually__init__), and then do assignment. Default:False.The decorator itself can be equally applied to both the__init__method and the entire class.
Package: autoinject-pymitter
Pymitter IntegrationAdds the ability to inject an instance of EventEmitter frompymitter. This instance
will be shared within a context (separate threads have separate emitters). Registration is done via the entry point in
autoinject, so no need to do anything other than install this package.fromautoinjectimportinjectoras_injectorimportpymitterclassNeedsEvents:ee:pymitter.EventEmitter=None@_injector.constructdef__init__(self):passdefdo_stuff(self):self.ee.emit("foo.bar","hello world")classLikesEvents:ee:pymitter.EventEmitter=None@_injector.constructdef__init__(self):self.ee.on("foo.bar",self.on_event)defon_event(self,arg):print("foo bar emitted:{}".format(arg))emitter=NeedsEvents()receiver=LikesEvents()emitter.do_stuff()# OUTPUT: foo bar emitted: hello world