[virtuald]

It is correct to say that python is not officially supported by FRC, and that at a competition if you have a problem there will be less teams that will be able to help you with a language-specific problem.

However (as far as I know), because of the WPILib interface has been identical to the supported languages, most problems that people have when using python in FRC are the typical problems that anyone else in FRC has -- how to use the various devices that WPILib provides you. This means that other teams at a competition can help you, as long as you don't have a language specific problem. It's the same reason Java and C++ teams can help each other.

In it's 4 year history, there have been very few problems that affected the python WPILib that did not also affect the other languages.

In 2015, the WPILib interface will be 100% python, instead of wrappers, so this year it is arguably more risky to use than in previous years. Once again though, the interface will be identical to a supported language. Additionally, we've created a lot of unit tests, and are aiming for high test coverage to mitigate those potential problems.

Additionally, in 2015 python will have expanded language-specific documentation, full gazebo simulation support, and eclipse plugins with similar functionality to the C++/Java functionality.