Saravanan666/pypi-org huggingface dataset:
Package: wheat_sample_app
Getting StartedChange directory into your newly created project.cd wheat_sample_appCreate a Python virtual environment.python3 -m venv envUpgrade packaging tools.env/bin/pip install –upgrade pip setuptoolsInstall the project in editable mode with its testing requirements.env/bin/pip install -e “.[testing]”Configure the database.env/bin/initialize_wheat_sample_app_db development.iniRun your project’s tests.env/bin/pytestRun your project.env/bin/pserve development.ini0.0Initial version.
Package: wheat-yield-prediction-toolkit
Wheat Yield Prediction ToolkitAre you interested in predicting winter wheat yield in your area? Look no further! The Wheat Yield Prediction Toolkit is a collection of tools for gathering and processing data from various sources to help you make informed predictions about winter wheat yield.OverviewThe Wheat Yield Prediction Toolkit includes several modules for collecting data from different sources:USDA Quick Stats API for yield dataGee for remote sensingSoilGrids for soil data imagesNASA POWER provider for weather dataThis README will guide you through the steps to set up and use the toolkit. Let's get started!
Package: whecho
whecholinux echo but with webhooks! ⚓Don't guess when a job is finished! Have it message you!requirementspython 3.6+installationpip install whechoFirst Time Setupobtain a webhook URLCurrently supports:discordslackwebex(with markdown)Initialize thedefault_url$ whecho --init
Current config:
[1] default_url: None
[2] user: craut
[3] machine: craut-spectre

Please enter the number/name of the config option you would like to modify (empty or Q to exit): 1
Please enter the new value for default_url: <WEBHOOK_URL>
Successfully modified default_url to <WEBHOOK_URL>!
Current config:
[1] default_url: <WEBHOOK_URL>
[2] user: craut
[3] machine: craut-spectre

Please enter the number/name of the config option you would like to modify (empty or Q to exit): q
Successfully initialized whecho!general usage (from shell/console)$ whecho "hello there"usage from pythonfrom whecho.whecho import whecho_simple
whecho_simple("I'm inside python 🐍")advanced usage$ whecho --help
usage: whecho [-h] [--version] [-m MSG] [--init] [-u URL] [-d] [MSG [MSG ...]]

Linux echo with webhooks! ⚓

positional arguments:
  MSG                The message to echo.

optional arguments:
  -h, --help         show this help message and exit
  --version          Prints the version of whecho and exits.
  -m MSG, --msg MSG  The message to echo (same as 1st positional argument).
  --init             Initializes whecho. Also used to change current config.
  -u URL, --url URL  The webhook URL to send the message to.
  -d, --debug        Whether to print debugging information.
