Saravanan666/pypi-org huggingface dataset:
Package: buflow
Official Buflow Bindings for PythonA Python library for Buflow's API.SetupYou can install this package by using the pip tool and installing:$ pip install BuflowOr:$ easy_install BuflowSetting up a Buflow AccountSign up for Buflow athttps://buflow.comUsing the Buflow APIDocumentation for the python bindings can be found alongside Buflow's other bindings here:https://buflow.com/docsIn the standard documentation, most of the reference pages will have examples in Buflow's official bindings (including Python). Just click on the Python tab to get the relevant documentation.Exampleimportbuflowimportosbuflow.api_key=os.environ.get("STRIPE_SECRET_KEY")print("Creating task...")task_params={"questions":["Is there a tree in this image?","Is there a pedestrian in this image?",],}resp=buflow.Task.create(task_type='binary_classification',task_params=task_params,content='http://cdn.lamag.com/wp-content/uploads/sites/9/2016/07/134002821-800x500.jpg',content_type='image',priority='medium',instructions='Answer questions asked.',callback_url='https://www.example.com/labels',)print("Success:%r"%resp)task_id=resp["task_id"]print("Fetching task...")resp=buflow.Task.get(task_id)print("Success:%r"%resp)
Package: bufrpy
bufrpyPure-Python BUFR decoding librarySupports Python 2 and Python 3.Supports most common BUFR features, such as those used in NWCSAF RDT
and HRW data.QuickstartFirst install the module.% pip install bufrpyThen check that your BUFR files are readable using the module% python -m bufrpy.tool.bufr2json <templatefile> <bufrfile>—OR–% python -m bufrpy.tool.bufr2json <b-table-file> <bufrfile>—OR–% python -m bufrpy.tool.bufr2json <b-table-file> <d-table-file> <bufrfile>DocumentationSeehttp://bufrpy.readthedocs.org/en/latest/CISeehttps://travis-ci.org/tazle/bufrpy
Package: bufu
bufu - Minimal file uploader CLI for Snowflake stagebufuis a minimal file uploader CLI for Snowflake stage.Important Note: it is not a Snowflake official software.Install$ pip install bufuConfigurationbufuautomatically uses[connections]section in~/.snowsql/configto setup a connection.To usebufu, specifying current database, schema and warehouse are mandatory.Please see "Configuring SnowSQL" document to setup~/.snowsql/configfile:https://docs.snowflake.com/en/user-guide/snowsql-config.html#snowsql-config-fileUsagebufu show... List up all stages in the current schemabufu show <stage>... List up first 100 files in the stagebufu create <stage>... Create a stage in the current schemabufu put <file>... Create a stage starting with "bufu_" and put the file to the stagebufu put <file> <schema>... Put the file to the stage
Package: bugbuzz
# Bugbuzz - easy to use online debugger![Bugbuzz demo](/screencast.gif?raw=true )# Ember.js Dashboard projecthttps://github.com/victorlin/bugbuzz-python# Dashboard shortcutsVim style shortcutsC ContinueH ReturnJ NextL Step# Usage` pip install bugbuzz `then insert following lines in your code to debug`python import bugbuzz; bugbuzz.set_trace() `# Security concernsAs bugbuzz providing debugging in a software-as-service manner, all source code and local variables needed will be uploaded to the server. However, when a debugging session created, a random secret access key will be generated, and used for encryping all source code and local variables. The access key will be passed to dashboard as a part of hash tag like this`http://dashboard.bugbuzz.io/#/sessions/SECsLArhHBVHF5mrtvXHVp3T?access_key=<ACCESSKEY> `With the access key, the Ember.js dashboard app can then decrypt the source code and local variables downloaded from the server. As the access key is passed as part of hash in the URL, the server cannot see it, without the access key, your source code and local variables are not visible by the server.For more details about security topic, you can also read my article [Anonymous computing: Peer-to-peer encryption with Ember.js](http://victorlin.me/posts/2015/05/26/anonymous-computing-peer-to-peer-encryption-with-ember-js).# Run demoTo run our demo`bash git clonegit@github.com:victorlin/bugbuzz-python.git`install the project`bash virtualenv--no-site-packages.env source .env/bin/activate pip install-e. `and dependency used in thedemo.py`bash pip install requests `then`bash python demo.py `It will open a new tab in your browser for debugging.# NoticeThis is just a prototype, use it at your own risk
Package: bugcatcher
ftlFaster Than Light Command Line Test ClientInstallationInstalling with PIPpip install bugcatcherInstalling with PIP creates a console script forftlto run BugCatcher.Installing from the GitHub RepositoryDownload or clone this repository to your drive. Then use PIP to install the local package by going to its directory in your console and typing:pip install .Usageftl [-h] [--project PROJECT] [--endpoint ENDPOINT] [--async]
       [--sid SID] [--extension EXTENSIONS]
       command [items [items ...]]Retrieve a SID from the BugCatcherweb appand use it directly.ftl --project "Master" --sid 5EX3c6FNWMAv3AiIsFMGOhnMidNyDkarskyzddFq push *Or store some environmental variables.export STL_INTERNAL_SID=5EX3c6FNWMAv3AiIsFMGOhnMidNyDkarskyzddFq
export FTL_PROJECT="Master"Then minimize yourftlcommands.ftl push *ftl testftl view <test_id> --jsonftl del
Package: bugcatcher-ci
bugcatcher-ciContinuous Integration Tool Assisting in Static Code Analysis Facilitated Through BugCatcher by Faster Than LightInstallationInstalling with PIPpip install bugcatcher-ciSample IntegrationPlease view the changed files inthis PR. Setting up your testing is as easy as following this example and making sure you have an environment variable saved on CircleCI/TravisCI forFTL_SID. YourFTL_SIDcan be found on the dashboard of your BugCatcher account athttps://bugcatcher.fasterthanlight.devExample of a test run using BugCatcher-CI:% pytest -s
=============================================================== test session starts ===============================================================
platform darwin -- Python 3.8.0, pytest-5.2.2, py-1.8.0, pluggy-0.13.0
rootdir: /sampleproject
plugins: bugcatcher-0.1.6
collected 2 items                                                                                                                                 

tests/test_simple.py 
Testing codebase with BugCatcher API...
Uploading "sampleproject" code to BugCatcher...
Found a `.gitignore` file. Evaluating files...
6 of 20 local files match .gitignore patterns.
14 files ready to upload...
Local item MANIFEST.in
Local item README.md
Local item setup.py
Local item .gitignore
Local item tox.ini
Local item setup.cfg
Local item LICENSE.txt
Local item .travis.yml
Local item tests/test_simple.py
Local item tests/__init__.py
Local item sample/__init__.py
Local item sample/package_data.dat
Local item data/data_file
Local item .circleci/config.yml
Sending new files:
	.circleci/config.yml
	.gitignore
	.travis.yml
	LICENSE.txt
	MANIFEST.in
	README.md
	data/data_file
	sample/__init__.py
	sample/package_data.dat
	setup.cfg
	setup.py
	tests/__init__.py
	tests/test_simple.py
	tox.ini

14 items total changed

Running tests on "sampleproject" using BugCatcher...
BugCatcher results for "sampleproject":

Severity: low ===> tests/test_simple.py (lines 15-15)
	assert_used - Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.

Severity: low ===> tests/test_simple.py (lines 17-17)
	assert_used - Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.

Severity: low ===> tests/test_simple.py (lines 21-21)
	assert_used - Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.

Minimum Severity Level to FAIL tests: "medium"
PASSING! - All results are less than "medium" level severity.
..

