Skip to content

Bump PyMEOS to 1.4 in per-folder requirements#4

Draft
estebanzimanyi wants to merge 2 commits into
mainfrom
bump/meos-1.4
Draft

Bump PyMEOS to 1.4 in per-folder requirements#4
estebanzimanyi wants to merge 2 commits into
mainfrom
bump/meos-1.4

Conversation

@estebanzimanyi
Copy link
Copy Markdown
Member

Pins both per-folder requirements.txt files to pymeos>=1.4.0a1 to track the MEOS 1.4 surface. Examples use the high-level PyMEOS Python API only (no direct pymeos_cffi imports), so no code changes accompany the version bump. Draft until PyMEOS 1.4 lands.

Each example folder now ships a requirements.txt that pins pymeos at
or above the 1.3.0a1 alpha so users installing fresh do not pull
1.2.x and hit the unified spatial nomenclature mismatch.  The notebook
imports themselves (TGeogPointInst, TFloatInst, TGeomPointSeq,
TGeomPointInst, STBox, pymeos_initialize) still resolve unchanged
against PyMEOS 1.3 because the class layer was kept stable across the
MEOS C-level rename.
Bumps the dependency floor to pymeos>=1.4.0a1 to track the MEOS 1.4
surface. The examples use only the high-level PyMEOS Python API
(no direct pymeos_cffi imports), so no code changes are needed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant