Hello folks. PSA. The `py_editable_in_resolve` op...
# general
s
Hello folks. PSA. The
py_editable_in_resolve
option is a game-changer for IDE module discovery. It obviates setting the PYTHONPATH via a .env file (for first-party code), and fixes some ikky extension integration issues (For example, with pylint and VSCode). Not sure how much awareness there is of this superb feature when it comes specifically to VSCode/IDE integration, because none of the IDE helper docs mention this.
❤️ 5
p
Thank you! Adding a note about that feature to IDE docs is an excellent idea! Would you please file a pull request?
s
I am happy to do that, is there a guide to contributing to the pants website? I would appreciate an example PR, say.
p
The docs are in the pantsbuild repo: https://github.com/pantsbuild/pants/tree/main/docs/docs During release (iirc) they get built and deployed to the website via https://github.com/pantsbuild/pantsbuild.org So, make a PR against the
main
branch of
pantsbuild/pants
. A brief explanation of the process is available here: https://www.pantsbuild.org/stable/docs/contributions#documentation-fixes
s
Thank you! I will get to this over the weekend.
🚀 2
❤️ 2
🙏 1
https://github.com/pantsbuild/pants/pull/22026 Please let me know if this looks ok. Happy to go over as many iterations as possible until it does. Thanks in advance!
Is there a typical turnaround time for review of these PRs? I recognize this might be lower priority because it is just docs, but also think it could help a lot of folks.
p
Sorry. I took a glance, but I haven't had time to think through the implications of reorganizing the docs. Is there a more minimal change you can do?
👀 1
s
Addressed your comments @happy-kitchen-89482! Sorry for the delay.