semvec/pypi-packages huggingface dataset:
iotapay 1.0.3
Pay using IOTA
Keywords: iotapay

`IOTAPAY <https://iotapay.dev/>`_
=================================

Python library to Pay using IOTA

=====
Setup
=====

Install the library: ``pip install iotapay``

Import package: ``from iotapay.iotapay import Iotapay``

Initialize: ``Iotapay('https://url:14265', 'TWQH9ETUWNDTRHSQVNLOSFMSTQLHRTZQGDTFUHEKRNPVDRQGHQEARNLSXXCXGICCVWBQHOHWPYZSHJYTC')``

===============
Basic functions
===============

***********
Get Balance
***********

``pay = Iotapay('https://url:14265', 'YOUR SEED')``

Retrieve balance: `pay.get_balance({})`

***
Pay
***

``data = {'json_data': {'version': '0.0.9',}, 'tag': 'ACYCLICIOTAPAYLIOTA99999999', 'to_address': 'ADDRESS', 'amount': 10}``

Pay : ``pay.pay(data)``

More Functions coming soon.
---------------------------

NOTE: Please, use proper **iota node url**, **ADDRESS** and your **SEED** to initialise.
timeline 0.0.7
Timeline module for modelling a series of actions.

*************************************************
python-timeline: Modelling of a series of actions
*************************************************

    Copyright (c) 2011, Canonical Ltd

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU Lesser General Public License as published by
    the Free Software Foundation, version 3 only.
   
    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU Lesser General Public License for more details.
   
    You should have received a copy of the GNU Lesser General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.
  
The timeline package provides a way to model a series of actions. For instance,
during a web request the appserver might call out to a number of backend
services, make sql queries and memcached lookups. All of these actions can be
tracked in a single timeline, and that serialised or analysed for slow points.

Dependencies
============

* Python 2.6+

* pytz

Testing Dependencies
====================

* subunit (http://pypi.python.org/pypi/python-subunit) (optional)

* testtools (http://pypi.python.org/pypi/testtools)

Usage
=====

Create a timeline object:

 >>> from timeline.timeline import TimeLine
 >>> log = TimeLine()

Then add actions:

 >>> action = log.start('mycategory', 'mydetails')

Perform your action and then tell the action it has finished:

 >>> action.finish()

At this point you can start another action. If you wish to nest actions, pass
allow_nested=True to start().

One of the things needed when working with timelines in complex applications is
locating the right one. Timeline provides a helper for WSGI apps:

 >>> from timeline import wsgi
 >>> app = wsgi.make_app(inner_app)

Calls to app will now inject a 'timeline.timeline' variable into the wsgi
environwhich can be used by inner_app to record actions.


Installation
============

Either run setup.py in an environment with all the dependencies available, or
add the working directory to your PYTHONPATH.


Development
===========

Upstream development takes place at https://launchpad.net/python-timeline.
To setup a working area for development, if the dependencies are not
immediately available, you can use ./bootstrap.py to create bin/buildout, then
bin/py to get a python interpreter with the dependencies available.

To run the tests use the runner of your choice, the test suite is
timeline.tests.test_suite.

For instance::

  $ bin/py -m testtools.run timeline.tests.test_suite

If you have testrepository you can run the tests with testr::

  $ testr run
injectslib 0.0.1
Official API package for https://injects.cert.pl

# injectslib

Python APi for [https://injects.cert.pl](https://injects.cert.pl).
Compatible with python2 and python3.

## Info

**Contact email**: msm@cert.pl

## Example

```python
import sys
from injectslib import InjectsApi


if len(sys.argv) == 1:
    print("Usage: example.py api_token")
api = InjectsApi(sys.argv[1])

print("Attacks on {}:".format(api.organisation().name))
for attack in api.attacks():
    print(" - attack by {}, first observed at {}".format(
        attack.family,
        attack.first_seen_iso
    ))
    for inject in attack.injects:
        print("   - inject when url like {}".format(inject.url_pattern))
    for action in attack.actions:
        print("   - {} when url like {}".format(
            action.act_type, action.url_pattern
        ))
```
pydero-jonlindg 1.0
Python wrapper for interacting with the DERO blockdag

# pydero

Pydero is a python wrapper for interacting with smart contracts on the DERO STARGATE testnet. Installing smart contracts is currently not supported, only executing a function on an already installed smart contract on the DERO block dag or query the value of stored variables in the smart contract. Executing a function requires a running dero cli-wallet with the flag --rpc-server. Retrieving the value of a stored variable requires a derod process running. 

# usage

First import the relevant classes
```
from pydero import Contract, Connection
```

Instantiate a python Contract object by the command 

```
contract = Contract(abi=abi,connection=connection,scid=scid)

```

connection should be an instance of the Connection class, scid should be a string with the scid of the smart contract on the dero blockdag. abi should be a dictionary of the form corresponding to the functions and parameters of the smart contract and the parameter types should be strings that are either "Uint64" or "String". For example, if the contract has two functions called Function1 and Function2, the first with one Uint64 and one String parameter and the second with no parameters, the abi is


```
from collections import OrderedDict
abi={"Function1":OrderedDict({"ParameterName1":"Uint64","ParameterName2":"String"}),"Function2":{}}

```

The order of function parameters is important, and therefore it is recommended to use an OrderedDict instead. Instead of specifying the abi manually, it can be loaded from the dero blockdag. This requires a valid scid and a working connection to a dero daemon.
```
contract.set_abi_from_db()
```

 To call a function on the contract, we simple do


```
contract.Function1(123,"abc")
```

To obtain the value of a stored variable called Foo:
```
contract.get_attribute("Foo")
```

We can also query different information form the running wallet, for example
```
connection.get_balance()
```

We can also query the daemon for information, for example
```
connection.get_last_block_header()
```


See the python scripts simple_test.py and test2.py for more examples.
pydero 1.0.0
Python wrapper for interacting with the DERO blockdag

# pydero

Pydero is a python wrapper for interacting with smart contracts on the DERO STARGATE testnet. Installing smart contracts is currently not supported, only executing a function on an already installed smart contract on the DERO block dag or query the value of stored variables in the smart contract. Executing a function requires a running dero cli-wallet with the flag --rpc-server. Retrieving the value of a stored variable requires a derod process running. 

# usage

First import the relevant classes
```
from pydero import Contract, Connection
```

Instantiate a python Contract object by the command 

```
contract = Contract(abi=abi,connection=connection,scid=scid)

```

connection should be an instance of the Connection class, scid should be a string with the scid of the smart contract on the dero blockdag. abi should be a dictionary of the form corresponding to the functions and parameters of the smart contract and the parameter types should be strings that are either "Uint64" or "String". For example, if the contract has two functions called Function1 and Function2, the first with one Uint64 and one String parameter and the second with no parameters, the abi is


```
from collections import OrderedDict
abi={"Function1":OrderedDict({"ParameterName1":"Uint64","ParameterName2":"String"}),"Function2":{}}

```

The order of function parameters is important, and therefore it is recommended to use an OrderedDict instead. Instead of specifying the abi manually, it can be loaded from the dero blockdag. This requires a valid scid and a working connection to a dero daemon.
```
contract.set_abi_from_db()
```

 To call a function on the contract, we simple do


```
contract.Function1(123,"abc")
```

To obtain the value of a stored variable called Foo:
```
contract.get_attribute("Foo")
```

We can also query different information form the running wallet, for example
```
connection.get_balance()
```

We can also query the daemon for information, for example
```
connection.get_last_block_header()
```


See the python scripts simple_test.py and test2.py for more examples.