Log file Viewer

[13:08:41] <elibrokeit> abadger1999: the usual solution to this would probably be to make ansible-base install an "ansible_base" module

[14:30:57] <FFY00> elibrokeit, people depend on the module being named ansible

[14:31:14] <FFY00> that would cause a lot of breakage

[14:32:45] <elibrokeit> wouldn't a "*-base" package imply part of the main program is being abstracted out into a low-level API?

[14:33:31] <FFY00> I would not necessarily assume that

[14:33:50] <FFY00> and AFAIK they are splitting the package, not introducing a new low level api

[14:34:29] <FFY00> people can keep depending on ansible

[14:34:38] <elibrokeit> so presumably "Requires-Dist: ansible" would install an "ansible" module and depend on "ansible-base", and the former would continue to provide a wrapper

[14:34:52] <FFY00> but now they have an option to just depend on ansible-base if they only need that functionality

[14:35:18] <elibrokeit> if they are splitting it, why rename it to ansible-base and make a new package which takes over the previous name o_0

[14:35:31] <FFY00> so that nothing breaks

[14:35:41] <FFY00> dependencies still work

[14:35:44] <FFY00> code still wokr

[14:35:46] <FFY00> *work

[14:36:14] <FFY00> but people have an option to change the dependency to ansible-base if they just need the minimal functionality provided by it

[14:36:17] <elibrokeit> anything that wants to switch to depend on ansible-base could rewrite its imports

[14:36:37] <elibrokeit> anything which doesn't, could use wrapped API provided by the ansible module

[14:36:55] <FFY00> I mean, yes, that's true

[14:37:16] <elibrokeit> this would avoid the issue where pip is only an installer, not a proper package manager.

[14:37:18] <FFY00> I'd imagine most people would just not bother and keep depending on ansible

[14:37:32] <elibrokeit> then those people aren't currently being helped

[14:38:35] <FFY00> the thing is that you would now need to mirror the ansible_base module in ansible

[14:38:41] <elibrokeit> but having an 'import ansible_base' module, and making 'import ansible' continue to provide proxied functionality *owned by the ansible distribution*, should solve all problems, surely

[14:39:02] <FFY00> so that the code does not break for people who depend on ansible instead of ansible_base

[14:39:48] <FFY00> it could be done but it's annoying to maintain

[14:40:08] <FFY00> namespace changes to ansible_base would need to be mirrored to ansible

[14:40:54] <FFY00> I would personally not opt to this option, especially for such a big project

[15:19:13] <abadger1999> <nod>

[15:20:14] <abadger1999> Yeah, we discussed making an ansible_base python module yesterday... It felt worse to us than just telling users there will be one time pain in the upgrade to 2.10

[15:20:26] <abadger1999> (discussed in the ansible project)