Package: whedon
# Whedon Python[![PyPI version](https://badge.fury.io/py/whedon.svg)](https://badge.fury.io/py/whedon)[![CircleCI](https://circleci.com/gh/openbases/whedon-python.svg?style=svg)](https://circleci.com/gh/openbases/whedon-python)![docs/img/robot.png](https://github.com/openbases/whedon-python/raw/master/docs/img/robot.png)-------------------------------------------------------------------------------This is a small module with helper functions for using Whedon. Please contribute at[openbases/python-whedon](https://www.github.com/openbases/whedon-python) onGithub.> Just... no!![docs/img/whedon-before.png](https://github.com/openbases/whedon-python/raw/master/docs/img/whedon-before.png)> Better!![docs/img/whedon-upgrade.png](https://github.com/openbases/whedon-python/raw/master/docs/img/whedon-upgrade.png)# Quick StartTo install```bashgit clone https://www.github.com/openbases/whedon-pythoncd whedon-pythonpython setup.py install``````pip install whedon```And then use:```bash$ py-whedon helpWhedon Python [v0.0.0]usage: py-whedon [--debug] [--quiet] [--version] sep general usage ...Whedon Pythonpositional arguments:sep            separator for printing lists, etc. (default ,)optional arguments:--debug, -d    use verbose logging to debug.--quiet, -q    suppress all normal output--version      show whedon python versionactions:actions for py-whedongeneral usage  descriptionpaper        extract values from a paper.mdshell        start an interactive shell with whedon```For complete usage, please see:- [usage documentation](https://openbases.github.io/whedon-python/html/usage.html)- [documentation](https://openbases.github.io/whedon-python/)- implementation in [whedon docker](https://www.github.com/openbases/whedon/).Have fun!
Package: wheel
This library is the reference implementation of the Python wheel packaging
standard, as defined inPEP 427.It has two different roles:Asetuptoolsextension for building wheels that provides thebdist_wheelsetuptools commandA command line tool for working with wheel filesIt should be noted that wheel isnotintended to be used as a library, and
as such there is no stable, public API.DocumentationThedocumentationcan be found on Read The Docs.Code of ConductEveryone interacting in the wheel project’s codebases, issue trackers, chat
rooms, and mailing lists is expected to follow thePSF Code of Conduct.
Package: wheel2deb
wheel2debwheel2debis a python wheel to debian package converter. It takes a list of wheels as input and produces a list of debian binary CPython packages (those prefixed with python- or python3-).Quick ExampleThe following shows how to convert numpy and pytest, along with their dependencies into a list of debian packages:# Download (and build if needed) pytest, numpy and their requirementspip3wheelpytestnumpy# Convert all wheels to debian source packages, build them with dpkg-buildpackagewheel2deb
ls-loutput/*.deb# Install generated packagesdpkg-ioutput/*.deb# Run pytest on numpypython3-c"import numpy; numpy.test()"Project scopePython 2.7 and 3CPython only for nowsupport for non pure python wheelssupport debian architectures all, armhf, amd64, i686tested on jessie, stretch, buster so far, ubuntu should also workRequirementswheel2debusesapt-cacheto search for debian packages,dpkg-shlibdepsto calculate shared library dependencies andapt-fileto search packages providing shared library dependencies.wheel2deb buildrequires the usual tools to build a debian package:aptupdate
aptinstallapt-filedpkg-devfakerootbuild-essentialdevscriptsdebhelper
apt-fileupdateIf you want to cross build packages for ARM, you will also need to installbinutils-arm-linux-gnueabihf.Converting pure python wheels, don't actually requires apt-file and dpkg-dev.Keep in mind that you should only convert wheels that have been built for your distribution and architecture. wheel2deb will not warn you about ABI compatibility issues.InstallationFrom the release pagewheel2debis packaged as a single binary application that you can download from the release page. Using those releases will spare you the hassle of building Python 3.10 on old Debian based distributions.Withwakemeopssudoapt-getinstallwheel2debWith dockerWe currently do not build docker images withwheel2debpre-installed. You can use wakemeops docker images to quickly play withwheel2debon a different distribution than your host.dockerrun-tiwakemeops/debian:busterAnd in the container run:install_packages wheel2debWithpipxwheel2debis available frompypi:pipxinstallwheel2debFeaturesguess debian package names from wheel names and search for them in the cachesearch packages providing shared library dependencies for wheels with native codehandle entrypoints and scripts (those will be installed in /usr/bin with a proper shebang)try to locate licence files and to generate a debian/copyright fileUsageUsewheel2deb convert --helpandwheel2deb build --helpto check all supported options.DevelopmentYou will needpoetry, and probablypyenvif you don't have python 3.10 on your host.poetryinstallTo run wheel2deb test suite run:poetryruntaskcheckTo build a python wheel:poetryrunpoetrybuildBugs/RequestsPlease use theGitHub issue trackerto submit bugs or request features.LicenseCopyright Parkoview SA 2019-2023.Distributed under the terms of theMITlicense, wheel2deb is free and open source software.
Package: wheel-axle
Wheel Axle - Python Wheel enhancement libraryProblembdist_wheeldoes not support symlinks.bdist_wheeldoes not support overwriting in a convenient way:whether the distribution is pure-Pythondistribution ABI tagExtend Python tag override capabilitySolutionWARNING: THIS IS EXPERIMENTAL BETA SOFTWARE. THERE ARE NO WARRANTIES OF ANY KIND. USE AT YOUR OWN RISK.
ADDITIONAL INCLUDED DISCLAIMERS ALSO APPLY.Wheel-Axle (Axle,bdist_axle) is a drop-in replacement/augmentation utility forwheel(bdist_wheel)
that extends and builds spec-compliant wheels.During the build,Axleis able to capture and record symlinks in the following schema paths (locations):purelibplatlibscriptsheadersdataAdditionally,Axleis able to customize the tags via additional command line options.While the generated wheel is fully spec-compliant, additional symlinks functionality is not possible without its
companion libraryWheel Axle Runtime. Thus, every wheel generated by
thebdist_axleautomatically becomes dependent onwheel-axle-runtimethat provides post-install logic required.ImplementationThe body of the library is as ugly and messy asdistutils/setuptoolsare, and consists of, mainly, in
hacking/overwriting varioussetuptoolscommands to detect, handle and record symlinks and their targets. Once that
problem is solved, the list of symlinks is recorded in the.dist-info/symlinks.txtin the following CSV format:symlink namesymlink targeta boolean (0 or 1) flag indicating whether the target is a directoryNOTE: Symlinks may be relative, absolute and/or broken. Symlink targets are recorded verbatim (even when broken) and
are NOT otherwise interpreted. THIS IS INTENTIONAL. Please
seeWheel Axle Runtime Security Noticefor additional information.A special<distribution name and version>.pthfile is also added to the distribution. When the wheel is installed
this.pthfile triggers the post-install logic viawheel-axle-runtime.Usagepython setup.py bdist_wheel <arguments>can be replaced withpython setup.py bdist_axle <arguments>. The replacement
is drop-in.Additional functionality is available via the following options:--python-tag      Python implementation compatibility tag (default: 'py3')
  --root-is-pure    set to manually override whether the wheel is
                    pure (default: None)
  --abi-tag         set to override ABI tag (default: None)Using--python-tag,--root-is-pureand--abi-tagallows you to create wheels that carry platform-dependent data
while otherwise containing pure-Python libraries.
Package: wheelbin
wheelbinwheelbinreceives a wheel file and returns its compiled version,
i.e. an equivalent wheel file with the Python files substituted with
their corresponding Python bytecode files.The output wheel filename reflects this compilation by fixing the Python
implementation, ABI and target architecture, and it replaces the.whlextension with.bin.whl.Additionally, Python files can be excluded from compilation by passing a
wildcard expression to the--excludeoption.wheelbinis a package forked from the originalpycwheelby
Grant Patten.UsageFor example, given a wheel fileyour_wheel-1.0.0-py3-none-any.whlandwheelbininstalled on a GNU/Linux distribution under Python 3.7:$wheelbinyour_wheel-1.0.0-py3-none-any.whl# Output: your_wheel-1.0.0-cp37-cp37m-linux_x86_64.bin.whl
Package: wheelcms_comments
WheelCMS comments=================![Build status](https://travis-ci.org/wheelcms/wheelcms_comments.png)This package provides support for simple (local) comments on WheelCMS content.It's similar to the[wheelcms_disqus package](https://github.com/wheelcms/wheelcms_disqus/), but doesnot require an external service.Installation------------Add wheelcms_comments to your INSTALLED_APPS *before* the wheelcms_axle package, e.g.INSTALLED_APPS = ("wheelcms_comments",..."wheelcms_axle",)if your base definition of INSTALLED_APPS is out of your direct control(e.g. when using[wheelcms_project](https://github.com/wheelcms/wheelcms_project)), trysomething like this:INSTALLED_APPS = ("wheelcms_comments",) + INSTALLED_APPSwheelcms_comments uses [django-simple-captcha](https://django-simple-captcha.readthedocs.org/en/latest/usage.html), so you will need to include thisas well:Addfrom django.conf.urls.defaults import *urlpatterns += patterns('',url(r'^captcha/', include('captcha.urls')),)to your urls.py. Like with the INSTALLED_APPS, make sure the captchapattern matches *before* the base patterns or else the WheelCMS patternswill intercept the /captcha requests.django-simple-captcha  depends on the PIL library. You may need to install "python-imaging" or Pillow depending on your OS/Distribution. You will also need FreeType support with your PIL.Lastly, add 'captcha' to your INSTALLED_APPSUsing comments--------------Now you should be able to enable commenting in your site's settings (savethe settings the first time, it may show incorrectly that comments arealready enabled).You can also enable/disable comments on a per-content basis.New contents will be created as WheelCMS content (content type Comment)with an initial state 'pending'. You can use the workflow dropup in thetoolbar to moderate pending comments.Upgrade notes-------------pre 0.2 users should fake migrate the first migration:manage.py migrate wheelcms_comments 0001 --fake
Package: wheel-doctor
wheel-doctorEasily manipulate METADATA in python wheels and tarballsIntended purposeThe main goal of this tool is to remove references to other packages specified as path dependencies, which will be present in some cases (e.g. building packages in monorepos). Partially inspired by:https://gitlab.com/gerbenoostra/poetry-monorepoUsageShow a table of dependencies specified in a package:> wheel-doctor show-dependencies dist/package-1.0.0-py3-none-any.whl

┏━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Dependency  ┃ Version                                                           ┃
┡━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ numpy       │ <none>                                                            │
│ loguru      │ <none>                                                            │
│ xarray      │ <none>                                                            │
│ my-package  │ @ file:///home/user/my-package                                    │
└─────────────┴───────────────────────────────────────────────────────────────────┘Overwrite a specific dependency> wheel-doctor replace-dependency-version dist/package-1.0.0-py3-none-any.whl my-package "" --verbose

dist/package-1.0.0-py3-none-any.whl
Updating dependency my-package: Replacing version '@ file:///home/user/my-package'
with version '<none>'
Updated dependencies:
┏━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Dependency  ┃ Version                                                           ┃
┡━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ numpy       │ <none>                                                            │
│ loguru      │ <none>                                                            │
│ xarray      │ <none>                                                            │
│ my-package  │ <none>                                                            │
└─────────────┴───────────────────────────────────────────────────────────────────┘Removing all path dependencies> wheel-doctor remove-path-dependencies dist/package-1.0.0-py3-none-any.whl my-package --verbose

dist/package-1.0.0-py3-none-any.whl
my-package: Removing path dependency '@ file:///home/user/my-package'
Updated dependencies:
┏━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Dependency  ┃ Version                                                           ┃
┡━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ numpy       │ <none>                                                            │
│ loguru      │ <none>                                                            │
│ xarray      │ <none>                                                            │
│ my-package  │ <none>                                                            │
└─────────────┴───────────────────────────────────────────────────────────────────┘
Package: wheeler.blink
#blink#This project demonstrates how an Arduino sketch may be distributed as a Python package.## Programming sketch usingarduino_helpersandavr_helpers##Although not strict dependencies of theblinkpackage, by using
[arduino_helpers][1] and [avr_helpers][2], we can easily flash the compiled.hexfirmware files included in theblinkpackage.For example:>>> import blink
>>> board = 'diecimila'
>>> firmware = blink.get_firmwares()[board][0]
>>> firmware.name
path('blink.hex')
>>> from arduino_helpers.context import ArduinoContext, Board, Uploader
>>> # For Ubuntu systems, Arduino IDE is installed at `/usr/share/arduino`.
>>> context = ArduinoContext('/usr/share/arduino')
>>> uploader = Uploader(Board(context, board))
>>> from avr_helpers import AvrDude
>>> # Automatically select port, by iterating through available serial
>>> # ports until a connection can be established.
>>> avr_dude = AvrDude(uploader.protocol, uploader.board_context.mcu, uploader.speed)
>>> stdout, stderr = avr_dude.flash(firmware, ['-D'])
>>> print stderravrdude-x64: AVR device initialized and ready to accept instructionsReading | ################################################## | 100% 0.00savrdude-x64: Device signature = 0x1e9406
avrdude-x64: reading input file “blink.hex”
avrdude-x64: writing flash (1056 bytes):Writing | ################################################## | 100% 0.76savrdude-x64: 1056 bytes of flash written
avrdude-x64: verifying flash memory against blink.hex:
avrdude-x64: load data flash data from input file blink.hex:
avrdude-x64: input file blink.hex contains 1056 bytes
avrdude-x64: reading on-chip flash data:Reading | ################################################## | 100% 0.67savrdude-x64: verifying …
avrdude-x64: 1056 bytes of flash verifiedavrdude-x64 done.  Thank you.[1]:https://github.com/wheeler-microfluidics/arduino_helpers[2]:https://github.com/wheeler-microfluidics/avr_helpers
Package: wheeler.pygtkhelpers
# Note #This project is a fork of [this project][1], written by Ali Afshar
<aafshar@gmail.com>.# Description #PyGTKHelpers is a library to assist the building of PyGTK applications. It is
intentionally designed to benon-frameworky, and blend well with your
particular style of PyGTK development.PyGTKHelpers provides a number of widespread features including: View
delegation, MVC, mixed GtkBuilder/Python views, widget proxying, signal
auto-connection, object-base lists and trees, a number of helper widgets,
utility functions for assisting creating new GObject types, unit testing
helpers and utilities to help debug PyGTK applications.[1]:https://pythonhosted.org/pygtkhelpers/
Package: wheeler.signal_generator_board_rpc
#signal_generator_board_rpc#This project provides a RPC interface for a signal-generator board design based
on the [ATMEGA328][1] processor _(the processor used in the Arduino
[Uno][2])_.  The RPC interface is based on the [arduino_rpc][3] project.# API Example #Below, we show an example session interacting with the signal-generator board
through a serial stream.>>> from signal_generator_board_rpc import SignalGeneratorBoard
>>> s = SignalGeneratorBoard(‘/dev/ttyUSB0’)free memory: 191
>>> s.
s.config_version               s.ram_free                     s.set_waveform_voltage
s.forward_i2c_request          s.set_hf_amplitude_correction  s.vout_pk_pk
s.i2c_address                  s.set_i2c_address              s.waveform_frequency
s.load_config                  s.set_pot                      s.waveform_voltage
s.pot                          s.set_waveform_frequency
>>> s.wave
s.waveform_frequency  s.waveform_voltage
>>> s.waveform_frequency()
1000.0
>>> s.waveform_voltage()
0.0
>>> s.set_waveform_frequency(frequency=1000.1010)
<signal_generator_board_rpc.protobuf_commands.SetWaveformFrequencyResponse object at 0x7f477cb446e0>
>>> s.waveform_frequency()
1000.1010131835938
>>> s.set_waveform_voltage(vrms=1.01)
0
>>> s.waveform_voltage()
1.0099999904632568
>>> hex(s.i2c_address())
‘0x10’
>>> s.set_i2c_address(address=0x11)
<signal_generator_board_rpc.protobuf_commands.SetI2cAddressResponse object at 0x7f477cb44830>
>>> hex(s.i2c_address())
‘0x11’[1]:http://www.atmel.ca/devices/ATMEGA328.aspx[2]:http://arduino.cc/en/Main/arduinoBoardUno[3]:https://github.com/wheeler-microfluidics/arduino_rpc
Package: wheel-factorize
wheel_factorizeWheel factorization is an improvement of trial division method for
integer factorization. This project is the Python implementation of
wheel factorization.Wikipedia LinkSourceUsagefromwheel_factorizeimportWheelFactorasWFwf=WF(3)# basis sizeprint(wf.factors(10))print(wf.factors(31))print(wf.factors(22222222222))print(wf.is_prime(9999991))
Package: wheelfile
Wheelfile 🔪🧀This library aims to make it dead simple to create a format-compliant.whl
file (wheel). It provides an API comparable tozipfile. Use this if you wish
to inspect or create wheels in your code.For a quick look, see the example on the right, which packages the wheelfile
module itself into a wheel 🤸.What's the difference between this andwheel?"Wheel" tries to provide a reference implementation for the standard. It is used
by setuptools and has its own CLI, but no stable API. The goal of Wheelfile is
to provide a simple API.Wheelfile does not depend on Wheel.AckonwledgementsThanks toPaul Moorefor providinghis gistof basic metadata parsing logic, which helped to avoid many foolish mistakes
in the initial implementation.pip install wheelfilefromwheelfileimportWheelFile,__version__spec={'distname':'wheelfile','version':__version__}requirements=['packaging ~= 20.8''zipfile38 ; python_version<"3.8"']withWheelFile(mode='w',**spec)aswf:wf.metadata.requires_dists=requirementswf.write('./wheelfile.py')# 🧀