Re: [PR] Set minimum dependencies for apache-beam deps on Py 3.12+3.13 [airflow]

2025-01-31 Thread via GitHub


ashb merged PR #46321:
URL: https://github.com/apache/airflow/pull/46321


-- 
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]



Re: [PR] Set minimum dependencies for apache-beam deps on Py 3.12+3.13 [airflow]

2025-01-31 Thread via GitHub


potiuk commented on PR #46321:
URL: https://github.com/apache/airflow/pull/46321#issuecomment-2627785121

   So yeah - we should limit `apache.beam` not `grpc.io` in this case.


-- 
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]



Re: [PR] Set minimum dependencies for apache-beam deps on Py 3.12+3.13 [airflow]

2025-01-31 Thread via GitHub


potiuk commented on PR #46321:
URL: https://github.com/apache/airflow/pull/46321#issuecomment-2627784128

   Ah. This is because apache-beam 2.55.0 has grpcio.tools as "build 
requirements" not "requirements". In a modern build packaging - when a frontend 
is building package (because it does not have corresponding binary wheel) it 
will perform the build of that package from .sdist in "isolated build 
environment" -> where it downloads and sets up  temporary venv with the 
dependencies specified in the "build requirements" of that package. 
   
   From the error looks like apache-beam 2.55.0 has grpcio-tools 1.53.0 set as 
their `build requirements`. 


-- 
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]



Re: [PR] Set minimum dependencies for apache-beam deps on Py 3.12+3.13 [airflow]

2025-01-31 Thread via GitHub


ashb commented on PR #46321:
URL: https://github.com/apache/airflow/pull/46321#issuecomment-2627772384

   I'm going to set the min version of apache-beam itself instead.


-- 
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]



Re: [PR] Set minimum dependencies for apache-beam deps on Py 3.12+3.13 [airflow]

2025-01-31 Thread via GitHub


ashb commented on PR #46321:
URL: https://github.com/apache/airflow/pull/46321#issuecomment-2627766307

   Odd, that didn't seem to work:
   
   ```
 + uv pip install --python /usr/local/bin/python --resolution lowest-direct 
--upgrade --editable '.[apache-beam]' --editable ./task_sdk
 Using Python 3.12.8 environment at: /usr/local
 Resolved 179 packages in 4.73s
   × Failed to download and build `apache-beam==2.55.0`
   ├─▶ Failed to install requirements from `build-system.requires`
   ├─▶ Failed to build `grpcio-tools==1.53.0`
   ```


-- 
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]



Re: [PR] Set minimum dependencies for apache-beam deps on Py 3.12+3.13 [airflow]

2025-01-31 Thread via GitHub


potiuk commented on PR #46321:
URL: https://github.com/apache/airflow/pull/46321#issuecomment-2627712082

   Cool !


-- 
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]