semvec/pypi-packages huggingface dataset:
django-project-initializer 1.0.4
The Django Project Initializer is a helper Python script that initializes a Modified Django project with mysql and python-stubs out-of-the-box.
Requires Python: >=3.12

# Django Project Initializer

**Author:** AdrianJames27

## Overview

The Django Project Initializer is a Python script that automates the setup of a new Django project. It performs the following tasks:

1. **Prompts** the user for a project name.
2. **Clones** a base Modified Django template repository from [GitHub](https://github.com/AdrianJames27/django_template).
3. **Removes** the `.git` directory from the cloned repository to eliminate version control history.
4. **Renames** the project directory to the specified project name.

## Requirements

- **Python 3.12**: Ensure Python is installed on your system.

## Error Handling
- The script includes basic error handling for common interruptions:
* KeyboardInterrupt: Handles manual interruption (e.g., pressing Ctrl+C).
* EOFError: Handles unexpected end of input.
* General Exceptions: Catches other unforeseen errors and provides an error message.

## Install Script (pip)
```bash
pip install django_project_initializer
```

## Create a Django Project
```bash
django-init
```

## License
- This project is licensed under the GPL-3.0 License - see the [LICENSE](https://github.com/AdrianJames27/django_project_initializer?tab=GPL-3.0-1-ov-file) file for details.
keyrings.gl-artifactregistry-auth 1.1.2
Keyring backend for Google Auth tokens for GDPLabs
Requires Python: >=3.6

# GDPLabs Artifact Registry Python Tools

This repository is a fork of [keyrings.google-artifactregistry-auth](https://pypi.python.org/pypi/keyrings.google-artifactregistry-auth) with modifications to support GDPLabs domains.

## Changes from Original

This fork extends the original package to support additional domains:
- `.obrol.id`
- `.gdplabs.id`

## Overview

This package provides a [keyring](https://pypi.python.org/pypi/keyring) backend implementation for interacting with Python repositories hosted on Artifact Registry, including GDPLabs domains.

## Authentication

The backend automatically searches for credentials from the environment and authenticates to Artifact Registry. It looks for credentials in the following order:

1. [Google Application Default Credentials](https://developers.google.com/accounts/docs/application-default-credentials)
2. From the `gcloud` SDK
3. If neither exists, an error occurs
chercher-plugin-rss 0.1.3
Chercher plugin that adds support for RSS feeds.
Requires Python: >=3.13

# chercher-plugin-rss

Chercher plugin that adds support for RSS feeds.

## Installation

```bash
uv tool install --with chercher-plugin-rss chercher
```

## Settings

> [!NOTE]
> If you plugin needs additional settings, add the instructions here.

## Development

> [!NOTE]
> TODO
mcp-demo 0.1.0
A MCP server project
Requires Python: >=3.12

# mcp-demo MCP server

A MCP server project

## Components

### Resources

The server implements a simple note storage system with:
- Custom note:// URI scheme for accessing individual notes
- Each note resource has a name, description and text/plain mimetype

### Prompts

The server provides a single prompt:
- summarize-notes: Creates summaries of all stored notes
  - Optional "style" argument to control detail level (brief/detailed)
  - Generates prompt combining all current notes with style preference

### Tools

The server implements one tool:
- add-note: Adds a new note to the server
  - Takes "name" and "content" as required string arguments
  - Updates server state and notifies clients of resource changes

## Configuration

[TODO: Add configuration details specific to your implementation]

## Quickstart

### Install

#### Claude Desktop

On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

<details>
  <summary>Development/Unpublished Servers Configuration</summary>
  ```
  "mcpServers": {
    "mcp-demo": {
      "command": "uv",
      "args": [
        "--directory",
        "/Users/haifwu/LLM/mcp-demo",
        "run",
        "mcp-demo"
      ]
    }
  }
  ```
</details>

<details>
  <summary>Published Servers Configuration</summary>
  ```
  "mcpServers": {
    "mcp-demo": {
      "command": "uvx",
      "args": [
        "mcp-demo"
      ]
    }
  }
  ```
</details>

## Development

### Building and Publishing

To prepare the package for distribution:

1. Sync dependencies and update lockfile:
```bash
uv sync
```

2. Build package distributions:
```bash
uv build
```

This will create source and wheel distributions in the `dist/` directory.

3. Publish to PyPI:
```bash
uv publish
```

Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token: `--token` or `UV_PUBLISH_TOKEN`
- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`

### Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging
experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).


You can launch the MCP Inspector via [`npm`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:

```bash
npx @modelcontextprotocol/inspector uv --directory /Users/haifwu/LLM/mcp-demo run mcp-demo
```


Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.