sqlalchemy-postgres-point 0.2.1__tar.gz → 0.2.2__tar.gz

{sqlalchemy_postgres_point-0.2.1 → sqlalchemy_postgres_point-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: sqlalchemy-postgres-point
-Version: 0.2.1
+Version: 0.2.2
 Summary: Lightweight SQLAlchemy custom type for PostgreSQL POINT columns with tuple binding and an earth-distance comparator.
 Keywords: sqlalchemy,postgresql,point,geometry,geospatial,gis,database,types,earthdistance
 Author: Michael Bianco
@@ -46,7 +46,7 @@ from sqlalchemy_postgres_point import PointType
 
 
 class Base(DeclarativeBase):
-	pass
+    pass
 
 
 class Place(Base):
@@ -55,6 +55,7 @@ class Place(Base):
     # Store as (longitude, latitude)
     location = Column(PointType)
 
+
 # Example query using the custom comparator
 from sqlalchemy import select
 
@@ -80,14 +81,15 @@ Revises: your_previous_revision
 Create Date: 2025-01-XX XX:XX:XX.XXXXXX
 
 """
+
 from typing import Sequence, Union
 
 from alembic import op
 import sqlalchemy as sa
 
 # revision identifiers, used by Alembic.
-revision: str = 'your_revision_id'
-down_revision: Union[str, None] = 'your_previous_revision'
+revision: str = "your_revision_id"
+down_revision: Union[str, None] = "your_previous_revision"
 branch_labels: Union[str, Sequence[str], None] = None
 depends_on: Union[str, Sequence[str], None] = None
 
@@ -118,15 +120,16 @@ Values are loaded as a 2-tuple of floats `(lng, lat)` or `None` when NULL.
 
 ## Alembic Integration
 
-To ensure generated migration files include the correct `PointType` import, pass the provided `render_item` hook to `context.configure()` in your `alembic/env.py`:
+To ensure generated migration files include the correct `PointType` import, pass the provided `render_item` hook to `context.configure()` in your `alembic/env.py`. This must be added to **both** `run_migrations_online` and `run_migrations_offline`:
 
 ```python
-from sqlalchemy_postgres_point.alembic_integration import render_item
+from sqlalchemy_postgres_point.alembic_integration import (
+    render_item as render_point_item,
+)
 
-# in run_migrations_online and run_migrations_offline:
 context.configure(
     # ... other options ...
-    render_item=render_item,
+    render_item=render_point_item,
 )
 ```
 
@@ -134,17 +137,26 @@ Once wired up, `from sqlalchemy_postgres_point import PointType` will be automat
 
 ### Chaining `render_item`
 
-It's insane to me, but you have to chain multiple `render_item` instances you may have yourself.
+If you need to combine this with other packages that also provide a `render_item`, chain them:
 
 ```python
-from sqlalchemy_postgres_point.alembic_integration import render_item as render_point
+from sqlalchemy_postgres_point.alembic_integration import (
+    render_item as render_point_item,
+)
+
 
 def render_item(type_, obj, autogen_context):
     return (
-        render_point(type_, obj, autogen_context)
+        render_point_item(type_, obj, autogen_context)
         or other_package.render_item(type_, obj, autogen_context)
         or False
     )
+
+
+context.configure(
+    # ... other options ...
+    render_item=render_item,
+)
 ```
 
 Or you could use something like [`some_fn`](https://funcy.readthedocs.io/en/stable/funcs.html#some_fn) to make this even cleaner.

{sqlalchemy_postgres_point-0.2.1 → sqlalchemy_postgres_point-0.2.2}/README.md

@@ -34,7 +34,7 @@ from sqlalchemy_postgres_point import PointType
 
 
 class Base(DeclarativeBase):
-	pass
+    pass
 
 
 class Place(Base):
@@ -43,6 +43,7 @@ class Place(Base):
     # Store as (longitude, latitude)
     location = Column(PointType)
 
+
 # Example query using the custom comparator
 from sqlalchemy import select
 
@@ -68,14 +69,15 @@ Revises: your_previous_revision
 Create Date: 2025-01-XX XX:XX:XX.XXXXXX
 
 """
+
 from typing import Sequence, Union
 
 from alembic import op
 import sqlalchemy as sa
 
 # revision identifiers, used by Alembic.
-revision: str = 'your_revision_id'
-down_revision: Union[str, None] = 'your_previous_revision'
+revision: str = "your_revision_id"
+down_revision: Union[str, None] = "your_previous_revision"
 branch_labels: Union[str, Sequence[str], None] = None
 depends_on: Union[str, Sequence[str], None] = None
 
@@ -106,15 +108,16 @@ Values are loaded as a 2-tuple of floats `(lng, lat)` or `None` when NULL.
 
 ## Alembic Integration
 
-To ensure generated migration files include the correct `PointType` import, pass the provided `render_item` hook to `context.configure()` in your `alembic/env.py`:
+To ensure generated migration files include the correct `PointType` import, pass the provided `render_item` hook to `context.configure()` in your `alembic/env.py`. This must be added to **both** `run_migrations_online` and `run_migrations_offline`:
 
 ```python
-from sqlalchemy_postgres_point.alembic_integration import render_item
+from sqlalchemy_postgres_point.alembic_integration import (
+    render_item as render_point_item,
+)
 
-# in run_migrations_online and run_migrations_offline:
 context.configure(
     # ... other options ...
-    render_item=render_item,
+    render_item=render_point_item,
 )
 ```
 
@@ -122,17 +125,26 @@ Once wired up, `from sqlalchemy_postgres_point import PointType` will be automat
 
 ### Chaining `render_item`
 
-It's insane to me, but you have to chain multiple `render_item` instances you may have yourself.
+If you need to combine this with other packages that also provide a `render_item`, chain them:
 
 ```python
-from sqlalchemy_postgres_point.alembic_integration import render_item as render_point
+from sqlalchemy_postgres_point.alembic_integration import (
+    render_item as render_point_item,
+)
+
 
 def render_item(type_, obj, autogen_context):
     return (
-        render_point(type_, obj, autogen_context)
+        render_point_item(type_, obj, autogen_context)
         or other_package.render_item(type_, obj, autogen_context)
         or False
     )
+
+
+context.configure(
+    # ... other options ...
+    render_item=render_item,
+)
 ```
 
 Or you could use something like [`some_fn`](https://funcy.readthedocs.io/en/stable/funcs.html#some_fn) to make this even cleaner.

{sqlalchemy_postgres_point-0.2.1 → sqlalchemy_postgres_point-0.2.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "sqlalchemy-postgres-point"
-version = "0.2.1"
+version = "0.2.2"
 description = "Lightweight SQLAlchemy custom type for PostgreSQL POINT columns with tuple binding and an earth-distance comparator."
 keywords = [
     "sqlalchemy",
@@ -21,7 +21,7 @@ urls = { "Repository" = "https://github.com/iloveitaly/sqlalchemy-postgres-point
 
 
 [build-system]
-requires = ["uv_build>=0.11.0,<0.12"]
+requires = ["uv_build>=0.11.0,<0.13"]
 build-backend = "uv_build"
 
 [tool.uv.build-backend]

{sqlalchemy_postgres_point-0.2.1 → sqlalchemy_postgres_point-0.2.2}/sqlalchemy_postgres_point/point.py

@@ -11,7 +11,6 @@ References:
 
 import math
 import re
-from typing import Tuple
 
 from sqlalchemy.types import Float, UserDefinedType
 
@@ -23,7 +22,7 @@ class PointType(UserDefinedType):
         return "POINT"
 
     @staticmethod
-    def _validate_point(value: Tuple[float, float]) -> Tuple[float, float]:
+    def _validate_point(value: tuple[float, float]) -> tuple[float, float]:
         """Validate and normalize a (lng, lat) tuple.
 
         - Ensures it's a 2-length tuple/list