Project dependencies may have API risk issues about transitions HOT 1 CLOSED

Hello @PyDeps,

sorry for not answering earlier. An interesting project/mission you have there going and I can follow your reasoning. What took me so long was that I had to make up my mind whether a version limit would make transitions easier and/or more reliable to use and I came to the conclusion it would not.

You mention add_metaclass as a 'problematic' method since it was introduced in six 1.4.0.
However, you can nevertheless use transitions with an earlier version. Only the diagrams extension would be affected but this is as the name suggests just an optional extension.

six is mostly used for its string_types which I hope won't go away in the foreseeable future.
This is also why I decided to not introduce upper version limits since this might limit future releases of transitions to be used in for instance poetry projects with rather strictly pinned six versions even though transitions would work perfectly fine in this context.

I guess I should take a look at the other requirements_*.txt files since the APIs of pygraphviz, mypy or pytest might be more volatile than six. A lower version limit for six might be a good fit for requirements_diagrams.txt.

I will close this issue (and the related PR) but if you (or any future reader) think(s) I overlooked important factors, let me know by leaving a comment.

Thanks again for your input. I appreciate your work and effort to make open source software better.

from transitions.