Saravanan666/pypi-org huggingface dataset:
Package: bugs-everywhere
Bugs Everywhere===============This is Bugs Everywhere (BE), a bugtracker built on distributed versioncontrol.  It works with Arch, Bazaar, Darcs, Git, Mercurial, and Monotoneat the moment, but is easily extensible.  It can also function with noVCS at all.The idea is to package the bug information with the source code, so thatbugs can be marked "fixed" in the branches that fix them.  So, instead ofnumbers, bugs have globally unique ids.Getting BE==========BE is available as a Git repository::$ git clone git://gitorious.org/be/be.git beSee the homepage_ for details.  If you do branch the Git repo, you'llneed to run::$ maketo build some auto-generated files (e.g. ``libbe/_version.py``), and::$ make installto install BE.  By default BE will install into your home directory,but you can tweak the ``PREFIX`` variable in ``Makefile`` to installto another location... _homepage: http://bugseverywhere.org/Getting started===============To get started, you must set the bugtracker root.  Typically, you will want toset the bug root to your project root, so that Bugs Everywhere works in anypart of your project tree.::$ be init -r $PROJECT_ROOTTo create bugs, use ``be new $DESCRIPTION``.  To comment on bugs, youcan can use ``be comment $BUG_ID``.  To close a bug, use``be close $BUG_ID`` or ``be status $BUG_ID fixed``.  For morecommands, see ``be help``.  You can also look at the usage examples in``test_usage.sh``.Documentation=============If ``be help`` isn't scratching your itch, the full documentation isavailable in the doc directory as reStructuredText_ .  You can buildthe full documentation with Sphinx_ , convert single files withdocutils_ , or browse through the doc directory by hand.``doc/index.txt`` is a good place to start.  If you do use Sphinx,you'll need to install numpydoc_ for automatically generating APIdocumentation.  See the ``NumPy/SciPy documentation guide``_ for anintroduction to the syntax... _reStructuredText:http://docutils.sourceforge.net/docs/user/rst/quickref.html.. _Sphinx: http://sphinx.pocoo.org/.. _docutils: http://docutils.sourceforge.net/.. _numpydoc: http://pypi.python.org/pypi/numpydoc.. _NumPy/SciPy documentation guide:https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt
Package: bugsnag-exporter
This package exports metrics aboutBugsnagerror events asPrometheusmetrics.UsageConfigure API tokenYou’ll need to provide an API token to access the Bugsnag Data Access API.
See theBugsnag documentationfor details.Start HTTP serviceStart the HTTP server like this:$ BUGSNAG_APITOKEN=MYTOKEN bugsnag_exporter --host=127.0.0.1 --port=9642Pass--ttl=SECONDSto cache Bugsnag API results for the given time or -1 to disable (default is 600).
Prometheus considers metrics stale after 300s, so that’s the highest scrape_interval one should use.
However it’s usually unnecessary to hit the API that often, since the vulnerability alert information does not change that rapidly.You can pass–bucketswith a comma-separated list to define the upper bucket bounds that are used to generate the histogram metric.Configure Prometheusscrape_configs:
  - job_name: 'bugsnag'
    scrape_interval: 300s
    static_configs:
      - targets: ['localhost:9642']We export one metric, a histogram calledbugsnag_events,
