[QUESTION] Beartype version pinning (0.14.0 - 0.16.0) causing compatibility issues

[joaorrpinto]

What is your question or problem? Please describe.

The pathway library currently pins beartype to a narrow version range ("beartype >= 0.14.0, < 0.16.0"), which is causing compatibility issues across our organization's projects.

When pathway is installed as a dependency alongside other packages that require newer versions of beartype (or have looser version constraints), we encounter dependency conflicts that prevent successful environment resolution. This restrictive pinning is problematic because:

1. Broader ecosystem incompatibility: Other libraries in our stack may require or support newer beartype versions (0.16.0+), making it impossible to use pathway without creating isolated environments or relaxing constraints elsewhere.
2. Dependency hell: The tight constraint creates friction during dependency management and forces us to either exclude pathway or exclude other critical dependencies.
3. Upstream updates blocked: As beartype continues to evolve and improve, pathway users cannot benefit from newer versions without manually forking or maintaining custom dependency configurations.

Describe what you would like to happen

I would like to request that the pathway team:

1. Evaluate the beartype version constraint to understand why versions >= 0.16.0 are excluded
2. Test pathway compatibility with the latest stable versions of beartype (0.16.0 and above) to determine if the upper bound restriction is still necessary
3. Relax the version pinning to allow a wider range of beartype versions (e.g., "beartype >= 0.14.0" or "beartype >= 0.14.0, < 1.0.0") if compatibility is confirmed
4. Document any known compatibility issues if newer beartype versions introduce breaking changes that prevent relaxation of the constraint

This would significantly reduce dependency management friction for organizations using pathway alongside other modern Python packages.