Saravanan666/pypi-org huggingface dataset:
Package: tom-scimma
tom_scimmaThis module addsHopskotchandSkipsupport to the TOM Toolkit. Using this module, TOMs can query alerts submitted to the Hopskotch stream, and publish alerts to Hopskotch.InstallationInstall the module into your TOM environment:pip install tom-scimmaAddtom_scimma.scimma.SCIMMABrokerto theTOM_ALERT_CLASSESin your TOM'ssettings.py:TOM_ALERT_CLASSES = [
    'tom_alerts.brokers.mars.MARSBroker',
    ...
    'tom_scimma.scimma.SCIMMABroker'
]Though Skip alerts are public (for now), you'll need Hopskotch credentials to submit alerts. You can register for an
accounthere. Add the appropriate Skip and Hopskotch
credentials to your project'ssettings.py:BROKERS={'SCIMMA':{'url':'http://skip.dev.hop.scimma.org','api_key':os.getenv('SKIP_API_KEY',''),'hopskotch_url':'dev.hop.scimma.org','hopskotch_username':os.getenv('HOPSKOTCH_USERNAME',''),'hopskotch_password':os.getenv('HOPSKOTCH_PASSWORD',''),'default_hopskotch_topic':''}}Configurable settingsurl: The URL for Skip requests, i.e. for retrieving alerts.api_key: The API key used to authenticate/authorize with Skip. Currently unused.hopskotch_url: The URL for Hopskotch broker submissions, i.e. submitting alerts.hopskotch_username: The username used to authenticate with Hopskotch.hopskotch_password: The password used to authenticate with Hopskotch.default_hopskotch_topic: The Hopskotch topic to submit alerts to when none is provided.Available templatetagsThough the TOM Toolkit provides a broker submission templatetag,tom_scimmaprovides an additional templatetag that
includes a keyword argument for topic. To use it,Addtom_scimmato yoursettings.INSTALLED_APPS:INSTALLED_APPS=['django.contrib.admin','django.contrib.auth',...'tom_scimma']Then, addscimma_extrasto the{% load ... %}statement of your desired template:{% load bootstrap4 targets_extras ... scimma_extras %}Finally, add your desired templatetag where you would like it in your template:{% submit_upstream_scimma_form target observation_record redirect_url topic_name %}The signature and docstring of thesubmit_upstream_to_scimmabutton are as follows:```
def submit_upstream_scimma_form(target=None, observation_record=None, redirect_url=None, topic=None):
    """
    Renders a button to submit an alert upstream to a broker. At least one of target/obs record should be given.

    :param broker: The name of the broker to which the button will lead, as in the name field of the broker module.
    :type broker: str

    :param target: The target to be submitted as an alert, if any.
    :type target: ``Target``

    :param observation_record: The observation record to be submitted as an alert, if any.
    :type observation_record: ``ObservationRecord``

    :param topic: The topic to submit the alerts to.
    :type topic: str

    :param redirect_url:
    :type redirect_url: str
    """
```Running the testsIn order to run the tests, run the following in your virtualenv:python tom_scimma/tests/run_tests.py
Package: tomso
tomso: Tools for Models of Stars and their Oscillationstomsois a set of Python modules for loading and saving input and
output files for and from stellar evolution and oscillation codes.
The functions are bundled together in modules that correspond to a
specific stellar evolution code, stellar oscillation code or file
format.tomsocurrently supports theFGONGformat and various input/output files forADIPLS,GYRE,MESAandSTARS.Read the full documentation attomso.readthedocs.io.ContributingSomething isn't workingSearchthe issueson GitHub and, if your problem hasn't been addressed before, open a
new issue that describes what you tried to do, what you expected to
happen and what happened instead.  In case it's helpful, include your
operating system, Python version and NumPy version.  Also try to
include aminimal working
example,
including the files (or parts thereof) that are causing the problem.I found a bug and wrote a patch to fix itIf you've found the problem is something intomsothat doesn't work as it
should and fixed it yourself, great!  Open apull requestthat describes what the problem was and how your patch fixes it.I wanttomsoto support my favourite file formatOpen an issue with links to the specification of the file format or
where I can find (or create) examples with which to test new code.  I
have limited time to extendtomso's features unless it happens to
align with research I'm doing but I'll try my best to implement
something.ContributorsWarrick Ball
Package: tomspdb
tomspdbMy version of Python's pdb debugger pdb with convenience functions.FeaturesJump to my code and out of library code (my)Go to top and bottom of the stack (topandbottom).Interact with pdb object directly (get_pdb) useful for customizing pdbInteract with the frame object (get_frame). You can use this to look at my codeExclude directories fromwhereto make the output more readable (pretty_whereorwhere)Usingpip install tomspdb
python3 -m tomspdb script.pyPrior workThis blog postby Mauricio R. Cruz . I found this code sample very usefulipdbandpdbppare more useful alternatives to pdb
Package: tom-superevents
GW Superevent (or GRB, Neutrino) EM follow-upThis reusable TOM Toolkit app provides support for gravitational wave (GW)
superevent electromagnetic (EM) follow up observations.InstallationInstall the package into your TOM environment:pipinstalltom_supereventsIn your projectsettings.py, addtom_supereventsto yourINSTALLED_APPSsetting:INSTALLED_APPS=[...'tom_superevents',]Include the tom_superevent URLconf in your projecturls.py:urlpatterns=[...path('superevents/',include('tom_superevents.urls')),]Copytom_superevents/templates/tom_common/base.htmlinto your project root'stemplates/tom_common/base.html.Runpython manage.py migrateto create the tom_superevent models.Running the testsIn order to run the tests, run the following in your virtualenv:python tom_superevent/tests/run_tests.py
Package: tom-swift
tom_swiftNeil Gehrels Swift Observatoryfacility module for TOM Toolkit. This module uses theSwift TOO APIfor all its interactions with theSwiftObservatory. When installed and
configured, your TOM can query target visibility, submit TOO observation requests to Swift, and check TOO observation status.Swift TOO PrerequisitesIn order to submit TOO requests to Swift, you mustregister with the Swift TOO system.
Once you are registered and have logged in, you canget your shared secret, which you
will use, along with your username, to make TOO requests. See the Configuration section below.InstallationInstall the module into your TOM environment:pipinstalltom-swiftIn your projectsettings.py, addtom_swiftto yourINSTALLED_APPSsetting:INSTALLED_APPS=[...'tom_swift',]Addtom_swift.swift.SwiftFacilityto theTOM_FACILITY_CLASSESin your TOM'ssettings.py:TOM_FACILITY_CLASSES=['tom_observations.facilities.lco.LCOFacility',...'tom_swift.swift.SwiftFacility',]ConfigurationInclude the following settings inside theFACILITIESdictionary insidesettings.py:FACILITIES={...'SWIFT':{'SWIFT_USERNAME':os.getenv('SWIFT_USERNAME','anonymous'),'SWIFT_SHARED_SECRET':os.getenv('SWIFT_SHARED_SECRET','anonymous'),},}If you followed the Prerequsites section above, then you have a Swift TOO username and shared secret.
(Your shared secret isnotyour Swift TOO account password). Set environment variablesSWIFT_USERNAMEandSWIFT_SHARED_SECRETto your Swift TOO username and shared secret, respectively. (Do not check them
into any software repository).exportSWIFT_USERNAME='<your Swift TOO usename>'exportSWIFT_SHARED_SECRET='<your Swift TOO shared secret>'Thesettings.FACILITIES['Swift']configuration dictionary
above will get the values from the environment variables that you set. Your TOM will then use them to interact
with the Swift TOO API.
Package: tomtag
TomTagThis package holds several functions to process raw timetags that would be output by a tagger like e.g. a UQD Logic16.
The assumption is that the data is stored as integer times the internal resolution of the machine.
The most powerful functions arehistogramwhich does what you expect, andsync, which allows you to redefine the timetags based on a given signal that is trusted to be periodic (to a higher quality than the internal clock of the timetagger.)A very simple use example is illustrated here:https://github.com/Thomas-Jaeken/tomtag/blob/eadfe923e1eab1344aa1252ada93bb91cb31b046/example.py#L1-L10Installationpip install tomtagThis should build on all OS, but if for some reason you want to compile it yourself, clone this repo and execute these:python setup.py sdist bdist_wheel
pip install dist/tomtag-0.6.tar.gz
Package: tomte
tomteA library that wraps many useful tools (linters, analysers, etc) to keep Python code clean, secure, well-documented and optimised.Essentially does nothing else but pinning multiple packages to compatible versions, for consistency across many projects and simplicity of use.Extremely (!) opinionated by design!Wrapped toolsblackbanditisortflake8mypysafetydarglintvulturepylintdocs (various mkdocs libraries)tests (various pytest libraries)toxliccheckTo install, for instanceblack, simply specifytomte[black]==VERSION, whereVERSIONis the latest version, and then useblackCLI as required.Development:Install deps:Install poetry.Upgrading versionsCurrently, the following, somewhat hacky, process works well:Runsed -i '' "s/==/>=/g" pyproject.tomlto remove strict version requirements.poetry shellandpip install toml requestsRunpython ./bump_to_latest.pyCheck non-strict versions inpyproject.tomland make them strict by manually running thepoetry add PACKAGE@==VERSION --optional. Finaly, runpoetry updateName"The Swedish hustomte (house elf/gnome) is a quiet little guy, dressed mostly in gray and red, living at your house or farmsted helping out by taking care of things around the house and keep everyone safe.""A tomte and his son enjoying quiet company of the cat. Illustration by Rolf Lidberg."Release guide:Finish edits, bump versions inpyproject.tomlandtomte/__init__.py, thenpoetry lock, thenrm -rf dist, thenpoetry publish --build --username=<username> --password=<password>.
Package: tom-tns
Transient Name Server (TNS) Report and Classification plugin for TOM ToolkitTOMtoolkit module for reporting transients to the TNSInstallationInstall the package into your TOM environment:pipinstalltom-tnsIn your projectsettings.py, addtom_tnsto yourINSTALLED_APPSsetting:INSTALLED_APPS=[...'tom_tns',]Add your TNS credentials to yoursettings.pyif they don't already exist for the TNS Broker.If you don't have access to a TNS Bot for your TOM, you can make one from theTNS website.NOTE: If you are testing on the sandbox, the sandbox is only synced every Sunday, so new bots created using the above link
won't show up until after the next update.BROKERS={...'TNS':{'bot_id':os.getenv('TNS_BOT_ID',''),# This is the BOT ID you plan to use to submit to TNS'bot_name':os.getenv('TNS_BOT_NAME',''),# This is the BOT name associated with the above ID'api_key':os.getenv('TNS_API_KEY',''),# This is the API key for the associated BOT'tns_base_url':'https://sandbox.wis-tns.org/api',# This is the sandbox URL. Use https://www.wis-tns.org/api for live submission.'group_names':['bot_group','PI_group'],# Optional List. Include if you wish to use any affiliated Group Names when reporting.},}Include the tom_tns URLconf in your projecturls.py:urlpatterns=[...path('tns/',include('tom_tns.urls',namespace='tns')),]Once configured, aTNSbutton should appear below the Target Name.NOTE: Users who are usingtomtoolkit<2.15.12will have to add the TNS button manually.
Package: tomtombrumbrum
tomtombrumbrumThe package is still under construction.This library aims to simplify the usage of the TomTom API.To use their API you need an API key.For more information, go to theofficial website.This project and its authors are not affiliated in any way to TomTom. For more information, see DISCLAIMER.txt.Author: Gabriele3viUsageMatrix routing v2 API...
Package: tomwer
tomwertomwer is offering tools to automate acquisition and reconstruction processes for Tomography.
It contains:a library to access each acquisition process individuallygui and applications to control main processes (reconstruction, data transfert...) and execute them as a stand alone application.an orange add-on to help users defining their own workflow (http://orange.biolab.si).. image::http://www.edna-site.org/pub/doc/tomwer/extra/tomwer_start_short.gif.. |Gitlab Status| image::https://gitlab.esrf.fr/tomotools/tomwer/badges/master/pipeline.svg:target:https://gitlab.esrf.fr/tomotools/tomwer/pipelinesDocumentationLatest documentation <https://tomotools.gitlab-pages.esrf.fr/tomwer/>_InstallationStep 1 - tomwer
'''''''''''''''To install it with all 'features':.. code-block:: bashpip install tomwer[full]alternatively you can install the master branch from.. code-block:: bashpip install git+https://gitlab.esrf.fr/tomotools/tomwer/#egg=tomwer[full]Step 2 - update orange-canvas-core and orange-widget-base (Optional)
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''To access 'processing' wheels and 'reprocess action' you might want to install forks of update orange-canvas-core and orange-widget-base. This is optional and projects works with native orange projects.. code-block:: bashpip install git+https://github.com/payno/orange-canvas-core --no-deps --upgrade
pip install git+https://github.com/payno/orange-widget-base --no-deps --upgradeLaunching applications
::::::::::::::::::::::After the installation tomwer is embedding several applications.Those applications can be launched by calling:.. code-block:: bashtomwer appName {options}.. note:: if you only calltomwerthen the man page will be displayed... note:: You can access each application help using ``.. code-block:: bash

   tomwer appName --helptomwer canvas - orange canvas
'''''''''''''''''''''''''''''You can launch the canvas to create workflows from the different 'bricks'.. code-block:: bashtomwer canvas.. note:: you can also useorange-canvas.. note:: if your installed a virtual environment do not forget to active it :.. code-block:: bash

   source myvirtualenv/bin/activateDocumentation
:::::::::::::.. code-block:: bashsphinx-build doc build/htmlThe documentation is build in doc/build/html and the entry point is index.html.. code-block:: bashfirefox build/html/index.html.. note:: the build of the documentation need sphinx to be installed. This is not an hard dependacy. So you might need to install it.
Package: ton
🌐 IntroductionThis library allows you to work with theTON blockchainAPI from Python.Features:Creating and importing walletGetting wallets balanceGetting transactions of any walletTransfer coinsExecuting methods of smart-contractsTransfer NFTHow to install:pipinstalltonIf you have anillegal instructionerror then you need to build libtonlibjson by yourself:gitclonehttps://github.com/psylopunk/ton&&cdton
chmod+xbuild_tonlib.sh&&./build_tonlib.sh# docker is neededGetting startedExampleswill give a general look at the library. They describe almost all supported methods, but in addition, below you can see each method in detail. To make a custom request tolibtonlibjson, check out list of available methods and execute it usingclient.executeMore documentation hereTroubleshootingFound a bug? Or just improvments? -- Read more about this inTroubleshootingDonateBTC – 192gK2df3izkpaNgcMbfEDrLgoofyjjfeCTON –EQCl1Ug9ZT9ZfGyFH9l4q-bqaUy6kyOzVPmrk7bivmVKJRRZ
Package: tona
TONAWhat's TONA?It is an ALL IN ONE tool that will help increase your personal productivity.Our goal is to create a lightweight tool with a minimalist interface, so that users can focus on what matters most.Tools⌛️ Time Tracking📑 Project Manager🎯 Habit Manager🚀 OKR ManagerIncomingContactsWalletPassword ManagerGetting startedInstall using pip$pipinstall-Utona
$tonawebapp
$Runningonhttp://0.0.0.0:5001/(PressCTRL+CtoquitInstall using docker-compose$docker-composeup
$Runningonhttp://0.0.0.0:5001/(PressCTRL+CtoquitContributeWe invite you to try outtonaand file any issues at github issues page. Patches are most welcome!LinksIssues:https://github.com/sentilis/tona/issuesDiscussions:https://github.com/sentilis/tona/discussions
Package: toncenter
toncenterToncenter API Python3 async wrap.Installationpip3installtoncenterDocumentation (WIP)https://witer33.github.io/toncenter/Examplefromtoncenter.clientimportClientimportasyncioasyncdefmain():asyncwithClient(open("main_api_token.txt").read())asclient:info=awaitclient.get_masterchain_info()# Gets masterchain infoprint(info.last)# Prints last blockif__name__=="__main__":asyncio.run(main())Example without context managerfromtoncenter.clientimportClientimportasyncioasyncdefmain():client=Client(open("main_api_token.txt").read())awaitclient.start()info=awaitclient.get_masterchain_info()# Gets masterchain infoprint(info.last)# Prints last blockawaitclient.stop()# ALWAYS call this method.if__name__=="__main__":asyncio.run(main())
Package: toncli
toncliThe Open Network cross-platform smart contract command line interface.Easy to deploy and interact with TON smart contracts.🔧 InstallationToncli support Windows / macOS (m1 / intel) / Linux / Docker, installation guide can be
found:INSTALLATION.md📚 Usage and docsNew totoncli?Try:Quick start guideAll other documentation lists indocs/Lessons🇬🇧 Ton FunC lessons Eng🇷🇺 Ton FunC lessons RusContributor GuideInterested in contributing? Feel free to create issues and pull requests.We are trying to process all tasks through issues. You can take own one 🥳Features and statusFeatureStatusfift/func/lite-serverusage✅Easy bootstrap project sampleswallet✅Deploy-wallet for auto send TON to contracts and tests✅Compile func tobuild/fromfunc/withfiles.yaml✅Auto send TON to init contract address✅Deploy to mainnet / testnet / ownnet✅Project interact after deploy: easily send messages, run getmethods, run fift parsers on getmethods output✅Load from hard project structure (example:src/projects/wallet)✅Run remote contracts locally (get cells from chain and run locally to get error / debug / etc.)✅Get contract address bytoncli addrs✅Docs for contract creation for beginners✅Project tests withrunvmcode✅Windows & Linux support✅Unit tests engine✅Add more project samples with advanced usage✅CommandsAll commands could be fined indocs/advanced/commands.mdConfigurationConfig folder will create on first deploy, all fift / func libs will copy to it, also deploy wallet contract will be
createdDeploy process (how it's actually work)Check network (testnet, mainnet) configuration locally (in config user folder)If no config found - download from URL in config.iniCheck deploy wallet locally (in config user folder)If it's first time - simple wallet will be created in config folderMessage with wallet address and tips will be displayed (user need to send some TON coin on it)If there is no TON in deploy contract - script will exit and notify user to update deployer balanceWill run tests onfift/data.fif/fift/message.fif(if exist) /fift/lib.fif(if exist)  before creating deploy
messageThis will check all files are correctAlso, you can run custom logic - for example create keys in build/Will calculate address of contract and display it to userWill send money from deploy walletWill deploy your contractExternal messagewill
be createdBoc will generatedWill invoke sendfile in lite-client (TODO: use native python lib, not lite-client)Developmentgit clone git@github.com:disintar/toncli.git
cd toncli && pip install -e .If you wish to update toncli locally you can usepip install -e path/to/toncli/rootfolder/command anytime after you make changes to the toncli source code.Version migration0.24Please, usetoncli update_libs0.22The easy migration method - removefift-libs,func-libsfrom~/.config/tonclior delete whole
directory~/.config/toncliHelp and questionsFeel free to ask questions and help in official telegram chats:Russian/English
Package: toncli-win
toncliTON smart contract command line interfaceStateWorking!Usage and docsNew totoncli?Try:Quick start guideAll other documentation lists indocs/Contributor GuideInterested in contributing? Feel free to create issues and pull requests.There is two main tasks and many TODOs.Main tasks are - not to use lite-client / fift / func. All can be done with python.There is many TODOs in code - feel free to fix them and create PRsFeatures and statusFeatureStatusfift/func/lite-serverusage✅Easy bootstrap project sampleswallet✅Deploy-wallet for auto send TON to contracts and tests✅Compile func tobuild/fromfunc/withfiles.yaml✅Auto send TON to init contract address✅Deploy to mainnet / testnet✅Project interact after deploy: easily send messages, run getmethods✅Load from hard project structure (example:src/projects/wallet)✅Run remote contracts locally (get cells from chain and run locally to get error / debug / etc.)✅Get contract address bytoncli address❌Gas auto calculation for store & deploy❌Add more project samples with advanced usage❌Project tests withrunvmcode❌Project debug❌Library support❌Init Message support  (with signature)❌Docs for contract creation for beginners❌Advanced user-friendly docs onfift,func❌CommandsAll commands could be fined indocs/advanced/commands.mdConfigurationConfig folder will create on first deploy, all fift / func libs will copy to it, also deploy wallet contract will be
createdDeploy process (how it's actually work)Check network (testnet, mainnet) configuration locally (in config user folder)If no config found - download from URL in config.iniCheck deploy wallet locally (in config user folder)If it's first time - simple wallet will be created in config folderMessage with wallet address and tips will be displayed (user need to send some TON coin on it)If there is no TON in deploy contract - script will exit and notify user to update deployer balanceWill run tests onfift/data.fif/fift/message.fif(if exist) /fift/lib.fif(if exist)  before creating deploy
messageThis will check all files are correctAlso, you can run custom logic - for example create keys in build/Will calculate address of contract and display it to userWill send money from deploy walletWill deploy your contractExternal messagewill
be createdBoc will generatedWill invoke sendfile in lite-client (TODO: use native python lib, not lite-client)Developmentgit clone git@github.com:disintar/toncli.git
cd toncli && pip install -e .