Python 3 for the FIRST Robotics Competition (FRC)

Initial RobotPy 2020 pieces available

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.

Using it is mostly the same as before:

py -m robotpy-installer download-robotpy
py -m robotpy-installer install-robotpy

There’s still work to be done, join us on gitter to help finish it up!

Initial RobotPy 2020 pieces available

Non-roborio builds of some core robotpy pieces are now available for installation from pypi! If you’re on Windows and have Python 3.6-3.8, you can do this to try it out:

py -m pip install -U wpilib robotpy-halsim-gui robotpy-wpilib-utilities

It’s best to do this in a clean virtualenv for now – you will need to uninstall pyfrc as it will conflict with the new sim. Once you have it installed, you can:

py sim

Please give it a try and let us know what breaks. There’s still a lot missing, but it’s coming soon:

  • commands
  • SendableChooser
  • Shuffleboard
  • Some new 2020 features

Tomorrow night I’ll push a roborio release, pyfrc/installer updates, and hopefully some 3rd party vendor packages.

RobotPy 2020 availability

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!

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).

RobotPy 2019 Release

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

RobotPy 2018 releases

I’ve gotten pretty lazy at updating this website, but we’ve had a ton of releases this year already. Be sure to update to the latest release of each RobotPy product that you’re using! s