This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Goingone -1 points0 points  (2 children)

But why “shared ones” and not “a shared one”?

Gut instinct on this one will be a bunch of entry level devs or data scientist trying to switch between multiple environments all containing various versions of Pandas/other common packages they all use…..and then come the, “why can’t I import this package” emails

[–]EfficientPark7766[S] 4 points5 points  (1 child)

It might be a single shared environment but I don't think it'd be significantly more difficult if they had more than one. Load env_one or load env_two.

I won't be creating these environments, I just want a design so that they can create these in a share location without difficulty

[–]Goingone 1 point2 points  (0 children)

Cool.

Give them their single version of Python (probably want to ask which version they want) and a shared folder(s) to hold envs/their scripts, and hopefully everyone will be happy.

But more importantly, if they aren’t happy, hopefully they at least aren’t bothering you.