# Which Python 3 features can we use once we are in a Python 3 only world?

**URL:** <https://www.rubin.community/t/which-python-3-features-can-we-use-once-we-are-in-a-python-3-only-world/2448>\
**Category:** Data Management\
**Tags:** python3\
**Created:** [November 30, 2017, 3:11pm UTC](https://www.rubin.community/t/which-python-3-features-can-we-use-once-we-are-in-a-python-3-only-world/2448 "2017-11-30T15:11:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ktl](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ktl/32/1373_2.png) [@ktl](https://www.rubin.community/u/ktl)\
**Post date:** [November 30, 2017, 3:18pm UTC](https://www.rubin.community/t/which-python-3-features-can-we-use-once-we-are-in-a-python-3-only-world/2448/2 "2017-11-30T15:18:32Z")

</div>

_A priori_ I would presume that any feature available in our supported Python version should be usable. There may be some features that we collectively decide are not appropriate for our usage or should be restricted (akin to brace initialization in C++), but given the relative recency of Python 3 and its relative lack of backward-compatibility cruft, I wouldn’t expect much of that. I’d also look to authorities and external best practice guides first.

---

_[View the full topic](https://www.rubin.community/t/which-python-3-features-can-we-use-once-we-are-in-a-python-3-only-world/2448)._