with labels{project="MyProject",release_stage="production"}.A typical alerting PromQL query might bebugsnag_events_bucket{le="+Inf",release_stage="production"}- ignoring (le)bugsnag_events_bucket{le="1000.0",release_stage="production"}> 0Additionally, abugsnag_scrape_duration_secondsgauge is exported.CHANGES1.2.0 (2021-10-15)Addsort=unsortedparameter to handle potentially large result sets1.1.1 (2021-05-07)Throttle paginated requests to avoid hitting the rate limit.1.1.0 (2019-10-02)Use default prometheus histograms with “le” buckets1.0.0 (2019-09-09)First release.
Package: bugsplat
BugSplatCrash and error reporting built for busy developers.👋 IntroductionThis repo contains the source code for bugsplat-py, a BugSplat integration for reporting Unhandled Exceptions in Python.🏗 InstallationInstall the bugsplat package using pippipinstallbugsplat⚙️ ConfigurationImport the BugSplat classfrombugsplatimportBugSplatCreate a new BugSplat instance passing it the name of your BugSplat database, application and versionbugsplat=BugSplat(database,application,version)Optionally, you set default values for appKey, description, email, user and additionaFilePathsbugsplat.set_default_app_key('key!')bugsplat.set_default_description('description!')bugsplat.set_default_email('fred@bugsplat.com')bugsplat.set_default_user('Fred')bugsplat.set_default_additional_file_paths(['./path/to/additional-file.txt','./path/to/additional-file-2.txt'])Wrap your application code in a try except block. In the except block call post. You can override any of the default properties that were set in step 3try:crash()exceptExceptionase:bugsplat.post(e,additional_file_paths=[],app_key='other key!',description='other description!',email='barney@bugsplat.com',user='Barney')Once you've posted a crash, navigate to the Crashes page and click the link in the ID column to be see the crash's details🧑‍💻 DevelopmentTo configure a development environment:Clone the repositorygitclonehttps://github.com/BugSplat-Git/bugsplat-py.gitCreate a virtual environmentpython-mvenvvenvActivate the virtual environment# unix/macossourcevenv/bin/activate# windows.\env\Scripts\activateInstall the project's dependenciespipinstall.Thanks for using BugSplat ❤️
Package: bugspots
Bugspots is a Python implementation of the bug prediction algorithm used at
Google. (seehttp://bitly.com/uglCGz)You can use its command-line interface to identify hot spots in a Git
repository:~dev/git/jquery$ bugspots.py
Scanning repository...
Found 6 hot spots

 2.581 src/event.js
 1.912 src/css.js
 1.420 test/unit/event.js
 1.115 test/unit/css.js
 0.996 src/manipulation.js
 0.906 src/effects.js
Package: bugspots3
Bugspots is a Python implementation of the bug prediction algorithm used at
Google.Home-page:https://gitlab.com/gitmate/bugspots3Author: The Bugspots Authors
Author-email:support@gitmate.ioLicense: ISC License
Description: UNKNOWN
Platform: Unix
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: ISC License (ISCL)
Classifier: Natural Language :: English
Classifier: Operating System :: Unix
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: Implementation :: CPython
Classifier: Topic :: Software Development :: Bug Tracking
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Topic :: Utilities
Package: bug-trail
Bug TrailThis is a workstation logger to capture bugs encountered while you are writing code.In other words, it is an HTML report writer for your logs, even if they aren't errors if that is your thing.InstallationThe handlers inbug-trail-coresupport python 3.9+.bug-trail, the report viewer supports python 3.11 and should
be installed apart from your main app.Install bug-trail-core with your app. It has as few dependencies as I could manage.pipinstallbug-trail-coreTo generate the static website install this in an isolated global virtual environment.pipxinstallbug-trailUsageConfiguration is optional via apyproject.tomlfile and the logging modules ordinary configuration options. Seeexample code-as-configThis is the schema with the default values.[tool.bug-trail]app_name="bug_trail"app_author="bug_trail"report_folder="logs"database_path="bug_trail.db"importbug_trail_coreimportloggingsection=bug_trail_core.read_config(config_path="../pyproject.toml")handler=bug_trail_core.BugTrailHandler(section.database_path,minimum_level=logging.ERROR)logging.basicConfig(handlers=[handler],level=logging.ERROR)logger=logging.getLogger(__name__)logger.error("This is an error message")To generate to the log folder relative to the current working directory:bug_trail--outputlogs--dberror_log.dbPicologgingIf you want to use picologging, install it. Everything is the same except you use thePicoBugTrailHandler.importbug_trail_coreimportloggingsection=bug_trail_core.read_config(config_path="../pyproject.toml")handler=bug_trail_core.PicoBugTrailHandler(section.database_path,minimum_level=logging.ERROR)logging.basicConfig(handlers=[handler],level=logging.ERROR)logger=logging.getLogger(__name__)logger.error("This is an error message")Do more with your datapipxinstalldatasette
datasettebug_trail.dbSecurityNone. Do not publish your error log to the internet or to public Github. Add the log folder to your .gitignore file.AdvancedGet ctags fromhere./ctags-R-ffish_tank.tagsfish_tankPrior ArtInspired by elmah.bug_trailis much less ambitious, as this is just a browsable, static HTML report.If you want logger for a website, hosted in your Flak or Django website:Flask-ErrorsHandlerdjango-elmahThese are the closest "write logs to HTML" projects I could find:PyLog2htmlGist -https://gist.github.com/ColinDuquesnoy/8296508dblogging- Uses sqlite, but does not use standard library logging frameworkIf you want someone else to do it all for youSentry
Package: bug-trail-core
Bug TrailThis is a workstation logger to capture bugs encountered while you are writing code.In other words, it is an HTML report writer for your logs, even if they aren't errors if that is your thing.InstallationInstall this with your app. It has as few dependencies as I could manage.pipinstallbug-trail-coreTo generate the static website install this in an isolated global virtual environment.pipxinstallbug-trailUsageConfiguration is optional via apyproject.tomlfile and the logging modules ordinary configuration options. Seeexample code-as-configThis is the schema with the default values.[tool.bug-trail]app_name="bug_trail"app_author="bug_trail"report_folder="logs"database_path="bug_trail.db"importbug_trailimportloggingsection=bug_trail.read_config(config_path="../pyproject.toml")handler=bug_trail.BugTrailHandler(section.database_path,minimum_level=logging.ERROR)logging.basicConfig(handlers=[handler],level=logging.ERROR)logger=logging.getLogger(__name__)logger.error("This is an error message")To generate to the log folder relative to the current working directory:bug_trail--outputlogs--dberror_log.dbPicologgingIf you want to use picologging, install it. Everything is the same except you use thePicoBugTrailHandler.importbug_trailimportloggingsection=bug_trail.read_config(config_path="../pyproject.toml")handler=bug_trail.PicoBugTrailHandler(section.database_path,minimum_level=logging.ERROR)logging.basicConfig(handlers=[handler],level=logging.ERROR)logger=logging.getLogger(__name__)logger.error("This is an error message")Do more with your datapipxinstalldatasette
datasettebug_trail.dbSecurityNone. Do not publish your error log to the internet or to public Github. Add the log folder to your .gitignore file.AdvancedGet ctags fromhere./ctags-R-ffish_tank.tagsfish_tankPrior ArtInspired by elmah.bug_trailis much less ambitious, as this is just a browsable, static HTML report.If you want logger for a website, hosted in your Flak or Django website:Flask-ErrorsHandlerdjango-elmahThese are the closest "write logs to HTML" projects I could find:PyLog2htmlGist -https://gist.github.com/ColinDuquesnoy/8296508dblogging- Uses sqlite, but does not use standard library logging frameworkIf you want someone else to do it all for youSentry
Package: bugu_bot
<div align=”center”># 布谷机器人,增进你和你单身朋友的友谊</div>## 使用方式先创建群聊，可以起一个好听一点的名字例如![avatar](/图/名字.png)然后把你的机器人拉进来，并给一个管理![avatar](/图/拉人.png)最后,邀请受害人加入本群即可(小于 50 不需要同意哦！)
Package: buguet
BuguetEthereum Debugger (for smart contracts in Solidity).Prerequisitespython3Ethereum node running in archive mode with debug api. E.g. geth:geth --rpc --rpcapi eth,debug --gcmode archiveBy default localhost:8545 endpoint is used.Compiled contracts in format produced bysolcwith--combined-jsonoption.
Each contract called in transaction should be compiled with the same solidity
version as it deployed on the blockchain (multiple versions can be used for one transaction).Installationpip install buguetUsageBasic usage is:buguet contract1.json,contract2.json transaction_idSeebuguet --helpfor all options.Commandshelp (h)                Print help
    step (s)                Step into function
    next (n)                Next line in current frame
    stepout (so)            Step out of current function
    continue (c)            Continue execution
    break {file}:{line}     Set breakpoint
    breakpoints             List breakpoints
    unbreak {idx}           Remove breakpoint
    stack                   Print current stack
    mem                     Print memory
    op                      Print and execute one instruction
    {expr}                  Evaluate expression
Package: bugwarrior
bugwarrioris a command line utility for updating your localtaskwarriordatabase from your forge issue trackers.It currently supports the following remote resources:activecollab(2.x and 4.x)bitbucketbugzillaDebian BTSgerritgithub(api v3)gitlab(api v3)gmailjiramegaplanpagurephabricatorPivotal TrackerredminetaigateamlabtractrelloversiononeyoutrackDocumentationFor information on how to install and use bugwarrior, readthe docson RTFD.Build StatusBranchStatusmasterdevelopContributorsRalph Bean (primary author)Ben Boeckel (contributed support for Gitlab)Justin Forest (contributed support for RedMine, TeamLab, and MegaPlan, as
well as some unicode help)Tycho Garen (contributed support for Jira)Kosta Harlan (contributed support for activeCollab, notifications,
and experimental taskw support)Luke Macken (contributed some code cleaning)James Rowe (contributed to the docs)Adam Coddington (anti-entropy crusader)Iain R. Learmonth (contributed support for the Debian BTS and maintains the
Debian package)BinaryBabel (contributed support for YouTrack)Matthew Cengia (contributed extra support for Trello)Andrew Demas (contributed support for PivotalTracker)
Package: bugyi.lib
bugyi.libOverly general Python library used when no other library is a good fit.project status badges:version badges:Installation 🗹To installbugyi.libusingpip, run the following
commands in your terminal:python3-mpipinstall--userbugyi.lib# install bugyi.libIf you don't have pip installed, thisPython installation guidecan guide
you through the process.Useful Links 🔗API Reference: A developer's reference of the API exposed by this
project.cc-python: Thecookiecutterthat was used to generate this project.
Changes made to this cookiecutter are periodically synced with this project
usingcruft.CHANGELOG.md: We use this file to document all notable changes made to
this project.CONTRIBUTING.md: This document contains guidelines for developers
interested in contributing to this project.Create a New Issue: Create a new GitHub issue for this project.Documentation: This project's full documentation.
Package: bugyi.tools
bugyi.toolsMiscellaneous tools / executable scripts.Badges 📛project status badges:version badges:Installation 🗹Usingpipxto Install (preferred)This packagecouldbe installed using pip like any other Python package (in
fact, see the section below this one for instructions on how to do just that).
Given that we only need this package's entry points, however, we recommend thatpipxbe used instead:# install and setup pipxpython3-mpipinstall--userpipx
python3-mpipxensurepath# install bugyi.toolspipxinstallbugyi.toolsUsingpipto InstallTo installbugyi.toolsusingpip, run the following
commands in your terminal:python3-mpipinstall--userbugyi.tools# install bugyi.toolsIf you don't have pip installed, thisPython installation guidecan guide
you through the process.Useful Links 🔗API Reference: A developer's reference of the API exposed by this
project.cc-python: Thecookiecutterthat was used to generate this project.
Changes made to this cookiecutter are periodically synced with this project
usingcruft.CHANGELOG.md: We use this file to document all notable changes made to
this project.CONTRIBUTING.md: This document contains guidelines for developers
interested in contributing to this project.Create a New Issue: Create a new GitHub issue for this project.Documentation: This project's full documentation.
Package: bugyocloudclient
OBC Bugyo Cloud clientOBC 奉行クラウド PythonクライアントUsageBugyoCloudClientのインスタンスを作成します。importbugyocloudclientasbcctenant_code='The first part of URL path.'client=bcc.BugyoCloudClient(tenant_code)最初にLoginTaskを実行して、ログイン状態にします。auth_info=bcc.AuthInfo('login id','password')login_task=bcc.LoginTask(auth_info)client.exec(login_task)ログインしてから、別のタスクを実行します。
（今は打刻タスクしかありません）。punch_info=bcc.PunchInfo()punch_info.clock_type=clock_typepunch_task=bcc.PunchTask(punch_info)client.exec(punch_task)Installing poetrycurl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python3Changing python command name from 'python' to 'python3'.vi ~/.poetry/bin/poetryCreating environmentpoetry installTestingpoetry run pytestBuild & Publishpoetry buidpoetry publish -r testpypipoetry publish画面あるいはAPI認証画面URL:https://id.obc.jp/{{テナント?}}/METHOD: GETResponse:Headers:Content-Type: text/html; charset=utf-8認証方法チェックURL:https://id.obc.jp/{{テナント?}}/login/CheckAuthenticationMethodMETHOD: POSTHeaders:__RequestVerificationToken: 認証画面のフォームにあるhidden valueContent-Type: application/x-www-form-urlencoded; charset=UTF-8X-Requested-With: XMLHttpRequestContent:"OBCiD" : ログインID"isBugyoCloud" : "false"Response:Headers:Content-Type: application/json; charset=utf-8Content:AuthenticationMethodSAMLButtonTextPasswordButtonText認証URL:https://id.obc.jp/{{テナント?}}/login/login/?Length=5METHOD: POSTHeaders:Content-Type: application/x-www-form-urlencoded; charset=UTF-8Content:"btnLogin" : """OBCID" : ログインID"Password_d1" : """Password_d2" : """Password_d3" : """Password" : パスワード"__RequestVerificationToken" : 認証画面のフォームにあるinput hidden value"X-Requested-With" : "XMLHttpRequest"Response:Headers:Content-Type: application/json; charset=utf-8Content:RedirectURLLoginOBCiDレスポンスにあるRedirectURLをGETすると302が返ります。
302に従うと、ユーザ初期画面へ遷移します。URLは、https://hromssp.obc.jp/{{テナント？}}/{{ユニーク文字列？}}/のようになります。ユーザ初期画面URL:https://hromssp.obc.jp/{{テナント？}}/{{ユニーク文字列？}}/METHOD: GET認証後の302応答に従うとたどり着きます。ユニーク文字列の部分を、このあとの処理で使います。打刻画面URL:https://hromssp.obc.jp/{{テナント？}}/{{ユーザ初期画面URLより}}/timeclock/punchmark/METHOD: GETResponse:Headers:Content-Type: text/html; charset=utf-8打刻URL:https://hromssp.obc.jp/{{テナント？}}/{{ユーザ初期画面URLより}}/TimeClock/InsertReadDateTime/METHOD: POSTHeaders:"__RequestVerificationToken": 打刻画面にあるinput hidden value"Content-Type": "application/x-www-form-urlencoded; charset=UTF-8""X-Requested-With" : "XMLHttpRequest""Referer" : 打刻画面のURLContent:"ClockType" : 打刻種類"LaborSystemID" : "0""LaborSystemCode" : """LaborSystemName" : """PositionLatitude" : 緯度"PositionLongitude" : 経度"PositionAccuracy" : "0"打刻種類出勤 = "ClockIn"退出 = "ClockOut"
Package: bugzfeed
Bugzfeed is a WebSocket server that provides notifications when bugs in a
Bugzilla database change.  It is part of the [Bugzilla Change Notification
System][1].  Currently it uses Mozilla’s Pulse service but could conceivably
be extended to use other middleware such as ZeroMQ.Bugzfeed uses the tornado options format, meaning that options can be
specified either on the command line or in a Python (not.ini) config
file via the –config option.  As per standard tornado option processing,
–config overrides options specified earlier on the command line.[1]:https://wiki.mozilla.org/BMO/ChangeNotificationSystem
Package: bugzilla
Simple Bugzilla interfaceWhy?Because other libraries I found had limited API support (like no attachment support), complex implementation, and don’t seem very supported/taking
PRs :)For example most of what can be done with a 1000SLOC lib is done in this one with 100SLOC.UsageYou can and should get an API KEY from Bugzilla with a Bugzilla account to your instance, in the user preferences.
Everything is basically a DocDict (a dict() you can address like an object i.e. dict[‘x’] is also dict.x).
The contents of the DotDict reflects the exact output of the API, i.e. any JSON the API sends is what you’ll find in the
DotDict. Any data you need to send to the API uses the same names as well.
See full doc athttp://bugzilla.readthedocs.org/en/latest/api/core/v1/or/and just look at the output of the examples.Examplesimportbugzillab=bugzilla.Bugzilla(url="https://bugzilla-dev.allizom.org/rest/",api_key="your api key")#Just getting a bugbug=b.get_bug(1001)print(bug.id,bug.status)#All attributes - it's just a dot dict.print(bug)#Making a bugbug=bugzilla.DotDict()bug.product='My product'bug.component='My component'bug.summary='A test bug'bug.whiteboard'my_flag'print(b.post_bug(bug))#Adding an attachmentattachment=bugzilla.DotDict()attachment.file_name='clowns.txt'attachment.summary='Test attachement'attachment.data='some ASCII content'print(b.post_attachment(1001,attachment))#Search for stuffterms=[{'product':'MyProduct'},{'product':'MyOtherProduct'},{'status':'NEW'}]print(b.search_bugs(terms))#Or more easilyprint(b.quick_search('test bug'))TODOCurrently it does not work without an API key.Currently only support ASCII attachments as string.Some more obscure API methods are not implemented, like classifieds.
Package: bugzilla-docstrings
DescriptionLibrary for reading Bugzilla docstrings used in Insights and CFME QE. Includes a flake8 extension for validating the docstrings.
This is a fork of polarion-docstringsInstallTo install the package to your virtualenv, runpip install bugzilla-docstringsor install it from cloned directorypip install -e .Package on PyPI <https://pypi.python.org/pypi/bugzilla-docstrings>
Package: bugzscout
Python interface for the FogBugz BugzScout API.Full Documentationis available on
ReadTheDocs.InstallationpipinstallbugzscoutSupported python versions2.6, 2.73.1, 3.2, 3.3pypyGetting Started>>>importbugzscout>>>b=bugzscout.BugzScout('http://fogbugz/scoutSubmit.asp','fb-user',
                            'the-project',
                            'the-area')>>>b.submit_error('An error occurred of type blah',extra='Extra info')Command Line InterfaceThere is a command line interface for submitting errors. To simplify submitting
