semvec/pypi-packages huggingface dataset:
gdal-utils 3.12.2.0
gdal-utils: An extension library for GDAL - Geospatial Data Abstraction Library
License: MIT
Requires Python: >=3.6.0

gdal-utils
=============

This gdal-utils Python package is a sub-set of the GDAL Osgeo Python package.

If you've installed the GDAL package you have these utils. However you
may wish to get a newer version of the utilities without changing GDAL,
that's what this package is for.

For using and developing the utils please refer to the osgeo documentation
and to the `GDAL API Tutorial`_.

We don't systematically test the utils against a different versions of gdal.
Versioning of GDAL and gdal-utils are independent from each other, today's
gdal-utils v3.3 works with GDAL v3.4 but it might not with v3.2. We
recommend upgrading to the latest versions of each as general practice. See
'Packaging' below for how to test compatibility.


Dependencies
------------

 * gdal (the osgeo package)
 * numpy (1.0.0 or greater) and header files (numpy-devel) (not explicitly
   required, but many examples and utilities will not work without it)


Installation
------------

gdal-utils can be installed from pypi.org::

  $ python -m pip install gdal-utils

After install the utilities are in ``PYTHYONHOME\Scripts`` and can be
invoked like regular programs, ``gdal_edit`` instead of ``gdal_edit.py`` or
``python path/to/gdal_edit.py`` for example.


Packaging
---------

Starting March 2022 installing gdal-utils with pip will use Setuptools'
_console_scripts_, which turn the scripts into native platform
executables that call the script using the appropriate platform interpreter.
This means you no longer need to something similar as a post-install step.
If this causes problems with your distribution please file an issue on
Github.

Recipe for testing gdal-utils compatibility against your installed GDAL
binaries::

    # Get installed GDAL version
    export _GDALVER=`gdal-config --version``

    # verify python osgeo is present
    python -c "from osgeo import gdal;print(f'Python Osgeo version: {gdal.__version__}')"

    git clone https://github.com/OSGeo/gdal.git --depth=50
    git remote set-branches origin "*"
    git fetch -v --depth=50

    # Install current version of gdal-utils
    cd swig/python/gdal-utils
    pip install .
    # OR, to use published PyPi.org version:
    # pip install gdal-utils

    # set source code tree to match binary gdal version
    git checkout v$_GDALVER

    cd gdal/autotest
    python install -r requirements.txt
    pytest ./pyscripts


Coding best practices
---------------------

Use existing scripts for style guidelines, newer ones are generally
more pythonic than old ones.

Passes _flake8_ lint test.

When called without arguments script should return a message prefixed
'Usage: ` and use return code ``2``.::

    » gdal_edit
    Usage: gdal_edit [--help-general] [-ro] [-a_srs <srs_def>]
        ...
        [-unsetmd] [-oo <NAME>=<VALUE>]... [-mo <META-TAG>=<VALUE>]... <datasetname>

    Edit in place various information of an existing GDAL dataset.


.. _GDAL API Tutorial: https://gdal.org/tutorials/
.. _GDAL: http://www.gdal.org
ldraney-linkedin-mcp 0.1.1
MCP server wrapping the LinkedIn Python SDK (v202510)
License: MIT
Requires Python: >=3.10

# linkedin-mcp

MCP server for the LinkedIn API v202510 — create posts, upload media, manage engagement, and schedule content.

## Installation

### Claude Desktop (one-click)

