[GitHub] [airflow] bensta edited a comment on issue #18932: Conflicts with airflow constraints for airflow 2.2.0 python 3.7

[GitBox <gi...@apache.org>]

bensta edited a comment on issue #18932:
URL: https://github.com/apache/airflow/issues/18932#issuecomment-966992155


   Yep, your explanation does make sense. And indeed, if I use the extras individually as you suggested, the install does indeed work. Thanks for the clarification!
   
   I have two thoughts from a user perspective: 
   a) The documentation does imply, that the [all] and [all_dbs] bundle extras are indeed for production use, since the [all] bundle is described as "all _user _facing__  features. Together with the presence of a devel_all package does indeed imply that this is meant to be used by the end user. 
   
   b) Having  bundles of extras is very convenient for end users, given the large number of extras there are. So if there would be a way to provide it to the end user without running into conflicts would be highly desirable. 
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org