Sanket-Shelar opened a new pull request, #1047:
URL: https://github.com/apache/ranger/pull/1047

   …port only (#1034)
   
   ## What changes were proposed in this pull request?
   
   Prepare apache-ranger 0.0.13 on PyPI with Python 3.13+ only support.
   
   Bump version to 0.0.13; set python_requires='>=3.13' and update classifiers.
   Refresh dependencies: requests>=2.34.2, strenum>=0.4.15 (avoids transitive 
chardet; [RANGER-3335](https://issues.apache.org/jira/browse/RANGER-3335)).
   Use SPDX Apache-2.0 license metadata in setup.py.
   Rewrite PyPI README: requirements, install, supported clients, quickstarts 
(Admin, UserMgmt, KMS, GDS, PDP), plus an Examples and Code References section 
that points to runnable sample scripts, client source files, and unit tests 
(replacing earlier inline usage blocks), auth notes, troubleshooting, 0.0.13 
highlights.
   Expand unit tests: split into TestRangerClient, TestGDSClient, and 
TestPDPClient; add GDS/PDP model coercion and API wiring coverage.
   Remove duplicate legacy packaging scripts (intg/src/main/python/setup.py is 
the single entry point):
   intg/scripts/setup.py
   ranger-examples/sample-client/scripts/setup.py, run-pyclient.sh
   Add .cursor/rules/ranger-python.mdc for Python client and test conventions.
   Breaking change: installs require Python 3.13+ (0.0.12 supported older 
versions).
   
   
   ## How was this patch tested?
   
    PYTHONPATH=src/main/python python -B src/test/python/test_ranger_client.py 
(16 tests)
    RangerClient and RangerGdsClient from sample_client.py, 
sample_gds_client.py exercised against a live Ranger Admin server
    mvn -pl intg test
    python -m build + twine check dist/* from intg/src/main/python
    Wheel install in clean venv; verify requests>=2.34.2, no chardet
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to