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
Both HTTP and BSON exist, but the fuzzy match recommendations don't suggest the cased-counterparts.
Depending on your philosophy here, I think it's worthwhile to either:
Install with a warning about the cased version of the package is being installed and will need to be referenced as such.
OR prevent case sensitivity on packages.
OR make fuzzy matching case-insensitive, so packages like HTTP and BSON, will show up when a user tries to install http and json respectively.
I'm making this a feature request because:
It's a risk if you're allowing both http and HTTP to co-exist.
A little annoying to start projects with many packages that have their own unique casing.
Confusing for beginners like myself seeing that "http package doesn't exist". This is because both pip and gem are case-insensitive when downloading packages.
The text was updated successfully, but these errors were encountered:
Both HTTP and BSON exist, but the fuzzy match recommendations don't suggest the cased-counterparts.
Depending on your philosophy here, I think it's worthwhile to either:
I'm making this a feature request because:
http
andHTTP
to co-exist.The text was updated successfully, but these errors were encountered: