On Tue, May 12, 2020 at 10:02 AM Daniel Frey <djqf...@gmail.com> wrote: > > On 5/12/20 6:52 AM, Victor Ivanov wrote: > > Python has indeed been a bit of a mess recently for me as well, but I > > haven't had any major issues. Presumably, this could be attributed to > > the fact that since python migrations started I have been using the > > --changed-deps flag to emerge, which I noticed did help to clean a few > > things up during world upgrades. > > > > I had one package that insisted pulling an old version of python while > everything else wanted 3.7 or 3.8, and I had to unmerge the offending > package. I hope I don't need that package any time soon...
Keep in mind that python is slotted, so you can have both in most cases. It only gets messy when you start having conflicts. I did have a package try to downgrade another package because python-2 support is enabled by default and the newer version of the package didn't support it. The package didn't need python-2 - it was just responding to the profile defaults. I just manually set the USE flags for that package to disable python-2 for it. It probably wouldn't have hurt much to do the downgrade either, but that isn't ideal. I suspect we'll see this stuff continue to shuffle for a few more weeks and then as the old versions of python are banned/etc the issues will start to go away. I think the main reason this is so user-visible is that the profiles were changed before all the packages supported the newer versions. -- Rich
