I don't see an actual 3.6.0 release. I think that he backed out a 3.6.0 release and instead made a 3.5.1 release. See this commit

It looks like perhaps the previous maintainer had set up for a 3.6.0 or ....

Yeah, if you look at the "configparser network graph" you see that when he pulled in my patch from the old repository it included a step from 3.5.0 to 3.6.0. That was probably my guessing that this was a big enough change to warrant a minor number bump. He then overrode that and made it a minor version number bump instead. The newest release is 3.5.1.

PING

I can see this fixing #8343, but #7370 is to address general issues with handling of the backports namespace (which involves several packages), so I'm not sure why this would close it. Otherwise this seems good.

This also appears to close #4155

So in all:

Fixes #8343 #4154
Closes #4155

Do you agree with that?

Anything I can do to get this merged?

Anything I can do to get this merged?

I should have been clear: I was looking for a response to #10433 (comment). If you agree, I'll merge it.

Ah rats, forgot to update the browser window before posting that last cry for attention. Didn't see your two recent comments. Apologies!

I believe that it also closes #7370, the general problem was that all but one of the backports packages were using "pkgutil-style" namespacing, and/but configparser was uing "pkg_resource-style". A namespace needs to be one style or another.

The problem isn't having multiple namespace packages loaded, it's a clash of namespace styles (Thank Goodness(tm) there's only one way to do it in Python... 😱)

As I mentioned in the configparser PR:

The backports package established the backports namespace as pkgutil-style and other backports packages have followed its lead.

configparser using the pkg_resource-style has caused many problems, see e.g. configparser issue #17.

Now that configparser is updated, the backports namespace ought to be namespace problem free.

That makes sense. Thanks for chasing it down!