Saravanan666/pypi-org huggingface dataset:
Package: buildkite-test-collector
Buildkite Test Collector for Python (Beta)The official Python adapter forBuildkite Test Analyticswhich collects information about your tests.Supported python versions:>=3.8⚒Supported test frameworks:pytest.📦Supported CI systems:Buildkite, GitHub Actions, CircleCI, and others via theBUILDKITE_ANALYTICS_*environment variables.👉 InstallingCreate a test suite, and copy the API token that it gives you.Addbuildkite-test-collectorto your list of dev dependencies insetup.pyextras_require={"dev":["buildkite-test-collector"]}Set up your API tokenAdd theBUIDLKITE_ANALYTICS_TOKENenvironment variable to your build system's environment.Run your testsRun your tests like normal.  Note that we attempt to detect the presence of several common CI environments, however if this fails you can set theCIenvironment variable to any value and it will work.$pytestVerify that it worksIf all is well, you should see the test run in the test analytics section of the Buildkite dashboard.🎢 TracingBuildkite Test Analytics has support for tracing potentially slow operations within your tests (SQL queries, HTTP requests, etc).  This library now supports the ability to add tracing information to your test analytics output by using the newspanspytest fixture.  See theSpanCollectordocumentation for more information.🔜 RoadmapSee theGitHub 'enhancement' issuesfor planned features. Pull requests are always welcome, and we’ll give you feedback and guidance if you choose to contribute 💚⚒ DevelopingAfter cloning the repository, install the dependencies:pip install -e '.[dev]'And run the tests:pytestUseful resources for developing collectors include theBuildkite Test Analytics docsand theRSpec and Minitest collectors.👩‍💻 ContributingBug reports and pull requests are welcome on GitHub athttps://github.com/buildkite/test-collector-python🚀 ReleasingVersion bump the code, tag and push.Publish to thePython Package Index:python3-mbuild
python3-mtwineuploaddist/*Create anew github release.📜 LicenseThe package is available as open source under the terms of theMIT License.🤙 ThanksThanks to the folks atAlembicfor building and maintaining this package.
Package: buildmason
BuildMasonBuildMason is a command-line tool for generating scaffolding projects with different configurations.It currently supports creating a basic Flask project, a Flask REST API project, and a Flask project with Blueprints.InstallationpipinstallbuildmasonUsagebuildmasonCOMMAND[OPTIONS][ARGS]...Commandsbasic-flask-project: Generates a basic Flask project.rest-api: Generates a Flask REST API project.blueprint: Generates a Flask project with Blueprints.Options--help: Show this message and exit.Getting StartedBasic Flask Projectbuildmasonbasic-flask-projectThis command will generate a basic Flask project structure. This is a simple Flask project that creates/route and renders an index.html page.Project template linkProject Structure{{cookiecutter.project_name}}/
├── README.md
├── app
│   ├── __init__.py
│   └── templates
│       └── home.html
├── config.py
├── requirements.txt
└── run.pyFlask REST API Projectbuildmasonrest-apiThis command will generate a Flask project with REST API configuration. This is a simple Flask project for a REST API with user data. The project defines a user data model and creates/queries the data.Project template linkProject Structure{{cookiecutter.project_name}}/
├── app/
│   ├── __init__.py
│   ├── models/
│   │   ├── __init__.py
│   │   ├── user.py
│   ├── services/
│   │   ├── __init__.py
│   │   ├── user_service.py
│   ├── utils/
│   │   ├── __init__.py
│   │   ├── config.py
│   ├── app.py
├── tests/
│   ├── __init__.py
│   ├── resources/
│   │   ├── __init__.py
│   │   ├── test_user_resource.py
│   ├── services/
│   │   ├── __init__.py
│   │   ├── test_user_service.py
├── venv/ (virtual environment)
├── requirements.txtFlask Blueprint ProjectbuildmasonblueprintThis command will generate a Flask project with Blueprints. This is a simple Flask project that allows user login into the web application. We make use several componentsFlask-Login library for session managementbuilt-in Flask utility for hashing passwordsAdd protected pages to the app for logged in users onlyUse Flask-SQLAlchemy to create a User modelCreate sign-up and login forms for the users to create accounts and log inFlash error messages back to users when something goes wrongUse information from the user’s account to display on the profile pageProject template linkProject Structure{{cookiecutter.project_name}}/
├── app
│   ├── __init__.py
│   ├── models
│   │   ├── __init__.py
│   │   └── user.py
│   ├── routes
│   │   ├── __init__.py
│   │   ├── auth.py
│   │   └── main.py
│   └── templates
│       ├── base.html
│       ├── index.html
│       ├── login.html
│       ├── profile.html
│       └── signup.html
├── requirements.txt
├── run.py
└── tests
    ├── __init__.py
    ├── models
    │   ├── __init__.py
    │   └── test_models.py
    └── routes
        ├── test_auth.py
        └── test_main.pyContributingFeel free to contribute to this project. Open issues or submit pull requests on the GitHub repository.LicenseThis project is licensed under the MIT License - see the LICENSE file for details.
Package: buildmc
buildMCA pure Python program that makes building a large, complicated project using CMake or Meson just a single, simple command.InstallPrereqs:Python ≥ 3.6CMake ≥ 3.14orMeson+Ninjapipinstallbuildmcor to use latest development codegitclonehttps://github.com/scivision/buildmccdbuildmc

pipinstall-e.UsagebuildMC makes switching between compilers trivial.
Also, building on native Windows and Windows Subsystem for Linux is detected and handled--the CMake or Meson cache is wiped to allow clean rebuild when switching without fuss.ExamplesSay you want to ensure a project builds with each of Visual Studio, GNU/GCC, Intel and Clang.
This can be easily done by typing in the top-level of the project directory:buildmcmsvc

buildmcgnu

buildmcintel

buildmcclangEach command independently builds and runs the user-configured tests using CMake or Meson.
When switching between Windows and Linux (using WSL from Windows) buildMC detects the OS switch and wipes the build cache and rebuilds as needed.
Package: buildme
BuildMe 🛠️Another build system. A simple command runner thats it.What is BuildMe 🤔️Well this pretty much sums it up.Why???IDK. I saw this comic and decided that I want a build system of my own.And,Makefile's are shit.Cmake is complicatedMeson requires two dependencies (Meson and Ninja)Bazel, corporate BSIt does come with some feature.It is just command runner (Does not give anfabout the file or it's mod time)v0.3.0 onwards, buildme does give anfabout the file and it's mod times (times have changed)It's just python. Anything that works on python works on buildme script.you want a build script that has access topandas, well you can now have it.Docs 🧾️Install buildmepip3 install git+https://github.com/Adwaith-Rajesh/buildme.gitORpip3 install buildmeCreate abuildmescriptThe shebang is IMPORTANT (This thingy -> #!/bin/env buildme)#!/bin/env buildmefrombuildmeimportCommandRunner,targetcr=CommandRunner()@target()deffoo(_,__):print('This is the foo target')@target()defbar(_,__):cr.run('echo this is from bar target')@target(depends=['foo','bar'])defall(_,__):passMake it executable$./buildmefooThis is the foo target$./buildmebar================================================================================[CMD]: echo this is from bar targetthis is from bar target================================================================================$./buildmeallThis is the foo target================================================================================[CMD]: echo this is from bar targetthis is from bar target================================================================================More docs can be found here:DocsBuildmeTargetCreating a targetTarget depending on another targetTarget depending on filesTargets that creates filesCommandRunnerReceiving Command line argsGetting info about the target itselfDynamic 'creates'Combining IdeasHelper functionsBye....
Package: buildout.autoextras
buildout.autoextrasBuildout (zc.buildout) extension for including setuptools extras_require
options for all items in a target option if the extra exists.UsageThis is a buildout extension, so simply add it to your extensions list:[buildout]
extensions = buildout.autoextrasOptionsThere are two options…autoextra-keysA list of extra keys (e.g. test, zcml, etc.) that should be included if
the package has the extra.autoextra-targetsA list of targets to check for the extras. For example, a buildout part
nameddemothat has aneggsoption. The target in this case would
bedemo:eggs. This is similar to zc.buildout’s variable replace
syntax except without the${}symbolling.Together these options might look something like:[buildout]
extensions = buildout.autoextras
parts = demo
autoextra-keys = zcml
autoextra-targets = demo:eggs

[demo]
recipe = zc.recipe.eggs
eggs =
    zope.testing
    zope.i18nChangelog1.1 (2011-10-25)Monkeypatching zc.buildout.easy_install.Installer’s install method in order
to post-process the distributions. Otherwise, we run into an order of
operations problem (e.g. obtaining eggs before some eggs have been marked
for development). [pumazi]1.0 (2011-10-21)Initial release. [pumazi]
Package: buildout.bootstrap
buildout.bootstrapBuildout extension to downloadhttps://bootstrap.pypa.io/bootstrap-buildout.pyautomatically.IntroductionFormerlycollective.recipe.bootstrapbuildout.bootstrapis a Buildout extension that adds a Buildoutbootstrap.pyfile to your buildout.It satisfies the use case:“I want to keep my buildout’s bootstrap.py file up to date without having to download it manually.”It also makes it easy to add abootstrap.pyfile to a buildout created viabuildout inite.g.:$ buildout initAfter running this command, you have abuildout.cfgthat looks like this:[buildout]
parts =And you can now add the extension like so:[buildout]
extensions = buildout.bootstrap
parts =Run buildout again and afterward you should have abootstrap.pyfile. Once you have abootstrap.pyfile you can bootstrap the buildout via:$ python bootstrap.pyIf you still don’t understand, consider the following: with this extension you can avoid having to type:$ curl -O https://bootstrap.pypa.io/bootstrap-buildout.pyYou typically use this extension when you have created a new buildout and want to:Check it in to version controlCheck it out somewhere else and bootstrap it with python only (i.e. no setuptools available)InstallationAddbuildout.bootstrapto theextensionsparameter in the buildout section of yourbuildout.cfge.g.:[buildout]
extensions = buildout.bootstrap
parts =ContributorsAlex ClarkDavid BeiteySean “nutjob” KellyChanges1.4.8 (2015-06-04)Update file to bootstrap-buildout.py1.4.7 (2015-05-18)Update URL tohttps://bootstrap.pypa.io/bootstrap-buildout.py1.4.6 (2013-07-13)Default to Buildout 21.4.5 (2013-01-12)Update buildout/bootstrap/__init__.py1.4.4 (2013-01-12)Update buildout/bootstrap/__init__.py [do3cc]Working error codes [do3cc]1.4.3 (2012-11-01)Don’t bother updating bootstrap.py when the buildout is running in offline (-o) mode
[nutjob]1.4.2 (2012-08-18)Change bootstrap URL tohttps://raw.github.com/buildout/buildout/1.6.x/bootstrap/bootstrap.py1.4.1 (2012-05-16)Change bootstrap URL tohttp://buildout.org/bootstrap.py1.4.0 (2012-05-16)Support Python 2.4Doc fix
[davidjb]1.3.0 (2012-04-06)Clean up package. Buildout moved to github. Remove option to specify version (based on svn tag)1.2 (2010-08-13)Add option to specify version (based on svn tag)Add test stubs1.1 (2010-08-13)Rename and repackage as Buildout extension1.0 (2009-12-19)Clean up docs0.1 (2009-08-07)Add initial functionalityCreated recipe with ZopeSkel
Package: buildout-component
# buildout-componentPython Buildout component tool, a tool program used to help componentize the settings of zc.buildout.## IntroductionBuildout is a great tool for Python development and deployment environment, but it requires a lot of settings to work
well.I am used to Buildout each reusable item as a component. If there is a component that needs to be reused, just copy its
content to a new project to use it directly, but it still depends on manual settings and configuration.In order to simplify the complicated settings, I wrote a gadget calledbuildout-componentto help me set up the
componentized environment of Buildout more conveniently.## FeaturesGenerate the file structure of Buildout Component;Through the question and answer method, to generate the Buildout profile.## InstallationInstallbuildout-component:$ pip install buildout-component## UseAfter installation, you can execute thebuildout-componentcommand:set up$ buildout-component setupDisplay set value$ buildout-component show-optionsCreate Component$ buildout-component createChangeLog0.1.dev0First release on PyPI.
Package: buildout.disablessl
buildout.disablesslsetuptools-0.7 introduced verification of SSL certificates. This feature,
however, is not configurable (yet?), which makes it impossible to install
packages from a custom package index with a self-signed certificate, for
example.This package is a very small, monkey-patching buildout extension that simply
sets “ssl available” to false. Use it like so:[buildout]
extensions = buildout.disablesslPython 2.7.9 activated SSL certificate verification by default, too. When using
this version or newer it is disabled, too.WARNING: Using this extension disables SSL verification (duh), so you make
yourself susceptible to man-in-the-middle attacks (among other things). Use
with caution!Developing buildout.disablesslAuthor:gocept<mail@gocept.com>PyPI page:http://pypi.python.org/pypi/buildout.disablessl/Issues:report by e-mailSource code:https://bitbucket.org/gocept/buildout.disablessl/Current change log:https://bitbucket.org/gocept/buildout.disablessl/raw/tip/CHANGES.txtChange log for buildout.disablessl1.1 (2015-04-28)Disable SSL certificate verification of Python 2.7.9+, too.1.0 (2013-11-14)initial release
Package: buildout.dumprequirements
A simple buildout extension that dumps a requirements.txt file for pip.This is more or less a copy of buildout.dumppickedversions. All credit goes to the authors of that project.Warningbuildout.dumppickedversions(and therefore alsobuildout.dumprequirements) does somenastystuff to get its job done. Namely it monkeypatcheszc.buildout.easy_install._log_requirement,zc.buildout.easy_install.Installer._get_distandlogging.shutdown. Because both extensions
monkeypatch the same methods, it is currently not possible to usebuildout.dumppickedversionsandbuildout.dumprequirementsat the same time.
I’m not quite sure how to solve this. Probably we’ll have to support the functionality of both extensions
in one package.UsageAddbuildout.dumprequirementsas an extension to the[buildout]section:[buildout]
extensions = buildout.dumprequirements
dump-requirements-file = requirements.txt
overwrite-requirements-file = truedump-requirements-filedefines the file the requirement list will be written to. If it is undefined the
package list will be printed to the console. Settingoverwrite-requirements-filetofalsewill preventbuildout.dumprequirementsfrom overwriting an existing file. The setting defaults totrue.
Contributors
============Stefan Foulis, AuthorMustapha Benali, Author of buildout.dumppickedversions
Package: buildout.eggsdirectories
ContentsIntroductionHowtoContributorsChangelogIntroductionbuildout.eggsdirectoriesincludes all eggs found in prepopulated
directories.This enables distribution of separate eggs sets.HowtoTunebuildoutsection:[buildout]
extensions = buildout.eggsdirectories
eggs-directories = ${buildout:directory}/more-eggs
                   /usr/local/plone-eggsAll eggs found inmore-eggsor in/usr/local/plone-eggswill be made
available for the installation of eggs or creation of scripts.ContributorsGodefroid Chapelle, Original AuthorChangelog1.0 (2014-02-10)Initial release [gotcha]
Package: buildout.extensionscripts
buildout.extensionscriptsis a convenient way to shoot yourself in the foot
and provides more than enough rope to hang yourself.With that out of the way, we can look what it can be used for.To usebuildout.extensionscripts, you add it as an extension in a buildout
like this:[buildout]
extensions = buildout.extensionscriptsAfter that you can add one or more lines like the following to thebuildoutsection:extension-scripts =
    ${buildout:directory}/somescript.py:callable_nameWhen you do that, you got an easy way to write a buildout extensions without
the need of an egg. Thecallable_nameinsomescript.pywill be called
with one argument which is the dictionary like buildout config.Now have fun shooting and or hanging yourself by changing that.
Package: buildout-md5sums
Author:Filip NoetzelWeb:http://github.com/peritus/buildout-md5sums/Git:git clonegit://github.com/peritus/buildout-md5sums.git(browse source)Download:Downloads page on GitHubSimple usageUse a buildout.cfg like this and the md5sum for the download-python target will be checked:[buildout]
extensions = buildout-md5sums
md5sums =
  http://python.org/ftp/python/2.6.6/Python-2.6.6.tar.bz2 = 376df294ae16e9601da989f8c4d8d432
  http://python.org/ftp/python/2.7/Python-2.7.tar.bz2 = 0e8c9ec32abf5b732bea7d91b38c3339
parts = download-python

[versions]
python = 2.6.6

[download-python]
recipe = hexagonit.recipe.download
url = http://python.org/ftp/python/${versions:python}/Python-${versions:python}.tar.bz2Using this setup, you can switch the downloaded version of python on the
command line while keeping the cryptographic checking alive:$ ./bin/buildout versions:python=2.7 install download-pythonDisallowing downloads without md5sumsIf your buildout.cfg like this, the extension will make the buildout fail if
there is a download using zc.buildout.download without a md5sum specified:[buildout]
extensions = buildout-md5sums
allow-picked-downloads = false
Package: buildout.packagename
buildout.packagenameis azc.buildoutextension which can be used
to extract the package name of an adjacentsetup.pyto avoid redundancy.
The extracted name is made available via thepackage-namevariable in
the[buildout]section, i.e. as${buildout:package-name}.UsageAn examplebuildout.cfgusing the extension might look like this:[buildout]
extensions = buildout.packagename
parts = app

[app]
recipe = zc.recipe.egg
interpreter = app
eggs = ${buildout:package-name}Please note that since using this extension only makes sense for
package-specific buildouts, thedevelopsetting is set to “.”
for added convenience.Changelog1.0 (2012-10-27)Initial release.
[witsch]
Package: buildout.packager
distutils extension module - create an buildout-based installer.zc.buildout is a Python-based build system for creating, assembling and
deploying applications from multiple parts, some of which may be
non-Python-based. It lets you create a buildout configuration and
reproduce the same software later.  –http://www.buildout.org/buildout.packager creates single-file installers for an buildout-environment
along with all dependencies, which can be used without network access.RequirementsPython 2.5 or laterInnoSetupfor Windows installerDependenciessetuptoolsordistributezc.buildoutFeaturesYou can create an installer reproducing zc.buildout environment.installer metadata over setup() metadataLimitationsThe installer doesn’t bundle Python interpreter.Not implemented for Unix environment.An examplesetup.py:from setuptools import setup
setup(
    name='Sphinx',
    version='1.0',
)buildout.cfg:[buildout]
parts = app

[app]
recipe = zc.recipe.egg
eggs =
    SphinxDo the commandpython setup.py bdist_buildout.
Then you get the installation file nameddistSphinx-1.0-py2.6-win32.exe.History0.0.1first releaseTodosfor Windowsuse innosetup packagereplace os.system with subprocessfor UnixNotImplementedKnown IssuesProcess restart probrem when zc.buildout upgrate it by oneself.
Package: buildoutpip
This is a buildout extension that allows to buildout from a pip requirements file.This was created very quickly to show my friend that it could be done. I don't need this right now,but I can see this being very useful for Pinax users.TODO:* allow to open local requirements* implement -e and -f requirements options* write testsHere is an example of a buildout file.[buildout]extensions = buildoutpiprequirements =http://github.com/pinax/pinax/raw/master/requirements/0.7/release.txtparts = pipeggs =[pip]recipe=zc.recipe.eggeggs = ${buildout:eggs}
Package: buildout.recipe.download
IntroductionThe recipe extension helps to download pinned eggs quickly. It uses python
multiprocessing module.InstallationBuild with
python setup.py build installadd below configuration to buildout.cfg:[download-eggs-first]
recipe = buildout.recipe.download
pkgurl = ${pkgserver:fullurl}
cache-folder = ${buildout:directory}/download-cache
versions-files = ${buildout:directory}/versions/versions.cfgOptinally we can pass threads, it is defaulted to 50
Package: buildout.recipe.mako_template
buildout.recipe.mako_templateA buildout recipe for making files out of Mako templates, with focus on
manageability of large number of templates.Contentsbuildout.recipe.mako_templateRecipe OptionsMinimal ExampleLarger ExampleCollision detectionLinks and CreditsHistory0.1.2 (2018-03-19)0.1.1 (2018-03-13)0.1.0 (2018-03-12)The reasons behind creating this ‘another’ template recipe for buildout are wish of having:makowith all power of python and good scoping in templates,simple listing ofsource : destinatoinmapping,and collision detection.Recipe Optionsfiles: list of couples of templates and targets files paths separated by:symbol.
It allow to specify if target should be executable, and to ignore a collision.
Line has following format:source:target[:is_executable(trueorfalse)[:collision_allowed(justaflag))]]directories: list of lookup directories of themakotemplates. Templates
file paths are relative to these directories. (default: ${buildout:directory})Additional options are simply forwarded to the templates, and options from all the
other parts are made available throughparts[<part-name>][<option-name>].Minimal Examplebuildout.cfg:[buildout]parts=foo[foo]recipe=buildout.recipe.mako_templateauthor=Mefiles=foo_1.sh.mako : foo_1.shfoo_1.sh.mako:echo Hello${author}!Will result in creation offoo_1.sh:echoHelloMe!Larger Example[buildout]parts=docker-compose[project]name=MyProject[docker-compose]recipe=buildout.recipe.mako_templatedirectories=${buildout:directory}/templatesgateway_ports=8080:8080files=backend.dockerfile.mako:.docker/backend.dockerfilefrontend.dockerfile.mako:.docker/frontend.dockerfilegateway.dockerfile.mako:.docker/gateway.dockerfiledocker-compose.yaml.mako:docker-compose.yamldocker-compose.yaml.mako:...
gateway:
    container_name:${parts['project']['name']}_gateway
    ports:
      - "${gateway_ports}"
...Collision detectionCases where one’s template target are overridden by another template
are detected automatically. For example, case:files=foo_1.sh.mako:foo_1.shfoo_2.sh.mako:foo_1.sh# overwrites ``target`` form abovewill result in a build fail with the message:Targetcollisionisdetectedat'foo_2.sh.mako : foo_1.sh'Yet in some cases, it may be a desirable behavior, so it’s possible to allow
overwriting by addingcollision_allowedflag.Links and CreditsThis recipe is heavily inspired bybrodul.recipe.template.To get more examples and information on using mako templates visitmakotemplates.History0.1.2 (2018-03-19)Add creating of a destination file containing folder if not exists.Add contents and useful links toreadme.rst.Add coverage checking tomake testcommand.
[enkidulan]0.1.1 (2018-03-13)Fix packaging issue.
[enkidulan]Update docs, add more examples, add badges.
[enkidulan]0.1.0 (2018-03-12)First release on PyPI.
Package: buildout.removeaddledeggs
buildout.removeaddledeggsQ: What is a buildout extension ?A:http://pypi.python.org/pypi/zc.buildout#extensionsInstallationAdd “buildout.removeaddledeggs” to theextension-section in your buildout, like[buildout]
parts =
        ...

extensions =
        buildout.removeaddledeggsChange history0.1 (2011-01-30)creating first release [kiwisauce]ContributorsTodosLoggingHow to run this extension after buildout?