We’re happy to announce the release of RobotPy for 2021. We’ve continued cleaning up the mess we started last year, and things should hopefully be much smoother.
WPILib 2021.2.1 libraries included
All packages now ship with type hints which enable autocomplete in vscode when using the Python or pylance extensions
Upgraded pybind11 support no longer crashes when you forget to call super().__init__
New meta package – pip install robotpy will now bring in all robotpy packages, and there are various ‘extra’ specifiers that allow installation of other packages also. See robotpy-meta for details
The documentation and examples have not been updated yet. Soon?
The roborio installation process has been a huge pain as robotpy has grown, and this year’s installer is significantly better than what we’ve had in the past. Better error handling, single cache, we’ve gotten rid of the opkg stuff, and everything uses pip now.
Then use ‘download’ and ‘install’ to download python packages from pypi and the RobotPy server and install them on the roborio. The package names are exactly the same names that you would install locally on your computer with pip. In particular, you can use the new meta package to download everything:
Initial RobotPy for RoboRIO is out! Same features as yesterday, but they all work now. pyfrc and the robotpy-installer have been updated (thanks to Nick of team 5654 for that!). Still no OSX support, someone needs to step up and make that work.
I’ve pushed pyfrc as a beta release, so you have to pass the --pre flag to pip.
py -m pip install --pre pyfrc
Additionally, the RobotPy RoboRIO installer is no longer a standalone download, but it is installed as part of pyfrc.
Maintaining pure python bindings is a significant amount of work, and as WPILib gains more features and as more and more third party vendors join FRC, it becomes harder to provide support for those features and third party devices. To reduce the amount of work required to maintain RobotPy in the long term, this year we’re moving back to a WPILibC wrapper (which is what we were doing pre-2015).
In the long term, there are lots of benefits to this approach:
I anticipate that python programs on the RoboRIO will have higher performance
We will be able to support more third party vendors with minimal effort
RobotPy will be less effort to maintain for our limited development team
Unfortunately in the short term, the wrappers are not ready yet. My current goal is to have RobotPy 2020 available by the end of the weekend.
RobotPy is a community project and only exists because FRC community members contribute! If you’d like to help out, join us at https://gitter.im/robotpy/robotpy-wpilib!
In the meantime, you really should be working on strategy for your team right now anyways! If you do need to do some prototyping, RobotPy 2019 still works great in simulation and on hardware (with the 2019 image).
The 2019 release of RobotPy is now available! We had some deployment issues, but everything seems to be up now.
The core pieces of RobotPy are updated and available (pyfrc, wpilib, cscore, pynetworktables, utilities)
While we highly recommend using vscode for python development, we have not deployed the robotpy vscode plugin to the vscode marketplace yet. Hopefully later this week.
Pathfinder v2 is not available yet, so there are no RobotPy bindings for them. Pathfinder v1 should continue to work.
NavX support is now in its own library (robotpy-navx), and has been updated for 2019
The CTRE bindings have not been updated for 2019, but I’ll work on those tonight and I expect them to be available later this weekend
No new motor controller bindings have been created yet this year. If you are interested in seeing them available, please comment and we’ll see what we can do (though, this is labor-intensive and we could use more help with this!)
If you run into issues, please let us know or file a bug on github! Get the latest release at https://github.com/robotpy/robotpy-wpilib/releases