semvec/pypi-packages huggingface dataset:
core-website-app 2.19.0
Basic web functionalities for the curator core project

================
Core Website App
================

Basic web functionalities for the curator core project.

Quickstart
==========

1. Add "core_website_app" to your INSTALLED_APPS setting
--------------------------------------------------------

.. code:: python

    INSTALLED_APPS = [
        ...
        'core_website_app',
    ]

2. Include the core_website_app URLconf in your project urls.py
---------------------------------------------------------------

.. code:: python

    url(r'^website/', include('core_website_app.urls')),


3. Install and configure Captcha
--------------------------------

See instructions: https://django-simple-captcha.readthedocs.io/en/latest/usage.html#installation
core-user-registration-app 2.19.0
User registration module for the core project

core_user_registration_app
==========================

User registration module for the core project.

Quick start
===========

1. Add "core_user_registration_app" to your INSTALLED_APPS setting
------------------------------------------------------------------

.. code:: python

    INSTALLED_APPS = [
      ...
      'core_user_registration_app',
    ]

2. Include the core_user_registration_app URLconf in your project urls.py
-------------------------------------------------------------------------

.. code:: python

    re_path(r'^', include('core_user_registration_app.urls')),
docker-hosts 0.1.1
Automatically manage Docker container hostnames in /etc/hosts for local development and CI
Requires Python: >=3.11
Keywords: docker, docker-compose, hosts, localhost, development, devops, containers, networking, automation

# Automatic Docker Hosts Management

Automatically manage Docker container hostnames in your `/etc/hosts` file.

I built this to solve a specific problem: using Docker Compose for local development services (postgres, redis, etc.) and sharing the same compose file with CI. I wanted `DATABASE_URL=postgres://postgres.localhost/mydb` to work both locally and in CI without maintaining separate configs. This tool creates stable domains for Docker Compose services that work everywhere - no manual `/etc/hosts` edits, no environment-specific configuration. Originally extracted from my [python-starter-template](https://github.com/iloveitaly/python-starter-template).

## Installation

Using uv:

```bash
uv tool install docker-hosts
```

Using pip:

```bash
pip install docker-hosts
```

## Usage

Update `/etc/hosts` with all running containers:

```bash
sudo docker-hosts
```

Preview what would be written without making changes:

```bash
docker-hosts --dry-run
```

Use a custom TLD (defaults to `.localhost`):

```bash
sudo docker-hosts --tld dev
```

Specify a custom hosts file path:

```bash
docker-hosts /tmp/hosts --dry-run
```

The tool requires sudo when writing to `/etc/hosts`, but you can test with `--dry-run` first to see what it would do.

### Windows / WSL

You may encounter issues if using Docker Desktop. Running Docker directly on WSL works properly.

## Features

- Network-aware - picks up all network aliases from Docker networks, not just the default bridge network. If your container is attached to multiple networks, all IPs and aliases get added.
- Safe writes - uses atomic file writes (write to temp, then rename) to avoid corrupting your hosts file. Your existing entries are preserved - the tool only manages the section between `### Start Docker Domains ###` and `### End Docker Domains ###` markers.
- Structured logging - built with structlog for clean, parseable logs. Set `LOG_LEVEL=DEBUG` to see what's happening under the hood.
- Dry-run mode - test what would be written before committing to changes. Great for understanding what the tool does or debugging issues.

## Development

### Running Tests

Tests require Docker to be running with the postgres and redis containers from `docker-compose.yml`:

```bash
docker compose up -d
pytest -v
```

Run only unit tests (no Docker required):

```bash
pytest -v -m unit
```

Run only integration tests:

```bash
pytest -v -m integration
```

The test suite includes:
- Integration tests that verify container detection using real Docker containers
- Unit tests for data extraction and file operations
- CLI tests using temporary hosts files in `tmp/hosts`

# [MIT License](LICENSE.md)
core-semantic-search-app 1.0.0
Semantic Search utils for the curator core project

========================
Core Semantic Search App
========================

Semantic search for the curator core project.

Quick start
===========

1. Add "core_semantic_search_app" to your INSTALLED_APPS setting
----------------------------------------------------------------

.. code:: python

    INSTALLED_APPS = [
      ...
      'core_semantic_search_app',
    ]


2. Include the core_semantic_search_app URLconf in your project urls.py
-----------------------------------------------------------------------

.. code:: python

    re_path(r'^semantic-search/', include('core_semantic_search_app.urls')),
core-parser-app 2.19.0
XSD parser tools for the curator core project

===============
Core Parser App
===============

XSD parser, renderers and modules for the curator core project.

Quick start
===========

1. Add "core_parser_app" to your INSTALLED_APPS setting
-------------------------------------------------------

.. code:: python

    INSTALLED_APPS = [
        ...
        "core_parser_app",
        "core_parser_app.tools.modules", 
        "core_parser_app.tools.parser", 
    ]

2. Include the core_parser_app URLconf in your project urls.py
--------------------------------------------------------------

.. code:: python

    url(r'^parser/', include("core_parser_app.urls")),


Migration to the Bootstrap modal
================================
Breaking changes during the migration from the jQuery UI modal to the Bootstrap modal for the module :

- The JavaScript global variables **openModule**, **openPopUp** and **initialState** from the popup.js file have been deleted.
- The JavaScript variable **openModule** has been renamed to **moduleElement**.
- The modal management has been changed. JQuery UI reused the same DOM element for all modal loaded in the page. Bootstrap use a unique DOM element for each modal. Consequently the main modal container will have the following unique ID : **modal-{{module_id}}**.
- The save callback uses the new variable **openModule** to get the unique DOM container and get the value to save.
- The Django form id must be changed be because it is not unique and can create conflict if the page includes a module more than one time (example with the BLOBHostForm):

.. code:: python

    form = BLOBHostForm()
    form.fields["file"].widget.attrs.update(
        {"id": "file-input-%s" % str(module_id)}
    )