Saravanan666/pypi-org huggingface dataset:
Package: colcon-coveragepy-result
colcon-coveragepy-resultAcolconextension for collectingcoverage.pyresults.UsageBuild packages with coverage, e.g. using acolcon mixinforcoverage$colconbuild--mixincoverage-pytestTest packages with coverage, again using a mixin$colcontest--mixincoverage-pytestCollect coverage results$colconcoveragepy-resultOpen HTML report, which by default is undercoveragepy/htmlcov/OptionsPrint coverage reports for each package and a combined coverage report of all packages$colconcoveragepy-result--verboseProvide additional arguments for reports generation, e.g. to show lines without coverage$colconcoveragepy-result--coverage-report-args-mProvide additional arguments for HTML report generation, e.g. to skip files with no code$colconcoveragepy-result--coverage-html-args--skip-emptyFor more options$colconcoveragepy-result--helpContributingSee:Contributionsfor guidelinesBootstrap from sourceto test the package from source
Package: colcon-gradle
colcon-gradleAn extension forcolcon-coreto supportGradleprojects.FeaturesFor all packages withbuild.gradlefiles:colcon buildwill callgradle assemblecolcon testwill callgradle testGradle wrappers will be used if present.Try it outUsing pippip install -U colcon-gradleFrom sourceFollow the instructions athttps://colcon.readthedocs.io/en/released/developer/bootstrap.html, except in "Fetch the sources" add the following tocolcon.repos:colcon-gradle:type:giturl:https://github.com/colcon/colcon-gradle.gitversion:mainAfter that, run thelocal_setupfile, build any colcon workspace with Gradle projects in it, and report any issues!
Package: colcon-installed-package-information
Extensions forcolcon-coreto inspect packages which have already been installed.OverviewThese colcon extensions provide a mechanism which can be used for getting information about packages outside of the workspace, which have already been built and installed prior to the current operation.
In general, it works similarly to and is based on thePackageDiscoveryExtensionPointandPackageAugmentationExtensionPointextensions provided bycolcon-core.DifferencesInstalled packages don’t generally have a single directory which stores the package content and metadata.
This set of extensions store the “prefix” under which the package resides rather than the package directory (e.g.~/workspace/installinstead of~/workspace/install/share/<package_name>or~/workspace/src/<package_name>), meaning many packages will likely share the samepathattribute value.Recursively crawling an entire system or even selective subdirectories to look for installed packages could be very slow, so this process also deviates from the Discover -> Identify -> Augment pipeline used incolcon-core.
Rather than attempting identification on prospective package locations, the discovery phase generally loads a list of installed packages from a database of some kind, such as the file-based colcon index.
In some cases, the database might already populate sufficient information on the descriptor to identify the package.
For others, only presence can be known, and augmentation extensions must add additional information to the descriptor by searching for specific files throughout the prefix directory.Thetypeattribute of an installed package works similarly to workspace packages, but must always start withinstalled.followed by a more specific package type.
If more information about a package cannot be determined and it is known only to exist under a certain prefix, thetypeshould be set toinstalled.Supported Package TypesThis package provides extensions which are able to discover packages using thePrefixPathExtensionPointto enumerate install prefixes, andFindInstalledPackagesExtensionPointto enumerate names of packages installed under those prefixes.
It can then use the colcon index in those prefixes as well as python eggs to determine dependency information and augment the packages appropriately.Support for more package databases for discovery and augmentation can be added by other packages by implementing and registering appropriate extensions.
Package: colcon-lint
# colcon-lintColcon extension for linting ROS package dependencies.This package is an extension of [colcon-core](https://github.com/colcon/colcon-core). Similar to [catkin-lint](https://github.com/fkie/catkin_lint) in ROS, it checks whether the dependencies of ROS2 packages are correctly described in thepackage.xml.## InstallationTo use this extension, please execute the following:`bash sudo apt installapt-rdependspip installcolcon-lint`## How to usePlease execute as follows. The package specification option is the same as other colcon commands.`bash colcon lint--packages-select<package-name>`Replace<package-name>with the name of the package you want to check.### OptionsOption | Description |— | — |package specification options | The same as other colcon commands. |logging options | The same as other colcon commands. |–quick| This option only checks for directly declared dependencies in the package.xml. It cannot detect dependencies that are resolved through recursively declared packages. |## TipsTo run faster, you can build with the-Wno-dev –trace-expand –trace-redirect=trace.logcmake option.`bash colcon build--cmake-args-Wno-dev--trace-expand--trace-redirect=trace.log`
Package: colcon-meson
colcon-mesonA colcon extension for buildingMesonpackages.Install from the Python Package Index via:pipinstallcolcon-mesonPassing Meson argumentsArguments can be passed tomeson setupvia--meson-args:set build options defined inmeson_options.txt:colconbuild--packages-select$PACKAGE--meson-args\-D$ARG1=$PARAM1\-D$ARG2=$PARAM2set the build type:colconbuild--packages-select$PACKAGE--meson-args\--buildtype=debugoptimizedSeemeson setup -hfor a detailed list of arguments.
Package: colcon-ros-bazel
[![Travis CI](https://travis-ci.org/colcon/colcon-ros-bazel.svg?branch=master)](https://travis-ci.org/colcon/colcon-ros-bazel)
[![AppVeyor](https://ci.appveyor.com/api/projects/status/github/colcon/colcon-ros-bazel?svg=true&branch=master)](https://ci.appveyor.com/project/Theosakamg/colcon-ros-bazel)
[![codecov](https://codecov.io/gh/colcon/colcon-ros-bazel/branch/master/graph/badge.svg)](https://codecov.io/gh/colcon/colcon-ros-bazel)
[![PyPI version](https://img.shields.io/pypi/v/colcon_ros_bazel.svg)](https://pypi.python.org/pypi/colcon_ros_bazel/)An extension for [colcon-core](https://github.com/colcon/colcon-core) to support ROS2 Bazel projects.
Package: colcon-ros-domain-id-coordinator
An extension forcolcon-coreto coordinate different DDSdomain IDsfor concurrently running tasks.The current implementation of this package cycles through all of the non-default ROS 2 domain IDs that should be available on a platform given that it has no special network configurations.
It does not track which task uses the domain IDs and therefore does not eliminate the possibility of a collision, but drastically reduces the likelihood that two tasks end up using the same domain ID.
Package: colcon-ros-gradle
colcon-ros-gradleAn extension forcolcon-coreto supportROS 2 Gradleprojects.Try it outUsing pippip install -U colcon-ros-gradleFrom sourceFollow the instructions athttps://colcon.readthedocs.io/en/released/developer/bootstrap.html, except in "Fetch the sources" add the following tocolcon.repos:colcon-ros-gradle:type:giturl:https://github.com/colcon/colcon-ros-gradle.gitversion:mainAfter that, run thelocal_setupfile, build any colcon workspace with Gradle projects in it, and report any issues!
Package: colcon-spawn-shell
IntroductionThis is acolconplugin to chain workspaces in new shells.
It allows quickly un-chaining workspaces by exiting the spawned shell.The shell’s prompt is edited to show the workspace order.
The only supported shell isbash.Quick StartOptional:Create and source a virtual environment.python3-mvenvenv.env/bin/activateFrom PipDownloadcolcon-spawn-shellfrom pip.pipinstallcolcon-spawn-shellBuild the colcon workspace you would like to spawn in a new shell.cdmy_cool_workspacecolconbuildSourcespawn_shell.bashto activate the workspace..install/spawn_shell.bashFrom SourceNoteIt’s recommended to install to a virutal environment for development.
Seethis tutorialfor more information.Download the source code forcolcon-spawn-shellmkdir-bspawn_shell_ws/srccdspawn_shell_ws/srcgitclonehttps://github.com/colcon/colcon-spawn-shell.gitBuild the workspace using colconcolconbuildSource the workspace.install/local_setup.bashFrom now on future workspaces can be activated by sourcingspawn_shell.bashcdmy_cool_workspacecolconbuild.install/spawn_shell.bashContributingForkthecolcon/colcon-spawn-shellrepository.Follow the“From Source” instructions, except clone your forked repository.Make changes and commit them to a branch.# Creat a branch for your changesgitcheckout-bmy-cool-changes# Make your changes ...gitcommit-m"committing my changes"# Push them to your forkgitpush--set-upstreamoriginmy-cool-changesCreate aPull Requestfrom your branch to the branchdeveloponcolcon/colcon-spawn-shellNotePlease create pull requests from the branchdevelopbecausethis repositoryuses thenvie git branching model.
Package: colda
IntroductionColDA  is an open source project aimed at providing distributed machine learning tools for data analysis and machine learning based onAssisted Learning.PackageGetting StartedUse caseExamples and Instructions can be found inexamples/Package StuctureBasic package structure can be found inGithub repositoryCompared to the Basic package structure,docs/will contain different element. But at this point, you can follow the templatepy-pkgis the main part of the package, you can add more modules (with__init__.py) in this part. For example, if you addtempmodule, you can importtempmodule by:importtempfrompy-pkgThis package structure can be improved by learningPyTorchpackage structure.Basic Structure:py-package-tempate/|--docs/|--|--build_html/|--|--build_latex/|--|--source/|--py-pkg/|--|--__init__.py|--|--__version__.py|--|--curves.py|--|--entry_points.py|--tests/|--|--test_data/|--||--supply_demand_data.json|--|__init__.py|--|conftest.py|--|test_curves.py|--.env|--.gitignore|--Pipfile|--Pipfile.lock|--README.md|--setup.pyHow to Manage Package Environmentpipenvis used to manage package. You can installpipenvby:pip3installpipenvUsepipenvto install package. The first command is to install the package for development. The second command is to install the package for production.pipenvinstall--dev
pipenvinstallUsepipenvto uninstall package:pipenvuninstallPipenv ShellsEntering into a Pipenv-managed shell. Remeber doing thisevery timebefore running the project.cdpy-package-tempate
pipenvinstall
pipenvshellLicenseColDA is licensed under theApache 2.0 License.Code of ConductPlease review and adhere to theCode of Conductwhen contributing to ColDA.ReferencePlease use the following reference@article{diao2022gal,title={GAL: Gradient Assisted Learning for Decentralized Multi-Organization Collaborations},author={Diao, Enmao and Ding, Jie and Tarokh, Vahid},journal={Advances in Neural Information Processing Systems},volume={35},pages={11854--11868},year={2022}}
Package: coldfront
ColdFront - Resource Allocation SystemColdFront is an open source resource and allocation management system designed to provide a
central portal for administration, reporting, and measuring scientific impact
of cyberinfrastructure resources. ColdFront was created to help high performance computing (HPC) centers manage access to a diverse set of resources across large groups of users and provide a rich set of
extensible meta data for comprehensive reporting. The flexiblity of ColdFront allows centers to manage and automate their policies and procedures within the framework provided or extend the functionality withplugins.  ColdFront is written in Python and released under the GPLv3 license.FeaturesAllocation based system for managing access to resourcesSelf-service portal for users to request access to resources for their research groupCollection of Project, Grant, and Publication data from usersCenter director approval system and annual project review processEmail notifications for expiring/renewing access to resourcesAbility to define custom attributes on resources and allocationsIntegration with 3rd party systems for automation, access control, and other system provisioning tasksRead moreCommunity Supported PluginsOpenStack PluginKeycloak User SearchStarfish PluginSubmit a PR to add your plugin to the list above.DocumentationFor more information on installing and using ColdFront see ourdocumentation hereContact InformationIf you would like a live demo followed by QA, please contact us atccr-coldfront-admin-list@listserv.buffalo.edu. You can also contact us for
general inquiries and installation troubleshooting.If you would like to join our mailing list to receive news and updates, please
send an email tolistserv@listserv.buffalo.eduwith no subject, and the
following command in the body of the message:subscribeccr-open-coldfront-list@listserv.buffalo.edufirst_name last_nameLicenseColdFront is released under the GPLv3 license. See the LICENSE file.
Package: cold-postman
cold-postmancold_postmanis a marketing tool to help users write cold mails in markdown and send them via a manageable csv file.Installationpip install cold_postmanInitialize the configpython-mcold_postmaninitdbpython-mcold_postmaninitconfigAboutconfig.yamlbatch_num:10# mails sent per batchpassword:''# passwordsmtp_port:587# portsmtp_server:smtp.example.com# smtp serveruser:'example@example.com'# user mailfrom:'Mr.Example'unsubscribe:link:mailto:example@example.com# The link for List-Unsubscibe.subject:Unsubscribe# The subject if is a mailto link.message:I'd like to unsubscribe.# Default message of the mail.alter_name:''# The alternative name if blank in first_name + last_name.sending_limits:# [Optional], Volume of sending limits. Please refer to the smtp provider.warning:100# [Optional], Warn on every N MB has sent. Default=100.pause:280# [Optional], paused job on N MB has sent. Defaul=290.Aboutcontrol csvControl csv is the receiver list. Columns decribed as below:first_name:  First name of the receiver.last_name:  Last name of the receiver.email:  Receiver's mail address.last_sent: Timestamp of last contact.enabled: (int)[1, 0],1=enabled.0=disabled, which will be skiped while executing.Send MailCommand to start the sending task:# usage: __main__.py [-h] [-c CONFIG] [-d CRMDB] -m MESSAGE -t TITLE -s SIGNATURE [-a ATTACH]# options:#   -h, --help            show this help message and exit#   -c CONFIG, --config CONFIG#                         (Filepath) The file path of the config.#   -d CRMDB, --crmdb CRMDB#                         (Filepath) The file path of the crm DB.#   -m MESSAGE, --message MESSAGE#                         (Filepath) REQUIRED. The email content in markdown.#   -t TITLE, --title TITLE#                         (str) REQUIRED. The email title#   -s SIGNATURE, --signature SIGNATURE#                         (Filepath) REQUIRED. The signature in markdown#   -a ATTACH, --attach ATTACH#                         (Filepath) The attachment.#   -u UNSUBSCRIBE, --unsubscribe UNSUBSCRIBE#                         (Bool) [True, False] Enable a unsubscribe link. Default=True#   -i INTERVAL, --interval INTERVAL#                         (Int) Interval (secs) between batchs. Default=10python-mcold_postman-mmessage.md-t'Subject of the Mail'-ssignature.md-aattachment.zipPrepare a markdown contentThe markdown content is converted to rtf viamarkdown2, which supports all the stardard syntax.The image wrapped in inline has to be written as following syntax.![image_cid](file_path.png)The alternative description will be applied as a cid in rtf, so please name it carefully and DO NOT be duplicated. To prevent from missing image, an absolute file path is recommended for attached image.
Package: coldshard-cli
ColdShard CLIThis is the official CLI for ColdShard. This allows you to do whatever it is you would've done on our panel,but in the command line🤯🎉!InstallationIt's very simple to install this CLI. You must have Python and PIP installed. Just run the following command:pipinstallcoldshard-cliUsageTo use this CLI, first you need to login. To do this, login at thepaneland create anAPI Key. Copy it and then login by running the following command:coldshardlogin--api-token[KEYHERE]Alternatively you can just runcoldshard loginand you will be prompted to enter your API key.After you have logged in, you can simply runcoldshard --helpto see all the commands you can run.ContributingIf you would like to contribute to this project, please fork the repository and make a pull request. If you have any questions, please join ourDiscord.LicenseThe license for this project is availablehere. If you would like to purchase the rights to distribute this project as your own, contact me on Discord atThe Untraceable#4852. Any attempts to do so without my permission will be met with legal action.
Package: coldsober-sure
hey,
this is coldsober irene.this package is about checking or tracking if the data written in the tkinter entry widget is the whole or float number
not a string or else datatype.you only need to create a double var and use it to track the data as you type in the entry widget.this is my github repository, you can see the sample codehttps://github.com/coldsober-irene/tracknumber/tree/mainchange log0.0.1 (04/01/2022)first release
Package: coldsweat
ColdsweatColdsweat is a self-hosted Python 3 web RSS aggregator and reader compatible with theFever API. This means that you can connect Coldsweat to a variety of clients likeReederfor iOS or Mac OS XReadKitapp and use it to sync them together.FeaturesWeb interface to read and add feedsCompatible with existing Fever desktop and mobile clientsMulti-user supportBasic support for grouping of similar itemsInstallation and quick setupLet's see how you can take a peek at what Coldsweat offers running it on your machine.Note: you can install Coldsweat in the main Python environment of your machine or in a virtual environment, which is the recommended approach, since its dependencies may clash with packages you have already installed.Learn more about virtual environments here.InstallColdsweat isFlask applicationdistributed as a Python wheel, hence you can install it from PyPI using the, hopefully familiar,piputility:$ pip install coldsweatThe install procedure will also create acoldsweatcommand, available in your terminal.Create a userOnce installed, create a new user specifing email and password with thesetupcommand:$ coldsweat setup john@example.com -p somepasswordIf you prefer you can enter the password interactively:$ coldsweat setup john@example.com  
Enter password for user john@example.com: ************
Enter password (again): ************
Setup completed for john@example.comEmail and password will be needed to access the web UI and use the Fever API sync with your favourite RSS client.Import your feedsLike other RSS software Coldsweat uses the OPML format to import multiple feeds with a single operation:$ coldsweat import /path/to/subscriptions.opml alice@example.com -fThe-foption tells Coldsweat to fetch the feeds right after the import step.Fetch feedsTo update all the feeds run thefetchcommand:$ coldsweat fetchYou should usecronor similar utilities to schedule feed fetches periodically.Run the web UIThen you can run the Flask development web server and access the web UI:$ coldsweat run 
* Serving Flask app 'coldsweat'
* Debug mode: off
* Running on http://127.0.0.1:5000
...SeeSetupandDeploypages for additional information.Upgrading from a previous versionUpgrade to the latest Coldsweat version with:$ pip install -U coldsweatNote: there's no upgrade path from previous 0.9.x releases. Your best bet if to export OPML subscriptions and import them in the new 0.10 release.ContributingSeeContributingpage.0.10 technical underpinningsRuns on Python 3.9 and upCompletely rebuilt using Flask web frameworkSupports SQLite, PostgreSQL, and MySQL databasesHTTP-friendly fetcherTested with latest versions of Chrome, Safari, and FirefoxMotivationI'm fed up of online services that are here today and gone tomorrow. Years ago, after the Google Reader shutdown it was clear to me that the less we rely on external services the more the data we care about are preserved. With this in mind I'm writing Coldsweat. It is my personal take at consuming feeds today.Coldsweat started in July 2013 as a fork ofBottle Feverby Rui Carmo. After several years of pause I've restarted to develop Coldsweat using Python 3 and the latest crop of web technologies.
Package: coldsync
coldsyncBackup important files to cold storage.pip install coldsyncGoogle Cloud Storageis supported for now. The API is can be extend to add support other providers. Inside the storage module extend theBaseStorageto add support for other providers.UsageTo use the commands you must first setup the following environment variables:CS_DATA_CENTERCS_PROJECT_NAMECS_ENV_NAMECS_GOOGLE_SERVICE_ACCOUNT_PATHWhereCS_DATA_CENTER,CS_PROJECT_NAME,CS_ENV_NAMEare used to identify the
bucket in which files are stored.TheCS_GOOGLE_SERVICE_ACCOUNT_PATHmust point to your googlecredentials.jsonfile.ExamplesShow all files inside the bucketCS_DATA_CENTER='central-europe' \
CS_PROJECT_NAME='coold-data-storage' \
CS_ENV_NAME='production' \
CS_GOOGLE_SERVICE_ACCOUNT_PATH='credentials.json' \
coldsync list-filesUpload a file to the bucketYou may need to mount the file in the docker container in order to have access to it.CS_DATA_CENTER='central-europe' \
CS_PROJECT_NAME='coold-data-storage' \
CS_ENV_NAME='production' \
CS_GOOGLE_SERVICE_ACCOUNT_PATH='credentials.json' \
coldsync upload-file sample.jpg --remote_path 'thecat.jpg'Download a file from the bucketYou may need to mount the download directory in the docker container in order to
have access to the files which have been downloaded from your local file system.CS_DATA_CENTER='central-europe' \
CS_PROJECT_NAME='coold-data-storage' \
CS_ENV_NAME='production' \
CS_GOOGLE_SERVICE_ACCOUNT_PATH='credentials.json' \
coldsync download-file 'thecat.jpg' thecat.jpgDeleting a file from the bucketCS_DATA_CENTER='central-europe' \
CS_PROJECT_NAME='coold-data-storage' \
CS_ENV_NAME='production' \
CS_GOOGLE_SERVICE_ACCOUNT_PATH='credentials.json' \
coldsync delete-file 'thecat.jpg'TestsRunning test suitepython setup.py test