semvec/pypi-packages huggingface dataset:
google-drive-cli-for-agents 0.1.1
CLI for Google Drive
Requires Python: >=3.10

# google-drive-cli-for-agents

CLI for Google Drive using the official Google API Python client.

## Features
- OAuth login without mandatory `gcloud`
- `pipx`-friendly install (`gdrive` available globally)
- List folder contents via folder ID or folder link
- Upload local files to a folder via folder ID or folder link
- Download files via file ID or file link
- Move files to trash via file ID or file link
- Diagnostics with `gdrive doctor`

## Install (Recommended)

```bash
python3 -m pip install --user pipx
python3 -m pipx ensurepath
pipx install google-drive-cli-for-agents
```

Verify:

```bash
gdrive --version
```

Upgrade:

```bash
pipx upgrade google-drive-cli-for-agents
```

## Install From Source

Local development:

```bash
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
```

Install via pipx from local clone:

```bash
pipx install -e /absolute/path/to/google-drive-cli
```

## OAuth Setup

Create a Google OAuth client of type **Desktop app**, then run:

```bash
gdrive auth login --client-secret /absolute/path/to/client_secret.json
```

Readonly token:

```bash
gdrive auth login --readonly --client-secret /absolute/path/to/client_secret.json
```

Inspect local credentials:

```bash
gdrive auth whoami
gdrive doctor
```

## Usage

List a folder (or root if omitted):

```bash
gdrive ls --folder https://drive.google.com/drive/folders/<folder-id>
gdrive ls --folder <folder-id>
gdrive ls
```

Upload a file:

```bash
gdrive upload ./report.csv --folder <folder-id>
gdrive upload ./report.csv --folder https://drive.google.com/drive/folders/<folder-id>
```

Download a file:

```bash
gdrive download --file <file-id>
gdrive download --file https://drive.google.com/file/d/<file-id>/view --output-path ./report.csv
```

Move a file to trash:

```bash
gdrive trash --file <file-id>
gdrive trash --file https://drive.google.com/file/d/<file-id>/view
```

## Output Formats

`gdrive ls` supports:
- `--output table` (default)
- `--output json`
- `--output csv --csv-path ./files.csv`

`gdrive upload` supports:
- `--output table` (default)
- `--output json`

## Credentials Path

By default credentials are stored at:
- `~/.config/gdrive-cli/credentials.json`

Override with env vars:
- `GDRIVE_CONFIG_DIR`
- `GDRIVE_CREDENTIALS_FILE`

## ADC Fallback (Optional)

If preferred, ADC via `gcloud` still works:

```bash
gcloud auth application-default login \
  --client-id-file=/absolute/path/to/client_secret.json \
  --scopes=https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/drive
```

## Publishing

Build artifacts:

```bash
python -m build
```

Upload manually:

```bash
python -m twine upload dist/*
```
mxpy 11.3.1
MultiversX Smart Contracts Tools
Requires Python: >=3.10

# Description
Python Command Line Tools for interacting with Multivers<sup>X</sup>.

