Alternative method to mark source roots in PyCharm/IntelliJ IDEA

[gopidesupavan]

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[gopidesupavan]

To save few clicks from manually select each directory 😄

We can update this file as we restructure so that it will be easy to fixup all in one go

[bugraoz93]

Looks good! Thanks for adding!

[potiuk]

Hmm. I thought about it, but there are two things:

• we need to make sure this one gets updated (pre-commit?)
• why don't we commit both modules.iml and corresponding airflow.iml and dev/breeze/breeze.iml directly to the repo?

They seem to be portable, with relative references - IntelliJ ultimate and Pycharm seem to have the same format and work similarly, I can't see why we should not be able remove those files from .gitignore and commit them.

[potiuk]

We could also commit equivalent configuration from vscode if it is portable and separate from all other vscode configuration.

[potiuk]

The only problem I see that in breeze we might want to have another venv:

    <orderEntry type="jdk" jdkName="Python 3.12 (breeze)" jdkType="Python SDK" />
    <orderEntry type="sourceFolder" forTests="false" />

(BTW. It's funny how you can see that IntelliJ is just twisted java environment... jdkName= "Python 3.12 (breeze)" 🤣

[potiuk]

BTW. I am not super strong on the committing, copying the files will mostly work as well, and that "jdk" is potentially blocking, but might be worth seeing if that will work :).

It woudl be awesome if contributor just opens the airflow folder as project in PyCharm/IntelliJ and has everything set-up.

[gopidesupavan]

BTW. I am not super strong on the committing, copying the files will mostly work as well, and that "jdk" is potentially blocking, but might be worth seeing if that will work :).

It woudl be awesome if contributor just opens the airflow folder as project in PyCharm/IntelliJ and has everything set-up.

For JdkName it actually auto populated when i created virtual environment, so when we change interpreter paths in Pycharm settings then that will update the airflow.iml file. i have tested changing multiple paths in pycharm interpreter its updating the airflow.impl file

ah not sure how to setup when airflow folder opens :)

[gopidesupavan]

I have another idea, can add python script, it generates airflow.iml, module.xml files and updates automatically something like this cli.

python setup_ide.py --venv_name {}

We can update this script whenever changes happens :) ?

So users has to run first time and when any new changes happens.

[potiuk]

I have another idea, can add python script, it generates airflow.iml, module.xml files and updates automatically something like this cli.

That seems like a nice middle ground

[potiuk]

❤️

[potiuk]

Constraint/static check failure is setuptools mayhem - being fixed in #48210