Download the `.mcpb` extension from the [latest release](https://github.com/ldraney/linkedin-mcp/releases/latest/download/ldraney-linkedin-mcp.mcpb) and double-click to install.

### Manual

```bash
uvx ldraney-linkedin-mcp
```

Or add to your Claude Code config:

```json
{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": ["ldraney-linkedin-mcp"],
      "env": {
        "LINKEDIN_ACCESS_TOKEN": "your_token",
        "LINKEDIN_PERSON_ID": "your_person_id"
      }
    }
  }
}
```

## Authentication

The server supports multiple authentication methods:

1. **Environment variables**: Set `LINKEDIN_ACCESS_TOKEN` and `LINKEDIN_PERSON_ID`
2. **OS Keychain**: Use the `save_credentials` tool to store credentials securely
3. **OAuth flow**: Use `get_auth_url` to start the OAuth flow

## Tools (21)

### Auth (4)
- `get_auth_url` — Get LinkedIn OAuth authorization URL
- `exchange_code` — Exchange OAuth code for access token
- `save_credentials` — Save credentials to OS keychain
- `refresh_token` — Refresh an expired token

### Posts (4)
- `create_post` — Create a text post
- `get_my_posts` — List your recent posts
- `delete_post` — Delete a post
- `update_post` — Update a post

### Media (6)
- `create_post_with_link` — Post with article preview
- `create_post_with_image` — Post with image
- `create_post_with_document` — Post with PDF/DOC/PPT
- `create_post_with_video` — Post with video
- `create_poll` — Create a poll
- `create_post_with_multi_images` — Post with multiple images

### Engagement (2)
- `add_comment` — Comment on a post
- `add_reaction` — React to a post

### Users (1)
- `get_user_info` — Get your profile info

### Scheduler (4)
- `schedule_post` — Schedule a future post
- `list_scheduled_posts` — List scheduled posts
- `cancel_scheduled_post` — Cancel a scheduled post
- `get_scheduled_post` — Get scheduled post details

## License

MIT
mkdocstrings-github 0.7.2
A GitHub Action handler for mkdocstrings
License: MIT
Requires Python: <3.15,>=3.10

<!-- --8<-- [start:header] -->

<h1 align="center">mkdocstrings-github</h1>

<p align="center">A GitHub Actions handler for <a href="https://github.com/mkdocstrings/mkdocstrings"><i>mkdocstrings</i></a>.</p>

<!-- --8<-- [end:header] -->

<p align="center"><img width=300px src="docs/img/logo.png"></p>

[![Qualify](https://github.com/watermarkhu/mkdocstrings-github/actions/workflows/qualify.yaml/badge.svg?branch=main)](https://github.com/watermarkhu/mkdocstrings-github/actions/workflows/qualify.yaml)
[![documentation](https://img.shields.io/badge/docs-mkdocs-708FCC.svg?style=flat)](https://watermarkhu.nl/mkdocstrings-github)
[![pypi version](https://img.shields.io/pypi/v/mkdocstrings-github.svg)](https://pypi.org/project/mkdocstrings-github/)
[![codecov](https://codecov.io/github/watermarkhu/mkdocstrings-github/graph/badge.svg?token=M6XW8UeURE)](https://codecov.io/github/watermarkhu/mkdocstrings-github)



For example, the following page is generated from [actions/checkout](https://github.com/actions/checkout):

<picture>
  <source media="(prefers-color-scheme: dark)" srcset="docs/img/example_dark.png">
  <source media="(prefers-color-scheme: light)" srcset="docs/img/example_light.png">
  <img alt="Fallback image description" src="docs/img/example_light.png">
</picture>


<!-- --8<-- [start:install] -->
You can install the GitHub handler by specifying it as a dependency:

```toml title="pyproject.toml"
# PEP 621 dependencies declaration
# adapt to your dependencies manager
[project]
dependencies = [
    "mkdocstrings-github",
]
```

after which the generated documentation can be inserted in the markdown page with:

```md
::: <path-to-action-or-workflow>
    handler: github
```

<!-- --8<-- [end:install] -->

<!-- --8<-- [start:footer] -->

## Features

- 📝 **Automatic Example Signature**: Displays an example call signature alongside the description. The version shown can be the latest release, latest major, current reference, or any custom string.
- ✨ **Enhanced Markdown Descriptions**: All description elements are parsed using a markdown parser, enabling comprehensive formatting and rich documentation capabilities.
- 🧩 **Individual Parameter Hyperlinks**: Each action or workflow parameter—including inputs, outputs, and secrets—receives a unique HTML id, facilitating direct linking to specific parameter documentation.
- 🔒 **Automated Permission Aggregation**: For reusable workflows, if permissions are specified at the job level rather than the workflow level, the required final permissions are automatically determined and displayed in the signature.
- 🔗 **Parameter cross-linking**: Link to other parameters of the action or workflow via a simple Markdown syntax.
- 🧑‍🤝‍🧑 **Parameter grouping**: Organize related inputs, outputs, and secrets into visual groups using inline YAML comments for clearer documentation structure.

<!-- --8<-- [end:footer] -->