## Documentation
[docs.multiversx.com](https://docs.multiversx.com/sdk-and-tools/sdk-py/)

## CLI
[CLI](CLI.md)

## Distribution
[pipx](https://docs.multiversx.com/sdk-and-tools/sdk-py/installing-mxpy/) [(PyPi)](https://pypi.org/project/multiversx-sdk-cli/#history)

## Development setup

Clone this repository and cd into it:

```
git clone https://github.com/multiversx/mx-sdk-py-cli.git
cd mx-sdk-py-cli
```

### Virtual environment

Create a virtual environment and install the dependencies:

```
python3 -m venv ./venv
source ./venv/bin/activate
pip install -r ./requirements.txt --upgrade
```

Install development dependencies, as well:

```
pip install -r ./requirements-dev.txt --upgrade
```

Allow `pre-commit` to automatically run on `git commit`:
```
pre-commit install
```

Above, `requirements.txt` should mirror the **dependencies** section of `pyproject.toml`.

If using VSCode, restart it or follow these steps:
 - `Ctrl + Shift + P`
 - _Select Interpreter_
 - Choose `./venv/bin/python`.

### Using your local `mxpy`

If you want to test the modifications you locally made to `mxpy`, set `PYTHONPATH` with the path to your local repository path.

For example, if you cloned the repository at `~/mx-sdk-py-cli`, run:

```
export PYTHONPATH="~/mx-sdk-py-cli"
```

Then `mxpy` will use the code in your local repository.
bex-hooks-python 0.1.0
bex-hooks-python
Requires Python: >=3.11

# bex-hooks-python

Python-related hooks for **bex**. This package provides hooks to create and manage Python virtual environments and their dependencies.

## Usage
`bex-hooks-python` is available on PyPI.

Add the plugin package to the `requirements` section of your `bex` bootstrap header:

```yaml
# /// bootstrap
# requires-python: ">=3.11,<3.12"
# requirements: |
#   bex-hooks
#   bex-hooks-python
# entrypoint: bex_hooks.exec:main
# ///
```

Then enable the plugin in your configuration:
```yaml
config:
  plugins:
    - bex_hooks.hooks.python
```

## Hooks

### `python/setup-python`

Sets up a Python virtual environment for a specified version and synchronizes its dependencies using `uv`. When both `requirements` and `requirements_file` are provided, their contents are merged into a single set of requirements.

#### Arguments

| Name                | Type          |    Default   | Description                                                                                             |
|---------------------|---------------|:------------:|---------------------------------------------------------------------------------------------------------|
| `version`           | `str`         | *(required)* | Python version to provision (e.g. `">=3.11,<3.12"`)                                                     |
| `uv`                | `str \| None` | `None`       | Version of `uv` to use                                                                                  |
| `requirements`      | `str`         | `""`         | Inline requirements (e.g. `"requests==2.32.0"`).                                                        |
| `requirements_file` | `list[str]`   | `[]`         | One or more requirements file paths.                                                                    |
| `activate_env`      | `bool`        | `False`      | If `True`, activates the environment for subsequent steps.                                              |
| `set_python_path`   | `bool`        | `False`      | If `True`, sets `PYTHONPATH` to the virtual environment.                                                |
| `inexact`           | `bool`        | `False`      | If `True`, tells `uv` not to remove dependencies that are present but not declared in the requirements. |

#### Example

```yaml
hooks:
  - id: python/setup-python
    version: ">=3.11,<3.12"
    uv: "0.4.0"
    requirements_file:
      - requirements.txt
    requirements: |
      requests==2.32.0
    activate_env: true
    inexact: true
```
multiversx-sdk-cli 11.3.1
MultiversX Smart Contracts Tools
Requires Python: >=3.10

# Description
Python Command Line Tools for interacting with Multivers<sup>X</sup>.

## Documentation
[docs.multiversx.com](https://docs.multiversx.com/sdk-and-tools/sdk-py/)

## CLI
[CLI](CLI.md)

## Distribution
[pipx](https://docs.multiversx.com/sdk-and-tools/sdk-py/installing-mxpy/) [(PyPi)](https://pypi.org/project/multiversx-sdk-cli/#history)

## Development setup

Clone this repository and cd into it:

```
git clone https://github.com/multiversx/mx-sdk-py-cli.git
cd mx-sdk-py-cli
```

### Virtual environment

Create a virtual environment and install the dependencies:

```
python3 -m venv ./venv
source ./venv/bin/activate
pip install -r ./requirements.txt --upgrade
```

Install development dependencies, as well:

```
pip install -r ./requirements-dev.txt --upgrade
```

Allow `pre-commit` to automatically run on `git commit`:
```
pre-commit install
```

Above, `requirements.txt` should mirror the **dependencies** section of `pyproject.toml`.

If using VSCode, restart it or follow these steps:
 - `Ctrl + Shift + P`
 - _Select Interpreter_
 - Choose `./venv/bin/python`.

### Using your local `mxpy`

If you want to test the modifications you locally made to `mxpy`, set `PYTHONPATH` with the path to your local repository path.

For example, if you cloned the repository at `~/mx-sdk-py-cli`, run:

```
export PYTHONPATH="~/mx-sdk-py-cli"
```

Then `mxpy` will use the code in your local repository.