Repository navigation
Conversation
…map, control filename, keyword typo - Remove pgsql_http from Makefile EXTENSIONS defaults and CI matrix so http.so is not grafted into the pgembed wheel (separate pgembed-http wheel only, built via explicit make EXTENSIONS=pgsql_http) - Revert unrelated pyproject version bump 0.2.1 -> 0.2.0 - postgres_server.create_extension: map http -> pgsql_http - pgembed_pgsql_http share path: look up http.control via EXTENSION_CREATE - Fix pgsl-http keyword typo; add test_pgsql_http regression test
- Install/available-extensions/platform/build sections updated - Notes libcurl build-time requirement
Contributor
Author
|
@jeffrey82221 please add some test coverage in another PR. |
Closed
…ing workflow - Restructure shim as nested package so setuptools finds it; fixed packages.find (was where=[src], matched nothing), real README for the readme field, package-data for the staged http.so/control/sql - setup.py forces platform wheel tags (prebuilt .so must never ship as py3-none-any) - publish-pgembed-http.yml mirrors build-and-test (same runners, same plain make so PG major tracks base; only EXTENSIONS differs), restores the base postgres cache, stages binaries via pg_config paths, smoke-tests CREATE EXTENSION http, publishes pgembed-http-v* tags via trusted publishing
The nested package dir broke 'pip install -e .' from the repo root: without a top-level __init__.py the shim imported as an empty namespace package and import pgembed crashed in _detect_extensions. Repo keeps the flat layout (same as the other shims); the publish workflow assembles the nested build-pgembed-http/ tree instead.
jeffrey82221
approved these changes
Oct 6, 2026
Contributor
Author
|
Ignoring the CI failures on publish because the first publish on pypi has to be manual. |
Contributor
|
I cannot install the package pgembed and pgembed-http properly. python3.12 -m venv .venv
source .venv/bin/activate
pip install -e . pgembed
cd src/pgembed_pgsql_http
pip install -e . pgembed-httpAfter the installation, pgembed.has_extension("pgsql_http") still == False. import pgembed
pgembed.has_extension("pgsql_http")
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@jeffrey82221 work cherry-picked from #19
Adds
pgsql-http(v1.7.2, https://github.com/pramsey/pgsql-http) as anoptional separate extension package, following the
pgembed-pgvectorsplit-wheel pattern. The base
pgembedwheel is unchanged in size.pgembed-http(src/pgembed_pgsql_http/) — import namepgembed_pgsql_http, registry keypgsql_http, SQL namehttp.pgembedcore only registers/discover it (EXTENSION_PACKAGES/SO_FILES/NAMES/ create-name); binaries ship in the split wheel.make EXTENSIONS=pgsql_http(same pattern aspg_search); not in the defaultEXTENSIONSset or CI wheel matrix.Usage: