Support for Python 3: Now Is Better Than Never

python-logoOur latest Python agent release (version is available today, and includes some substantial changes that we are really excited about. The biggest of these should be exciting for you too: New Relic now supports Python 3.3!

With this update, we are also committing to support all future Python 3 releases. However, this also means we are officially ending support for Python 2.5. Don’t worry: those of you still running 2.5 can continue to use our previous agent versions. Though this means you will miss out on new features and patches, you will still have access to all the features you get today. We are still happily supporting Python 2.6 and 2.7. See our documentation on system requirements.

Keep in mind that this is a major version upgrade for our agent. We have extensively tested our Python 3 agent with Django (1.5), Flask (0.10.1), Pyramid (1.4.3), Tornado (3.1.1) and CherryPy (3.2.4). As always, we recommend that you install and test in your staging environment, and be sure to let us know if you see any quirks. All existing features will continue to work, including: X-Ray Sessions, Key Transactions, Thread Profiler, Database Metrics, App-Map… the list goes on.

Are you still working through which version of Python to use? Please check out Python 2 or Python 3?

So why did we make the move to support Python 3 now? Whether you are developing a fresh new app in Python 3 or transitioning your existing app, we want to help you notice any performance problems early. Now you can transition your app to Python 3 with confidence, knowing that your favorite performance monitoring tool is ready and waiting to catch any issues that might crop up.

For detailed information, be sure to check out our Python Agent Release Notes.'

Nathan Taggart is a Product Manager for New Relic. He oversees New Relic Browser, a client-side application performance monitoring tool. He's given talks on front-end application performance at Fluent and Front-end Ops Conf. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!