python: bug fix when version = none - #14
Conversation
|
Why would we want to pass |
|
Even it's not super clear to me as in why we would like to use Maybe to take advantage of other steps 😕 |
|
Also, there are many other images which calls different features with |
Yeah, it doesn't install any version |
I imagine this was because we were preferring the oryx-provided versions? I don't see why we'd ever want to pass |
|
It's not just the joshspicer do you recommend removing such feature calls? I'll check for their use before removing. |
|
Do you know why they would set to We are in charge of what we keep/don't keep based on what makes sense now :) |
|
Even when
|
|
Gotcha - can you also document 'none' in the relevant feature.json's too then: eg: https://github.com/devcontainers/features/blob/main/src/node/feature.json#L7 |
|
|
joshspicer I have few ideas like replacing Let me know which one sounds better, can't really think of a single word for all of them. Else, we can continue using none 😕 |

When python feature is called with version:none then following error occurs while building the image