# Should we warn (new) users about difficulties with Python 3 and alternative Python interpreters?

**URL:** <https://discourse.openrobotics.org/t/should-we-warn-new-users-about-difficulties-with-python-3-and-alternative-python-interpreters/3874>\
**Category:** ROS General\
**Created:** [February 4, 2018, 8:55am UTC](https://discourse.openrobotics.org/t/should-we-warn-new-users-about-difficulties-with-python-3-and-alternative-python-interpreters/3874 "2018-02-04T08:55:51Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![suforeman](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/suforeman/32/453_2.png) [@suforeman](https://discourse.openrobotics.org/u/suforeman)\
**Post date:** [February 8, 2018, 2:17am UTC](https://discourse.openrobotics.org/t/should-we-warn-new-users-about-difficulties-with-python-3-and-alternative-python-interpreters/3874/7 "2018-02-08T02:17:25Z")

</div>

It’s good that ROS2 has stardardized on python3.

As for ROS[1], support for pyrhon2.7 vs python3 comes down to the package author/owner.

Some package support python3 while sone doesn’t. It’s completely possible to use ROS with python3.

I don’t know if a guaranteed way to correctly notify users if their collection of code does/doesn’t work with a specific version of python.

---

_[View the full topic](https://discourse.openrobotics.org/t/should-we-warn-new-users-about-difficulties-with-python-3-and-alternative-python-interpreters/3874)._