xylar opened a new issue #22380:
URL: https://github.com/apache/airflow/issues/22380


   ### Apache Airflow Provider(s)
   
   ftp, openfaas, sqlite
   
   ### Versions of Apache Airflow Providers
   
   I am the maintainer of the Airflow Providers on conda-forge.  The providers 
I listed above are the first 3 I have looked at but I believe all are affected. 
 These are the new releases (as of yesterday) of all providers.
   
   ### Apache Airflow version
   
   2.2.4 (latest released)
   
   ### Operating System
   
   Linux (Azure CI)
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   This is on conda-forge Azure CI.
   
   ### What happened
   
   All providers I have looked at (and I suspect all providers) now have 
`gitpython` and `wheel` in their `install_requires`:
   
   From `apache-airflow-providers-ftp-2.1.1.tar.gz`:
   ```
   install_requires = 
        
        gitpython
        wheel
   ```
   
   I believe these requirements are incorrect (neither should be needed at 
install time) and this will make maintaining these packages on conda-forge an 
absolute nightmare!  (It's already a serious challenge because I get a PR to 
update each time each provider gets updated.)
   
   ### What you think should happen instead
   
   These install requirements should be removed.
   
   ### How to reproduce
   
   Open any of the newly released providers from pypi and look at `setup.cfg`.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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