You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I try to mirror tensorflow with python environments for both 3.11 and 3.12 then it won't grab tensorflow-io-gcs-filesystem which is required for python <3.12. From what I can gather the trouble is that there's no version of tensorflow-io-gcs-filesystem for 3.12 and so morgan gives up and decides not to get it. Not exactly sure why that's not fatal, but more to the point morgan should be handling the different environments somewhat more independently. Environment a needs package x, then get a version of package x that fulfills the requirement for environment a. Don't care if it doesn't work for environment b, you still need it for environment a. If you want to get fancy it ends up being a packing problem. I would suggest just doing the trivial "find a version that works for the environment I need it in" and don't worry about trying to reduce duplication.
The text was updated successfully, but these errors were encountered:
If I try to mirror
tensorflow
with python environments for both 3.11 and 3.12 then it won't grabtensorflow-io-gcs-filesystem
which is required for python <3.12. From what I can gather the trouble is that there's no version oftensorflow-io-gcs-filesystem
for 3.12 and so morgan gives up and decides not to get it. Not exactly sure why that's not fatal, but more to the point morgan should be handling the different environments somewhat more independently. Environment a needs package x, then get a version of package x that fulfills the requirement for environment a. Don't care if it doesn't work for environment b, you still need it for environment a. If you want to get fancy it ends up being a packing problem. I would suggest just doing the trivial "find a version that works for the environment I need it in" and don't worry about trying to reduce duplication.The text was updated successfully, but these errors were encountered: