Jarek Potiuk
Jarek Potiuk
We can even do not make it a requiremeent, but install it dynamically when someone uses `--debug` option BTW.
Or name it `--debug-pudb` as a flag.
> Sneak peak > > 2022-09-14.20-34-13.webm We already have DebugExecutor that does exactly that in the same way and a bit simpler (and is portable across IDEs) I think.. https://airflow.apache.org/docs/apache-airflow/stable/executor/debug.html?highlight=debug+executor...
> Oh yes. Still, see my previous point about breakpoint() then breakpoint is fine. but it will not give you a fully-fledged, intuitive debugger in the console wiht visual debugging...
> @potiuk could we make the debugger a separate discussion? I don't personally have a strong opinion one way or another, but it sounds like that might be something that...
> Prior art for debugger: https://docs.pytest.org/en/7.1.x/how-to/failures.html?highlight=pdbcls > > `--pdb` to drop in to a debugger shell on error, `--trace` to drop in to a shell at the start of a...
Ah I see you mentioned it too - yeah I think this is a good way of approaching it to mimic pytest behaviour :). Just with default being different than...
BTW. The fix for provider builds testing on constraints is already merged and those errors are irrelevant
> I have plans/ideas in my head on how to turn this in to a _true_ test only command -- one that leaves _no trace_ of the run in the...
> I have plans/ideas in my head on how to turn this in to a true test only command -- one that leaves no trace of the run in the...