[GitHub] [airflow] ashb commented on issue #8674: Fix problems with, and test agsinst, Python 3.8

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

ashb commented on issue #8674:
URL: https://github.com/apache/airflow/issues/8674#issuecomment-628719122


   > For development we also have Breeze environment which I think long term might become the default
   
   Let's separate out development Airflow itself and developing DAGs etc.
   
   For the former: maybe, but it should never be a requirement on contributors. (And as long as I'm working on Airflow my default's gonna be direct development, not using Docker :grinning:. I am on Linux now though.)
   
   For the latter: being able to use OSX (and yes, eventually Windows) as a user writing dags and running a development Airflow instance without Docker is a critical goal of on-boarding for new users because:
   
   1. Running multiple docker containers at once can start to seriously impact performance on less-powerful laptops.
   2. Docker is still quite confusing if you aren't familiar with it, especially when it comes to rebuilding and volume mounts etc.
   
   We can solve some of that, but I am set on still supporting running directly for users on OSX.
   
   > I believe this is a very small subset of tests.
   
   Yes, it is. The only real issue in the spawn-vs-fork comes when we use the `conf_vars` decorator in the test -- where the temporarily changed config values doesn't affect any spawned subprocess. Given the fix for that is quite easy (we can set the `AIRFLOW__*` environment variable in the conf_var decorator too.) that I wouldn't even say we need a special decorator for it.
   
   And the config mocking issue aside, I think being able to test on OSX/with spawn is useful to getting us _towards_ testing it runs on OSX/Windows.
   
   


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

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