It pains me to ask if solo1-cli could use the "solo1" python package library name instead of "solo" ?
It conflicts with django-solo, and since your library is supposed to be experimental, and doesn't match the cli name,
it's a better candidate for resolving the name conflict.
It pains me to ask if solo1-cli could use the "solo1" python package library name instead of "solo" ?
It conflicts with django-solo, and since your library is supposed to be experimental, and doesn't match the cli name,
it's a better candidate for resolving the name conflict.