chore(docker): use editable mode in docker images

[mistercrunch]

Trying to address the issue raise here: #34120 (comment)

From my analysis, it should address the issue (package installed twice in docker) by using a symlink.

The downsides are pretty minimal, with a micro os-level penalty on resolving symlinks (super minimal from my understanding), and some considerations around image size, where in editable mode we can't/couldn't strip .py files if we wanted.

This seems like a positive step.

Other alternatives would probably require 2 extra layers (an extra build layer for both dev and lean), and it's hard to keep the docker logic DRY and readable in that context. Personally I'm not willing to take this on now... With that approach, we wouldn't have /app/superset and would only have superset/ in .venv, could compile and strip .py to only keep .pyc if we wanted there.

Doing some research, it seems python is still very much lacking around managing lean packages/bundles of bytecode only, where wheels and packages in general tend to be raw .py, and it's tricky to only pacakge .pyc if/when desired.

---

Some benefits from the -e (editable mode). /app/superset in docker:

• easy to find, easy to alter (pros/cons), easy to alter/inject files in extra docker layers
• easily docker-mountable, mount /app/superset to your local repo and you're live-running/editing the image

[korbit-ai]

Based on your review schedule, I'll hold off on reviewing this PR until it's marked as ready for review. If you'd like me to take a look now, comment /korbit-review.

Your admin can change your review schedule in the Korbit Console

[korbit-ai]

I've completed my review and didn't find any issues.

Check out our docs on how you can make Korbit work best for you and your team.

Loving Korbit!? Share us on LinkedIn Reddit and X

[mistercrunch]

@dpgaspar what do you think of this one!?

[eschutho]

Looks fine for non-production use.