=============================================================== 2 passed in 34.72s ================================================================
Package: bugger
Quick OverviewBugger is a collection of debugging tools for python applications.  All the
tools in the project have a couple common ideas/features that help to make
the library cohesive and easily usable in your application.Bugger tools help you debug your application by integrating in with
your existing application, avoiding interference at all costs.The Bugger tools have minimal dependencies.  If you have python 2.4+
and the standard library, you should be able to use the tools.The Bugger tools are well designed.  Sane defaults are provided to get
you up-and-running quickly, but it is understood that you may need to
customize things to fit your needs, we try to make this easy.The Bugger tools are well documented.  Sphinx documentation for the
project is regularly updated and available athttp://packages.python.org/bugger/Current Tools/FeaturesBugger contains an ever-expanding feature set which, at this time, includes
the following features/tools that you can plug into your application to
help you do your job…Embedded Console Tools (bugger.consoleEmbedded Telnet Console (bugger.console.TelnetInteractiveConsoleServer)
Package: bugh
bugh: Backup Github====`bugh` creates read-only local backups of all repositories in your Githubaccount, to protect you from hacking, catastrophic data loss, and your owndestructive power. To install, run:sudo pip install bughAfter installing, run `bugh [your Github username]` from the directoryin which you would like to mirror your repositories. The first invocation clonesevery repository in your Github account. Repeated invocations will run `gitpull` in already-cloned repositories, and will clone repositories that don'texist locally.Currently, `bugh` only mirrors the master branch of each repository; futureversions will allow mirroring all branches in a repository. It also does notsupport mirroring private repositories.`bugh` is made by [Will Haldean Brown][1] and is distributed under the GPLv3.Release Notes---Release versions here map to release versions on PyPI.1.0: Initial release.1.1: Increase limit on mirrorable repositories to 100.[1]:http://haldean.org
Package: bughotspots
BughotspotsA Python based implementation of the bug prediction algorithm proposed by Google:Bug Prediction at GoogleExample usageMove to the repository directory$cdapp2$bughotspots# scans the current repoScanning ../app2 repo, branch:masterFound 490 bugfix commits on the last 60 daysFixes---------------------------------------------------------------------------------Pull request #784: fix(something): update left offset value for help text-fix(something): update left offset value for help text-Pull request #783: fix(iframe.js): added display = block after stylesheets removal-fix(iframe.js): added display = block after stylesheets removal-Pull request #782: fix(iframe.js): AB-9155 - prevented removal of custom style-fix(iframe.js): AB-9155 - prevented removal of custom style-Pull request #779: fix(feature): copy changes-fix(feature): copy changes-Pull request #777: Fix: Updated image is not visible on reloading the feature due to lazy loading-fix(feature): keypress - esc / when el is not set-fix(eslint): app eslint resolve-fix(feature): clubbed f1 & f2 toggle logic | limitSelection for 3 dots-fix(AB-9045): handle effected pages-Merge branch 'master' into AB-9045-fix(AB-9045): handle effected pages-fix(feature): merging master-fix(feature): move event handler in utils-f.......Hotspots--------------------------------------------------------------------------------8.96 = app/feature/js/file1.js3.20 = app/feature/js/operations/file2.js3.07 = app/feature/js/operations/file3.js2.99 = package.json2.86 = app/feature/js/operations/file4.js2.28 = app/feature/js/file5.js2.22 = app/modules/feature/file6.js2.18 = app/modules/feature/file7.js1.95 = app/feature/js/operations/file8.js1.88 = app/feature/js/file9.jsScores mentioned in the Hotspots section are specific to the files and depict the rate of frequecny with which the file encounters errors and bug fixes. The higher the score, the more erroneous the file commit history.Parameters supportedOptional ArgumentDescriptionExample usage-h, --helpShows the help dialog describing usagebughotspots --help--daysDays ago to compute bug factor, default value: 30bughotspots --days 60--limitMax amount of results to show, default value: 10bughotspots --limit 100--branchUse a specific branch, default value: 'master'bughotspots --branch feature-branch--bugsFileUse a file with list of bugs to search in commits, default to searching commits with QF issues mentionedbughotspots --bugsFile bugs.csv--pathsProvide repository paths to look into, default to search in current directorybughotspots --paths ../app2 ../app1Build processBuild through setup.pypythonsetup.pybuildInstall the buildpythonsetup.pyinstallExecution after installationbughotspots--pathsapp2app1--days60--bugsFilebugIDs.csv--limit100
Package: bugmenot
bugmenotAn unofficial Python package to retrieve credentials fromBugMeNot.com.InstallationpipinstallbugmenotUsageCommand-lineusage:bugmenot[-h][--version]url

AnunofficialBugMeNot.comclient

positionalarguments:urlURLtothewebsite

optionalarguments:-h,--helpshowthishelpmessageandexit--versionshowprogram'sversionnumberandexitPythonimportbugmenotcredentials=bugmenot.get_credentials("<your-website>")ExampleThis command returns a list of (subsequently anonymized) bugmenot.com entries in tabular form:bugmenotoracle.comusernamepasswordsuccess_ratevotesagefake-example@gvnuclear.comBugMeNot385%15552monthsfake-example-fake-@awdrt.orgsdfdsfdsfd&-4571%21302monthsfake-example-a@wizard.comsdfdsfdsfdsfsfsdfsdd60%130531yearfake-exa@urhen.comasdfdsafasdfadsfass60%1126112monthsfake-exam@rowingbreak.comsffsdfdsfdsafasdfsa59%62748monthsanother-fake-example-entry-123@mail.comAbcsdfklj53%149897years
Package: bugone
# bugOne Python package #Simple package to interact with a bugNet. You can use both serial portsniffer or a mux serial port.The package provides a packet dumper```bugone-dumper:usage : bugone-dumper [-c host] [-s serial port] [-d hex|log|print]Diplay packet bugNet received in an human readable format```Example:```jkx@home0 ~/> bugone-dumper -c myserver -d logThu Mar 23 09:16:40 2017 => Message [65079] from 33 to 255- (33.1) -> (255.41) = 344- (33.2) -> (255.41) = 196Thu Mar 23 09:16:48 2017 => Message [21330] from 22 to 255- (22.1) -> (255.41) = 352- (22.2) -> (255.41) = 190- (22.3) -> (255.41) = 491```## Install ##To install simply use pip```shellpip install bugone```## Links ##* [PyPI Entry](https://pypi.python.org/pypi/bugone/)* [bugOne git](https://github.com/jkx/DIY-Wireless-Bug)* [DIY Wireless Bug](http://dwb.ilhost.fr/)* [mux_serial](https://github.com/marcelomd/mux_serial)
Package: bugout
bugout-pythonPython client library for Bugout APISetupAdd variables fromsample.envin you development environmentexportBUGOUT_TIMEOUT_SECONDS=5Example of usage, just filltoken,group_id,journal_idandentry_idwith proper values from your account. Or remove unnecessary variables and API calls.frombugout.appimportBugoutdefmain():bugout=Bugout()token=""group_id=""journal_id=""entry_id=""user=bugout.get_user(token=token)print(f"User name is{user.username}")group=bugout.get_group(token=token,group_id=group_id)journal=bugout.get_journal(token=token,journal_id=journal_id)entry=bugout.get_entry(token=token,journal_id=journal.id,entry_id=entry_id)search_res=bugout.search(token=token,journal_id=journal.id,query="your query",content=False)print(f"Search results:{search_res}")if__name__=="__main__":main()
Package: bugout-spire
SpireBugout custom knowledge basesSetup:Clone git repositoryInstall postgresql (https://www.postgresql.org/download/linux/ubuntu/)Install elasticsearch (https://www.elastic.co/guide/en/elasticsearch/reference/7.9/deb.html)Install requirementsCreate dev version and manage app athttps://api.slack.com/apps/Copy sample.env to dev.env and filldevfieldsexport BUGOUT_SLACK_[your info for slack apps]
...
export SPIRE_DB_URI="postgresql://postgres:postgres@localhost/brood_dev"
export ELASTICSEARCH_[your info for elasticsearch]
...
export BUGOUT_JOURNAL_EMOJI="beetle"
export SPIRE_API_URL="http://0.0.0.0:7475"
export BUGOUT_AUTH_URL="http://localhost:7474"Copyalembic.sample.initoalembic.dev.iniand correct fieldsqlalchemy.url = postgresql://postgres:postgres@localhost/brood_devRun alembic migration> ./alembic.sh -c alembic.dev.ini upgrade headInstall ngrok (https://ngrok.com/download)Run ngrok tunnel> ngrok http 7475Run server> ./dev.shSet slackOAuth & PermissionsRedirect URLs to ngrokhttps://60843a634907.ngrok.io/slack/oauthAdd OAuth Scopesapp_mentions:read
channels:history
channels:read
chat:write
commands
emoji:read
groups:history
groups:read
im:history
im:write
links:read
mpim:history
reactions:read
reactions:write
users.profile:readSet slackEvent SubscriptionsRequest URL to ngrokhttps://60843a634907.ngrok.io/slack/eventAdd eventsapp_mentions
app_uninstalled
channel_rename
emoji_changed
link_shared
message.im
reaction_added
reaction_removedRun brood local serverCreate brood userslack_installationwith hard password (this user will be managing
whole slack workspaces), generate token for this user and add it to environment atdev.envexport BUGOUT_INSTALLATION_TOKEN="<installation user token from brood>"Add slack dev bot to slackFor Shortcuts use readme (https://github.com/simiotics/spire/blob/bug-9-visual-slack-search/spire/slack/shortcuts.md)
Package: bugrest
Friendly and very light weight tool to keep track of list of things.
Designed with bugs/tickets/GTD in mindSee some generatedBug fileScreenshotKey featuresCLI(works in a terminal)Simple text file used as storage (ReStructuredText)Git, Mercurial& co friendlyColorizedin the terminalNo need to edit the text file by handAutomatically detects the “root” folder to use by finding  .hg, .svn or other version manager folder in parent directoriesMore advanced features not getting in your way if you don’t need them:PrioritiesTagsAttributesTime tracker (counts the time spent on a given task)Web Server allowingreal-time read only sharingof the listHTML exportSearch tool (grep-like)On the technical sidePurePython, no dependency required (Ok…docutils, but misses it ? ;)Simpleone filedesign, keeping things shortNo database, only the.rstfile is used for storageUsageThe command line tool isbrand works in the current directory.
If you don’t like this, feel free to editbrfile and change the following lines to absolute paths:BUGFILE = 'bugs.rst'
DONEFILE = 'fixed_bugs.rst'List bugs:brAdd new bug:br newDelete bug number 4:br rm 4Add one comment:br add 3Show full description of current bugs:br showShow description of some specific bug:br show 42Produce an html report:br html > bugs.htmlStart a web server on port 5555:br serveChange priority of item #66 (usingbugidinstead of item position):br set #66 priority 10
Package: bugrobot
Algorithm engineers or RDs often feel anxious when monitoring their running codes.Some codes can be running for several hours and even be running for several days.Such as the training of Deep Learning Models and some Big Data ETL tasks.If we can send some important message about the running status to our email or wechat,then we can know the status of our running task from our phone.Wow, that will be a great bless to the rest hairs of our Algorithm engineers.Actually, it can be achieved easily by send email with Python.If we set QQ mail remind on wechat and sending emails to our QQ Email, we cat receive the messages on our phone.Let's see how to do this!importbugrobotsubject="info@train_model.py"msg="auc=0.98"receivers=["2650115830@qq.com"]#①send message to Email!bugrobot.send_msg(receivers,subject,msg)#②send the bug information to Email if any exception occor!deff():return1/0bugrobot.monitor_run(f,["2650115830@qq.com"])
Package: bugscanner
Bug ScannerBug Scanner for Internet FreedomSub Findersubfinder(golang)InstallSub Finder$ go get -v -u github.com/projectdiscovery/subfinder/cmd/subfinderBug Scanner$ python3 -m pip install bugscanneror$ git clone https://github.com/aztecrabbit/bugscanner
$ cd bugscanner
$ python3 -m pip install -r requirements.txt
$ python3 setup.py installUsageSub FinderScan using regular quota$ ~/go/bin/subfinder -d bug.com -o bug.com.txtBug ScannerScan only when using the website quota you want to scan--mode direct --port 80$ bugscanner bug.com.txt$ bugscanner bug.com.txt --port 443--mode ssl --deep 2$ bugscanner bug.com.txt --mode ssl$ bugscanner bug.com.txt --mode ssl --deep 3--mode proxy --port 80$ bugscanner bug.com.txt --mode proxy --proxy proxy.example.com:8080$ bugscanner bug.com.txt --mode proxy --proxy proxy.example.com:8080 --port 443Updating$ python3 -m pip install --upgrade bugscannerNote--mode directforbrainfuck psiphon pro go--mode sslfor server name indicationbrainfuck tunnel shadowsocks--mode ssl --deep nis like this (cdn.bug.example.com : deep 2 = example.com, deep 3 = bug.example.com, etc)--mode proxyforbrainfuck tunnel goorbrainfuck tunnel openvpn
Package: bugs-chart.py
bugs-chart.pybugs-chart.py is a Python API that retrieves the TOP 100 information from theBugs.Installationpip install bugs-chart.pyQuickstartThe main usage of bugs-chart.py is similar tobillboard.py.>>> from bugs import *
>>> chart = ChartData(chartType=BugsChartType.Domestic)
>>> print(chart[0].json())
{
    "artist": "IVE (아이브)",
    "image": "https://image.bugsm.co.kr/album/images/256/40849/4084947.jpg",
    "lastPos": 1,
    "peakPos": 1,
    "rank": 1,
    "title": "Kitsch"
}
>>> print(chart.date)
2023-04-09 12:00:00ChartData Argumentsdate– The chart datechartTypeBugsChartType.All – 전체BugsChartType.Domestic – 국내BugsChartType.International – 해외chartPeriodBugsChartPeriod.Realtime – 실시간BugsChartPeriod.Daily – 일간BugsChartPeriod.Weekly – 주간imageSize– The size of cover image for the track. (default: 256)fetch– A boolean value that indicates whether to retrieve the chart data immediately. If set toFalse, you can fetch the data later using thefetchEntries()method.Chart entry attributesChartEntrycan be accessed using theChartData[index]syntax. AChartEntryinstance has the following attributes:title– The title of the trackartist– The name of the artistimage– The URL of the cover image for the trackpeakPos- The track's peak position on the chart.lastPos- The track's last position on the previous period.rank– The track's current rank position on the chart.DependenciesrequestsLicenseThis project is licensed under the MIT License.