Namespace collision with python-redfish-library from DMTF

[Lucas Alvares Gomes]

Not sure if we consider that a problem or not, but just to document: Current the python-redfish-library [0], which is a python library maintained by the DMTF (the folks who works on the Redfish specification) also uses the "redfish" namespace (e.g import redfish).

Again, we might not consider this a problem. But something to be aware of, I will leave it for the python-redfish developers to decide.

[0] https://github.com/DMTF/python-redfish-library

[Bruno Cornec (bruno-cornec)]

Is our namespace more "protected" by the fact we have the module on pypi ?

[Lucas Alvares Gomes (lucasagomes)]

Hi Bruno,

I honestly don't know, perhaps this is not even a problem. But I felt like reporting to let you guys know that it's a thing and installing both libraries in the same system (or venv) will cause collisions.

[Bruno Cornec (bruno-cornec)]

We are in contact with the team developing the DMTF libbrary, and we would like to coordinate. However, goals are different, and python library used are also different. SO it could be challenging.

And moreover, I don't think someone would like to use both of the library anyway, so while I think it's important to record the problem, I don't think in reality it will create problems.

And if there are, we then may solve that by changing namespacing.

[Dmitry Tantsur (divius)]

FYI it's probably going to be a problem if somebody attempts packaging both libraries. I think the policies may prevent that.