multiple errors, the FogBugz configuration can be set in the environment.# (Optional) Setup the environment.exportBUGZSCOUT_URL=http://fogbugz/scoutSubmit.aspexportBUGZSCOUT_USER=errorsexportBUGZSCOUT_PROJECT='My Project'exportBUGZSCOUT_AREA=Errors# Submit a new error.bugzscout--extra'Extra data for the case...''The description of the error.'See theBugzScout Command Line Interfacedocs for more detail.CeleryTheCeleryextension can be used to
asynchronously publish errors. This is the recommended pattern for using
bugzscout in production environments.# Import celery extension.importbugzscout.ext.celery_app# Submit errors asynchronously.bugzscout.ext.celery_app.submit_error.delay('The description here...',extra='The extra information here...')TheCelery workercan use the
same celery app for consuming messages.celeryworker--app=bugzscout.ext.celery_appAceleryconfig.pyfile on the PYTHONPATH can be used to configure the
celery instance. For example:exportCELERY_CONFIG_MODULE=celeryconfigceleryworker--app=bugzscout.ext.celery_appSee theCelery examplein the
docs for more detail.LicenseBSDAuthorsThomas Van Doren
Package: build
buildA simple, correct Python build frontend.See thedocumentationfor more information.Installationbuildcan be installed viapipor an equivalent via:$pipinstallbuildUsage$python-mbuildThis will build the package in an isolated environment, generating a
source-distribution and wheel in the directorydist/.
See thedocumentationfor full information.Code of ConductEveryone interacting in the build's codebase, issue trackers, chat rooms, and mailing lists is expected to follow
thePSF Code of Conduct.