semvec/pypi-packages huggingface dataset:
jesse-ftx-futures 0.1.0
FTX Futures driver for Jesse framework
Requires Python: >=3.7

# FTX FUTURES plugin for Jesse

This is the initial release of the FTX Futures driver for Jesse.
At the moment:
* it is only meant for importing candles and running backtests
* it supports only Perpetual futures (*-PERP)


## Installation 
Install by running:

```sh
pip install jesse-ftx-futures
```

### Register your driver
Now you need to tell Jesse where to find this driver. We do that by adding it as a driver for importing candles in `plugins.py` file that exists in the root of Jesse projects. Here is an example where I register a driver for the FTX FUTURES exchange:

```py
from jesse.modes.import_candles_mode.drivers.binance import Binance
from jesse.modes.import_candles_mode.drivers.binance_futures import BinanceFutures
from jesse.modes.import_candles_mode.drivers.binance_inverse_futures import BinanceInverseFutures
from jesse.modes.import_candles_mode.drivers.bitfinex import Bitfinex
from jesse.modes.import_candles_mode.drivers.coinbase import Coinbase
from jesse.modes.import_candles_mode.drivers.testnet_binance_futures import TestnetBinanceFutures

from jesse_ftx_futures import FTXFutures

import_candles_drivers = {
    'Binance': Binance,
    'Binance Futures': BinanceFutures,
    'Binance Inverse Futures': BinanceInverseFutures,
    'Testnet Binance Futures': TestnetBinanceFutures,
    'Bitfinex': Bitfinex,
    'Coinbase': Coinbase,
    'FTX Futures': FTXFutures
}
```

Now I should be able to run import candles from FTX (in this example for Perpetual):

```sh
jesse import-candles 'FTX Futures' 'BTC-USDT' '2012-06-04'
```

In this example for an expiring future (*it won't work on baktesting for now*):

```sh
jesse import-candles 'FTX Futures' 'BTC-0924' '2012-06-04'
```


### Add new config values for running backtests
Usually the reason for importing candles in the first place is to run backtests on them. So we need to tell Jesse where to find the config values for our newly added exchange in order for it run backtests on it. 

We can do that by opening `config.py` and coping and pasting values from an existing exchange such as `Binance Futures` and changing the values according to our needs for out exchange:
```py
# https://www.ftx.com
'FTX Futures': {
    'fee': 0.0006,

    # backtest mode only: accepted are 'spot' and 'futures'
    'type': 'futures',

    # futures mode only
    'settlement_currency': 'USDT',
    # accepted values are: 'cross' and 'isolated'
    'futures_leverage_mode': 'isolated',
    # 1x, 2x, 10x, 50x, etc. Enter as integers
    'futures_leverage': 3,

    # used for spot exchange only
    'assets': [
        {'asset': 'USDT', 'balance': 10_000},
    ],
},
```
redesign 2021.7
Namespace for Redesigning Psychiatry packages
Requires Python: >=3.6

# Namespace for Redesigning Psychiatry packages

This project represents the implicit namespace `redesign` in the names of
packages from the
[Redesigning Psychiatry](https://github.com/redesigningpsychiatry)
programme (such as `redesign.health`).

Note that this project is not a dependency of such packages. It exists merely
to indicate that an explicit module named `redesign` would cause a namespace
conflict with these packages. Installing this package will add a
`redesign.info` module that attaches a docstring to the `redesign` namespace
when imported.
pycodepack 1.0.2
A tiny tool to convert python files to dynamic libraries
Requires Python: >=3.6

# pycodepack
Compile python code to dynamic library using `Cython`.

## Installation

```shell
pip install pycodepack
```

## Usage

After installation, there is a runable module called `py2dylib`. Suppose your code is in `/home/code/test_project` and `run.py` is the entrypoint file, you can convert the python files in that folder to dynamic libraries by running

```shell
python -m py2dylib --folder /home/code/test_project --ignore run.py
```

If there is no `/home/code/test_project_build` here, it will copy the folder and compile the python code in that folder. Otherwise, it will try append `_` to the folder until it isn't exist. It's out-of-project building. You can specify `--inplace` option to build in original folder. 

Besides, the`pycodepack` is running under `incremental building` mode by default, which means it only builds those files that changed since last building. You can change it by specifying `--build_mode` option.

Run `python -m py2dylib --help` for more information.