-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better shim libraries #4167
Comments
Sorry, I don't understand this issue, can you give an example how you want things to be? |
Sorry for not responding earlier. Also I realized I misunderstood The goal is say I have a library foo, with releases versions |
@phadej Ah, I just discovered
|
I.e. you want to have
IMHO it's not worth it. There are quite a lot of difficulties (with shadowing modules, types, you cannot shim classes/instances anyway). I'd just create a compat library (in either direction). |
Also, And indeed, And e.g. |
I'd love to ditch names like
transformers-compat
and instead allow libraries to declare private dependencies on new versions of themselves.The harder part of this is private dependencies of course but #4104 also helps in that by making version bounds that exclude internal components and error today. That way tomorrow we are free to assign brand new meaning to them (i.e. actually depend on a newer version of me, please) tomorrow without breaking any existing packages.
The text was updated successfully, but these errors were encountered: