Saravanan666/pypi-org huggingface dataset:
Package: pipoe
pipoeThe objective of this project is to make creating OpenEmbedded python recipes just a bit easier.pipoewill take either a single package name or a requirements file and recursively generate bitbake recipes for every pypi package listed. It is not guaranteed that it will work for every package. Additionally, many recipes will still require additional modification after generation (patches, overrides, appends, etc.). In those cases it is recommended that the user add these modifications in a bbappend file.Install> pip3 install pipoeLicensesLicensing within OE is typically pretty strict.pipoecontains a license map which will attempt to map a packages license to one that will be accepted by the OE framework. If a license string is found which cannot be mapped, the user will be prompted to enter a valid license name. This mapping will be saved and the updated map will be saved to./licenses.pyif the--licensesflag is provided. It is recommended that this file be PR'ed to this repository when generally useful changes are made.Extraspipoesupports generating "extra" recipes based on the extra feature declarations in the packagesrequires_distfield (i.e. urllib3[secure]). These recipes are generated as packagegroups which rdepend on the base package.VersionsBy defaultpipoewill generate a recipe for the newest version of a package. Supplying the--versionargument will override this behavior. Additionally,pipoewill automatically parse versions from requirements files.Example> pipoe --help
usage: pipoe [-h] [--package PACKAGE] [--version VERSION]
             [--requirements REQUIREMENTS] [--extras] [--outdir OUTDIR]
             [--python {python,python3}] [--licenses]
             [--default-license DEFAULT_LICENSE]

optional arguments:
  -h, --help            show this help message and exit
  --package PACKAGE, -p PACKAGE
                        The package to process.
  --version VERSION, -v VERSION
                        The package version.
  --requirements REQUIREMENTS, -r REQUIREMENTS
                        The pypi requirements file.
  --extras, -e          Generate recipes for extras.
  --outdir OUTDIR, -o OUTDIR
                        The recipe directory.
  --python {python,python3}, -y {python,python3}
                        The python version to use.
  --licenses, -l        Output an updated license map upon completion.
  --default-license DEFAULT_LICENSE, -d DEFAULT_LICENSE
                        The default license to use when the package license
                        cannot be mapped.
> pipoe -p requests
Gathering info:
  requests
  | chardet
  | idna
  | urllib3
  | certifi
Generating recipes:
  python-requests_2.21.0.bb
  python-chardet_3.0.4.bb
  python-idna_2.8.bb
  python-urllib3_1.24.1.bb
  python-certifi_2018.11.29.bb

License mappings are available in: ./licenses.py
PREFERRED_VERSIONS are available in: ./python-versions.inc
Package: pipoke
What's this?Some tools to get data from pypi and kick it around, for fun and profit.Minus the profit.You can do stuff in python, but also have a CLI for most of the stuff.$pythonpipoke/pkg_vs_words.pyis-not-a-pkg-name"numpy,exists,but,this_crazy_pkg,does,not"{'this_crazy_pkg','but','exists','does'}So 'numpy' and 'not' are already registered with pypi.
But hey, the good news is 'but' and 'does' aren't.
Inspired to write some code bearing that name?Cool! How do I install it?pipinstallpipokeEnough said.Playfrompipoke.pkg_vs_wordsimportall_words,pkg_namesall_words# set of all English words (according to wordnet)pkg_names# set of all PyPi package names. All at the point the list was slurpedYou can have your own fun with that. Here are a few things to get you started.All pkg_names that are valid English words:frompipoke.pkg_vs_wordsimportall_words,pkg_namesset(all_words).intersection(pkg_names)All valid English words that are no "taken" by the pypi namespace:frompipoke.pkg_vs_wordsimportall_words,pkg_namesset(all_words).difference(pkg_names)All english words, package names, and intersection of both... that end with py:frompipoke.pkg_vs_wordsimportwords_and_pkg_names_satisfying_conditionwords_and_pkg_names_satisfying_condition(lambdaw:w.endswith('py'),print_counts=True)All english words, package names, and intersection of both... that contain py or pi:frompipoke.pkg_vs_wordsimportwords_and_pkg_names_satisfying_conditionimportpipoke.word_conditionsaswcwords_and_pkg_names_satisfying_condition(wc.contains_py_or_pi,print_counts=True)Want to search with a regular expression? Got you covered.
The above search is actually equivalent to:frompipoke.pkg_vs_wordsimportwords_and_pkg_names_satisfying_regexwords_and_pkg_names_satisfying_regex('.*(py|pi).*',print_counts=True)Get stuffThe repository comes with a data folder that contains a pickle containing a set of words (from wordnet)
and a set of pypi package names (well {pkg_name: pkg_url_stub, } to be exact).But you probably want to update that pypi list from time to time. And you can do so withfrompipoke.pypi_storeimportrefresh_saved_pkg_name_stubrefresh_saved_pkg_name_stub()Get dict of information for a pkg_name:frompipoke.pypi_storeimportinfo_of_pkg_from_webpkg_name='pipoke'info_of_pkg_from_web(pkg_name)And by the wayYou have a CLI for many of these things too.
Package: pip-outdated
Find outdated dependencies in your requirements.txt or setup.cfg file. Report missing/outdated/incompatible packages with table and colors.This tool compares the version number with the version specifier inrequirements.txtorsetup.cfg. If you just want to list all updatable package, simply usepip list--outdatedcommand.InstallationFrompypipip install pip-outdatedUsageusage: pip-outdated [-h] [-v] [-q] [<file> [<file> ...]]

Find outdated dependencies in your requirements.txt or setup.cfg file.

positional arguments:
  <file>         Read dependencies from requirements files. This option
                 accepts glob pattern. (default: ['requirements.txt',
                 'setup.cfg'])

optional arguments:
  -h, --help     show this help message and exit
  -v, --verbose  Print verbose information. (default: False)
  -q, --quiet    Don't return exit code 1 if not everything is up to date.
                 (default: False)Check multiple files e.g.test-requirements.txtanddev-requirements.txt:pip-outdated *-requirements.txtCheck files underrequirementsfolder:pip-outdated requirements/*.txtTodosAdd options to update the package?Add options to update the requirements.txt/setup.cfg file?Add options to list all packages? (e.g.-g,--global)Changelog0.6.0 (Jan 1, 2023)Bump dependencies.Drop cchardet.Change: fetch package version frompipCLI, so we can get package version in venv.0.5.0 (Jan 12, 2022)Bump dependencies.Add: typehint.0.4.0 (Jan 30, 2020)Breaking: bump Python to 3.7Add: request in parallel.Add:--quietoption.0.3.0 (Oct 13, 2019)Breaking: set exit code to 1 if not all good.Fix: don’t check prereleases.Add: checksetup_requiresandextras_requirein cfg files.0.2.0 (Feb 10, 2019)Bump dependencies:colorama@0.4.xpackaging@19.xrequests@2.xtermcolor@1.xterminaltables@3.x0.1.0 (May 12, 2018)First release.
Package: pip-package-list
pip-package-listA small and definitely faulty tool that tries to form a list of packages that you depend on. This is useful in mono-repo's where all dependencies are split into dozens ofrequirements.txtandsetup.pyfiles.One particular use-case that fueled the development of this tool was to create a flat list of dependencies to pre-install in a Docker base image.Although there is a number of tools that parse and resolve requirement files, I did not find any that parsesetup.pyfiles and extractinstall_requires.Usageusage: pip-package-list [-h] [--recurse-recursive] [--recurse-editable] [--recurse-path]
                        [--inline-constraints] [--dedupe] [--remove-editable] [--remove-path]
                        [--remove-recursive] [--remove-constraints] [--remove-vcs] [--remove-wheel]
                        [--remove-unversioned] [--remove-index-urls]
                        file_paths [file_paths ...]

positional arguments:
  file_paths            list of requirements.txt or setup.py files

optional arguments:
  -h, --help            show this help message and exit
  --recurse-recursive   recurse into -r entries
  --recurse-editable    recurse into -e entries
  --recurse-path        recurse into local path entries
  --inline-constraints  recurse into -c entries and inline them
  --dedupe              de-duplicate the resulting list
  --remove-editable     remove editable requirements from the final list
  --remove-path         remove path requirements from the final list
  --remove-recursive    remove recursive requirements (-r) from the final list
  --remove-constraints  remove constaints (-c) from the final list
  --remove-vcs          remove vcs requirements from the final list
  --remove-wheel        remove wheel requirements from the final list
  --remove-unversioned  remove requirements without a version number from the final list
  --remove-index-urls   remove -i entries (index urls) from the final list
Package: pip-package-template-docker
pip-package-template-dockerProject template for Dockerized pip package development.OverviewThis project is fully Dockerized. For convenience, aMakefileis provided to build/test during development.Python 3.11 is the primary version for development, while 3.7 - 3.10 are included for compatibility. You may want to change them in the future.
Seedocker-compose.ymlandMakefile.
Refer tothis pagefor Python versions you may want to support.Linting is done usingflake8and testing is done usingpytest.CI is designed for GitHub Actions. See.github. Coverage is reported toCoveralls.An automatic release to Pypi is made through GitHub Actions whenever you publish a new release on GitHub.LICENSEin the template is MIT.How to usePlease familiarize yourself with all the concept involved. I am not responsible for things breaking if you use this template.Python and different Python versionsCreating pip packages. I made a tutorial a few years ago, which you can seehere.Docker and docker-composeLinting and flake8Unit testing and pytestCI and GitHub ActionsCode coverageFind all instances ofpip-package-template-dockerand replace them with your desired package name.
This is thenameof your package known to Pypi andpip install.Rename thesrc/pip_package_template_dockerfolder.
Find all instances ofpip_package_template_dockerand replace them accordingly.
This is what yourimportstatement would use in Python code.Go throughsrc/setup.pyand make necessary changes. Please do not link your project to my name, email, or GitHub.ReplaceREADME.mdwith your own. If you would like to use the badges, please change the links to point to your project.ReplaceLICENSEwith your own. Please do not license your project under my name.Project version is found in the__init__.pyfile in your package.
Update it accordingly as you develop your package.Put unittests undersrc/tests.Sign up for necessary accounts, such asPypiandCoveralls.Acquire a Pypi token and put it under your project asPYPI_API_TOKEN.
On Pypi it is found under Account settings -> API tokens -> Add API token.
On GitHub it is located in your project settings -> Security -> Secrets and variables -> Repository secrets.
You may need to manually update once before a project-specific token can be acquired.
Package: pip-packaging
Pip packaging process1 - verify environnentpython -V
  Python 2.7.17

python -m pip --version
  pip 19.3.1 from /home/jeec6230/.local/lib/python2.7/site-packages/pip (python 2.7)2 - Install the required packagessudo python -m pip install --upgrade pip setuptools wheel
sudo python -m pip install tqdm
sudo python -m pip install --user --upgrade twine3 - Create an executable file without extension named as your project nametouch pip_packaging
chmod +x pip_packaging4 - Edit this file and type in :#!/usr/bin/env python

echo "hey there, this is my first pip package"5 - Create a setup file setup.pyIt will contain all your package metadata information.import setuptools

with open("README.md", "r") as fh:
    long_description = fh.read()


setuptools.setup(
    name='pip_packaging',  
    version='0.1',
    scripts=['pip_packaging'] ,
    author="Firstname Lastname",
    author_email="firstname.lastname@somwhere.org",
    description="Pip packaging tutorial package",
    long_description=long_description,
long_description_content_type="text/markdown",
    url="https://github.com/fnlastname/pip_packaging",
    packages=setuptools.find_packages(),
    classifiers=[
        "Programming Language :: Python :: 3",
        "License :: OSI Approved :: MIT License",
        "Operating System :: OS Independent",
    ],
)6 - Compile your packageWhile in your repository execute the following command :python setup.py bdist_wheel
Package: pippi-lang
Text cleaning PipelineDescriptionThis code contains a pipeline for pre-processing text data for sentiment analysis. It includes steps for removing stop words, HTML tags, changing letter size, and removing punctuation.Future code will include text-transformations like word-embedding and word-vectorization.ExampleElegant data pipelines are a key component of any data science project. They allow you to automate the process of cleaning, transforming, and analyzing data. This code is a simple example of how to create a pipeline for text data using cutom transformers and the sklearn Pipeline class.frompippiimport(TransformLettersSize,RemoveStopWords,Lemmatize,RemovePunctuation,RemoveHTMLTags,)fromsklearn.pipelineimportPipelineimportpandasaspdpipeline=Pipeline(steps=[("remove_stop_words",RemoveStopWords(columns=["review","sentiment"])),("remove_html_tags",RemoveHTMLTags(columns=df.columns.to_list())),("uppercase_letters",TransformLettersSize(columns=["sentiment"],case_transform="upper")),("remove_punctuation",RemovePunctuation(columns=["review"])),])output=pipeline.fit_transform(df)df=pd.DataFrame(output,columns=["review","sentiment"])Pipeline Visualization:[RemoveStopWords] -> [RemoveHTMLTags] -> [TransformLettersSize] ->   [RemovePunctuation]
Package: pip-pin
THIS IS AN EXPERIMENT. PLAY WITH IT, THINK ABOUT IT, DON'T USE IT ON PRODUCTION.Let me know what you think.pip pinSpecify and pin dependencies fromsetup.py.TL;DR;fromsetuptoolsimportfind_packages,setupsetup(name='meriadok',version='1.0.',packages=find_packages(),setup_requires=['pip-pin',],install_requires=['flask',],tests_require=['pytest',],develop_requires=['black',],)Non-pinned dependencies:Just install whatever you want withpip.PinningThis will produce (or update).pip-pindirectory, which you are supposed to commit into the repo.$ ./setup.py pin [(--install|--tests|--develop)]Note that this will pinonlythings listed in a respectivesetup.pysection. This means you can have additional stuff installed on your local
virtualenv, and noone is going to care until you make it a dependency.Pinned dependencies:Installing pinned dependencies:$ ./setup.py sync [(--install|--tests|--develop)]
Package: pippin-naco
PIPPIN(PDIpipeline forNACO data) is a pipeline capable of reducing the polarimetric observations made by the VLT/NACO instrument. It applies the Polarimetric Differential Imaging (PDI) technique to separate the polarised, scattered light from the (largely) un-polarised, stellar light. As a result, circumstellar dust can be uncovered.Documentation can be found athttps://pippin-naco.readthedocs.ioA comprehensive archive of the PIPPIN-reduced NACO data products can be found atarchive. There, we have published our reductions of potential young systems observed with NACO’s polarimetric configurationpaper-citation.If you use PIPPIN or PIPPIN-reduced data products from the archive for your publication, pleasecite our paper.PIPPIN is distributed under the MIT License (for terms and conditions, seeLICENSE).Copyright (C) 2023 Sam de Regt
Package: pip-plant
plantSimplified Package Management for PythonPlant is a simplified package manager for your Python projects.Programmers have routinely complained aboutpipnot being as elegant asnpmwhen it comes to installing dependencies. For example, withpip, one
has to always specify arequirements.txtfile for installing the packages
needed for a project. This is an inconvenience, especially when compared tonpm, which has an elegant commandnpm installto install all the
dependencies mentioned in the project'spackage.jsonby default.Withplant, Python programmers, especially the lazy ones (i.e. the good
ones) don't have to face this inconvenience. This packages boils all of the
hassle down to$ pip-plant, which simply installs all the dependencies
mentioned in your project'srequirements.txt.Usage$ pip-plant
Requirements detected!
Found 10 dependencies. Please wait, installing!
... [standard pip output] ...
All dependencies installed!That's basically it.Installation$ pip install pip-plantThis isn't the only problemplantsolves. More features coming soon include
automatic requirements file updation, dependency stats (i.e. dependency usage
proportions measurement in your project) and much more!
Package: pipplus
pipplusAn enhancement for pip that enables npm type commands for your python project.Works with Python 3.6+CommandsCurrently supportsnpm run ...type commands for scripts setup in the pyproject.toml file like so:[tool.pipplus.scripts]autopep8="autopep8 -i -r -vv ."pipplus works either with thepippluscommand or theppmcommand for ease of transition for those used to npm:$> ppm run autopep8
pipplus run autopep8 => "autopep8 -i -r -vv ."
enable pyproject.toml config: key=max_line_length, value=120
[file:setup.py]
...OS dependant scripts are also possible (where pipplus will determin the correct script per run based onos.name):[tool.pipplus.scripts]autopep8="autopep8 -i -r -vv ."[tool.pipplus.scripts.clean]nt="del /Q /Y build"posix="rm -rf build"TODOinitinstall(including save and save-XXX)uninstallupdateOther commands (hoping to have a full superset of pip and npm type commands if possible)
Package: pip-pop
Working with lots ofrequirements.txtfiles can be a bit annoying.
Have no fear,pip-popis here!(work in progress)Planned Commands$pip-diff[--fresh|--stale]<reqfile> <reqfile>Generates a diff between two given requirements files. Lists either stale or fresh packages.$pip-grep<reqfile><package>...Takes a requirements file, and searches for the specified package (or packages) within it.
Essential when working with included files.Possible Future CommandsInstall with blacklisting support (wsgiref, distribute, setuptools).
Package: pip-ppm
A shameless clone of npm for managing python packages.Do not take this project seriouslyit's just apip installcommand with some features for personal needs.Installationpip install pip-ppmrequirements.json file initializationppm initppm initcommand creates a file contains:{
  "name": "test",
  "version": "1.0.0",
  "description": "",
  "author": "",
  "license": "ISC",
}Install a package and save to the requirements.json fileppm install flask --save
ppm install flask==1 --save
ppm install flask ipython --saveWhen you useppm installcommand with--saveflag,
it's saving installed packages to therequirements.jsonfile{   
    ...
    "requirements": {
        "django": "2",
        "djangorestframework": ""
    }
}Install packages pre-defined in requirements.json fileppm install
...
Successfully installed django-2.0 djangorestframework-3.10.3Available commandsUsage: ppm [OPTIONS] COMMAND [ARGS]...

Options:
  --help  Show this message and exit.

Commands:
  init       Initializes requirements.json file
  install    Installs given package[s]
  uninstall  Uninstalls given package[s]
  dump       Dumps requirements.json file to `pip freeze` format
Package: pip-preserve-requirements
pip-preserve-requirementsPreserve pinned PIP requirements in repositories you control.It ensure pinned git references in pip requirements files are pushed to a repo you
control, and have a tag associated with the commit, so they are preserved from garbage
collection.Table of Contentspip-preserve-requirementsInstallationUsageConfigurationLimitationsLicenseInstallationpipx install pip-preserve-requirementsUsageUsage: pip-preserve-requirements [OPTIONS] REQUIREMENTS_FILE...

  Ensure pinned VCS references in pip requirements files have a git tag.

Arguments:
  REQUIREMENTS_FILE...  The requirements files to look for requirements tag.
                        [required]

Options:
  --tag-prefix TEXT               The prefix to use when creating git tag
                                  names.  [default: ppr-]
  --match-any-tag                 Whether to consider that any tag on the
                                  commit is sufficient. If not, ensure commits
                                  are tagged with the requested prefix.
  -r, --project-root DIRECTORY    The project root directory. Default options
                                  and arguments are read from pyproject.toml
                                  in this directory.  [default: .]
  --install-completion [bash|zsh|fish|powershell|pwsh]
                                  Install completion for the specified shell.
  --show-completion [bash|zsh|fish|powershell|pwsh]
                                  Show completion for the specified shell, to
                                  copy it or customize the installation.
  --help                          Show this message and exit.Configurationpip-preserve-requirementsis configured in a dedicated section ofpyproject.toml:Example:[tool.pip-preserve-requirements]tag_prefix="ppr-"# ensure a tag with the above prefix is present, if true, consider any tag is validmatch_any_tag=false[[tool.pip-preserve-requirements.vcs_vaults]]# any git provider which accepts URLs of the form https://host/owner/repo# or ssh://git@host/owner/repoprovider="github.com"owner="acme"# set to true for private reposssh_only=false# the vault where to push VCS referencedefault=trueLimitationsAt the moment, onlygit+httpsandgit+sshURLs are supported.The following improvements would be considered in scope, although there is no current
plan to work on them:supporting other VCS (such ashg);supporting non-VCS URLs, by pushing them to a user-controlled server;supporting regular requirements, by pushing them to a user-controlled index.Licensepip-preserve-requirementsis distributed under the terms of theMITlicense.
Package: pippt
Pi-pptPi-ppt is a simple presentation module based on Tkinter. The goal is to provide
a new experience of creating a presentation by programming.BuildDependencies:Requires a Tkinter module.$ apt-get install python3-tk$ apt-get install python3-pil python3-pil.imagetkInstallation:Install using pip.direct install$ pip3 install pipptorclone and install$ cd Pi-ppt$ pip3 install .Command Usage:Generates a sample format of code under given slide namepi-ppt --init <slide_name>DesignThe Pi-ppt module is based tkinter. This module contains four classesPipptadd_title_slideadd_slideadd_split_slideMain window: [Pippt]This class maintains the root window showing slides in the form of frames.
This class has abundlemethod which uses to bundle all the slides(frames)
into the root window.app = Pippt()app.bundle(frame_1, frame_2,...)Frames: [add_title_slide,add_slide,add_split_slide]These class maintains the each frame(slides) with their method. Methods
available in different class as metioned below.,title-add_title_slide,add_slide,add_split_slidesubtitle-add_title_slidecontent-add_slide,add_split_slideimage-add_slide,add_split_slidecodeblock-add_slideFeatures:Each frame has arguments likefont style, color, align and justifywhich
is set to the default that can be customizable too.Image and codeblocksizecan be changed accordingly.Auto line wrappingSample run:$ pi-ppt --init new_slide$ cd new_slide/$ python3 new_slide.pyOutput:
Package: pippurge
Enhancement for pip uninstall command, that it removes all dependencies of an uninstalled package.QuickstartUninstall package, e.g, flask:$ pippurge flask -yUninstall multiple packages, e.g, flask, requests:$ pippurge flask requests -yInstallationYou can install “pippurge” via pip fromPyPI:$ pip install pippurgeUsage$ pippurge --help
usage: pippurge [-h] [-y] packages [packages ...]

Uninstall packages with all its dependencies.

positional arguments:
  packages    some packages

optional arguments:
  -h, --help  show this help message and exit
  -y, --yes   don't ask for confirmation of uninstall deletions.