Hi, On Tue, Jul 20, 2021 at 3:33 PM Riadh <rfezzani@gmail.com> wrote:
Le 20/07/2021 à 15:10, Matthew Brett a écrit :
On Tue, Jul 20, 2021 at 1:33 PM Gregory Lee <grlee77@gmail.com> wrote:
That does seem like a very reasonable compromise, where the only real expense is the slightly kludgy name.
And it means that those of us depending on skimage can just do:
try: import skimage except ImportError: import skimage2.skimage as skimage
I am sorry, but this looks like a Hinsen rule break... But if such thing is acceptable, I am more incline to Tensorflow's strategy:
Could you explain more? From what I understood, `skimage` in these two imports would always be the < 1.0 API - and so no breakage at all. This is in the situation Gregory described where the top-level import in 1.0 would be `import skimage2`.
import skimage.compat.v1 as skimage
skimage.disable_v2_behavior()
Could you explain what you mean here? By "v1" do you mean what I have been calling the version < 1.0? What is the second line designed to do; haven't I already specified what behavior I want with the first line? Cheers, Matthew