Replies: 2 comments 5 replies
-
Thanks for raising the topic and #1167, which gives details about the matplotlib version conflict. To further this discussion, does anyone know of other costs or limitations incurred by python 3.8? |
Beta Was this translation helpful? Give feedback.
-
AutoGen by itself doesn't have many dependencies and can easily support Python 3.8 until its eol later this year (https://devguide.python.org/versions/). It is a pain sometimes to write for 3.8, but what can you do. Different examples and notebooks will be very different because they will sometime use the latest experimental libraries and that's fine for each of them. It is highly likely they will not support older versions of Python and they will be in conflict with each other. AutoGen has a huge potential and I believe those download numbers will be huge and will have to work in many different environments. There is no need to limit that because of examples or to limit examples only to use well supported libs. |
Beta Was this translation helpful? Give feedback.
-
Basis for this discussion is #1167 as well as the typical reasons for dropping support of an older Python version.
My thinking on the issue is that the maximum version range should be supported up until inclusion of a version begins to incur any amount of technical debt or sacrifice, which appears to be the case. It can only continue downhill from there. Instead, we should continue the climb up the mountain as soon as we have a reasonable excuse to.
Beta Was this translation helpful? Give feedback.
All reactions