> This is all that is bad about Python in one problem: poor > documentation, awkward package management, and backwards compatibility > issues. It's almost enough to make me glad I use C++ at work.
Since when is C++ the holy grail of backwards compatibility? Add a private variable the wrong way, and boom. Ever tried to make an app crosscompile between various compilers? Or share one library between compilers? Maybe you could provide some examples for your claim that others do this better, especially in the C++ world. A minor version change is a sign for binary breakage. It's not python's fault if 3rd-party-packages aren't up-to-date less than 2 months after the release. And I guess there is a reason for you chosing 2.6 - how do you expect progress to happen *without* changes? Python and setuptools aren't perfect. But going cutting edge and then complaining about things not being as smooth as they are with established paths is not exactly provoking sympathy. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
