semvec/pypi-packages huggingface dataset:
timeback-sdk 0.1.10b20260219212635
Timeback SDK for Python - adapters for FastAPI, Django, and more
Requires Python: >=3.12

# Timeback SDK

Server-side SDK for integrating Timeback into Python web applications.

## Installation

```bash
# pip
pip install timeback-sdk[fastapi]
pip install timeback-sdk[django]

# uv (add to a project)
uv add "timeback-sdk[fastapi]"
uv add "timeback-sdk[django]"

# uv (install into current environment)
uv pip install "timeback-sdk[fastapi]"
uv pip install "timeback-sdk[django]"
```

## FastAPI

```python
from fastapi import FastAPI
from timeback.fastapi import create_timeback_router

app = FastAPI()

timeback_router = create_timeback_router(
    env="staging",
    client_id="...",
    client_secret="...",
    identity={
        "mode": "sso",
        "client_id": "...",
        "client_secret": "...",
        "get_user": lambda req: get_session_user(req),
        "on_callback_success": lambda ctx: handle_sso_success(ctx),
    },
)

app.include_router(timeback_router, prefix="/api/timeback")
```

## Django

```python
# Coming soon
```
timeback-common 0.1.10b20260219212635
Shared infrastructure for Timeback Python clients
Requires Python: >=3.12

# timeback-common

Shared infrastructure for Timeback Python clients.

## Installation

```bash
# pip
pip install timeback-common

# uv (add to a project)
uv add timeback-common

# uv (install into current environment)
uv pip install timeback-common
```

```python
from timeback_common import BaseTransport, APIError, Paginator, where_to_filter

class MyTransport(BaseTransport):
    ENV_VAR_BASE_URL = "MY_SERVICE_BASE_URL"
    ENV_VAR_AUTH_URL = "MY_SERVICE_TOKEN_URL"
    ENV_VAR_CLIENT_ID = "MY_SERVICE_CLIENT_ID"
    ENV_VAR_CLIENT_SECRET = "MY_SERVICE_CLIENT_SECRET"
```

## Components

| Module | Description |
|--------|-------------|
| `transport` | Base HTTP transport with OAuth2 client credentials |
| `errors` | Shared exception hierarchy (APIError, NotFoundError, etc.) |
| `pagination` | Async Paginator for list endpoints |
| `filter` | `where_to_filter()` for type-safe filtering |

## Usage

This package is used internally by:
- `timeback-oneroster`
- `timeback-caliper`
- `timeback-edubridge`
- `timeback-core`
ag-quant 2026.2.19.5
简易量化框架
Requires Python: >=3.9

数据分为两种, <市场价格数据>和<因子构造基础数据>，要求这两种数据在上传时命名一样。
这两种数据缺一不可，因为没有<市场价格数据>就无法进行横截面分析和回测，没有<因子构造基础数据>因子就无法生成具体值
举个例子：我们现在有大豆的<CBOT连续合约的市场价格数据>和<大连期货交易所的持仓数据>,我们想用持仓数据构建一个“持仓波动率”因子，然后测试这个因子的表现（也就是横截面分析）。那么此时<CBOT连续合约的市场价格数据>就是<市场价格数据>，<大连期货交易所的持仓数据>就是<因子构造基础数据>。

因子和策略，分为构造和具体值，千万不能搞混。
同一个因子构造，在不同交易品种数据下会有不同的因子值。比如我们构造了一个因子叫<价格动量>，那么具体到大豆还是菜籽，会得到完全不同的因子具体值，但是他们都在用共同的一个因子构造叫<价格动量>策略同理，同一个策略构造，在不同市场环境下会产生完全不同的策略具体值（或者换一个熟悉的名字叫做交易信号）。
因子构造需要<因子构造基础数据>生成具体值，然后在<市场价格数据>下进行横截面分析。策略构造需要结合因子具体值生成策略具体值（交易信号），然后在<市场价格数据>下进行回测。横截面分析和回测的主体千万不能搞混。
onako 0.6.1
Dispatch and monitor Claude Code tasks from your phone
Requires Python: >=3.10
Keywords: claude, claude-code, tmux, orchestrator, ai

# Onako

Dispatch and monitor Claude Code tasks from your phone.

Onako is a lightweight server that runs on your machine. It spawns Claude Code sessions in tmux, and you monitor them through a mobile-friendly web dashboard. Fire off tasks from an iOS Shortcut or the dashboard, check in from anywhere.

## Install

```bash
pipx install onako
```

Requires [tmux](https://github.com/tmux/tmux) and [Claude Code](https://docs.anthropic.com/en/docs/claude-code).

## Usage

```bash
onako                              # starts server, drops you into tmux
onako --session my-project         # custom session name
```

If you're already inside tmux, onako auto-detects your session and skips the attach. Open http://localhost:8787 on your phone (same network) or set up [Tailscale](https://tailscale.com) for access from anywhere.

```bash
onako stop                         # stop the server
onako status                       # check if running
onako clean                        # remove worktrees for finished tasks
onako reset                        # full teardown: stop, kill session, clean worktrees
onako serve                        # foreground server (for development)
onako version                      # print version
```

### Dispatching tasks from the CLI

```bash
onako task "fix the login bug"                          # create a task
onako task "add tests" --branch feat/tests              # run in a git worktree
onako task "refactor auth" --branch feat/auth --base-branch develop
```

### Flags

```bash
onako --dangerously-skip-permissions    # skip Claude Code permission prompts
onako --no-attach                       # start server without attaching to tmux
onako --dir /path/to/project            # set working directory for tasks
```

### Adopting existing tmux windows

If you already have work running in another tmux session, move those windows into onako's session so they show up in the dashboard:

```bash
tmux move-window -s <session>:<window> -t onako
```

## How it works

Onako monitors all tmux windows in the configured session. Windows it creates (via the dashboard) are "managed" tasks. Windows created by you or other tools are discovered automatically as "external" — both get full dashboard support: view output, send messages, kill.

Task state is persisted in SQLite so it survives server restarts.