Audit the use of unsupported Python versions

Answer the Question:
  • Are there content items that do not meet the minimum version requirements (Python 3.5+) on this server?

Python 2.7 has reached end of life maintenance status. Support from the Python language governing body ended on January 1, 2020 and it is no longer receiving security patches.

Connect has continued to support Python 2.7 beyond its EOL status, but will join the community in ending support as of March 2022 (Release 2022.03.0). Learn more here about the minimum version of Python supported in Connect.

Before upgrading to Connect 2022.03.0+, consider the following recommended actions:

  1. Set a System Message on the server to warn Publishers about your upgrade timeline and the breaking change.
  2. Use this Audit Report to identify all content using an unsupported Python version.
  3. Contact any users who have content that will break due to this upgrade.

Publishers and Content Owners should be made aware that:

Step 1 - Get the report code

Step 2 - Run & Customize the report

This R Markdown report uses the /v1/content and /v1/users API endpoints available in Connect 1.8.6 and later. Visit the Connect API Reference documentation for more information.

Requirements: Administrator API Key

Create an .Renviron file to store your API key and Connect server URL.

Your Connect server URL is the same URL you use to access the Connect dashboard, minus the connect path. If you access the dashboard at, the server URL is

# ~/.Renviron
# The CONNECT_SERVER URL must have a trailing slash.

Restart your R session to pick up on the new environment variables.

Step 3 (optional) - Publish the report to Connect

If you are push-button publishing from the RStudio IDE, we recommend the selection “Publish document with source code” so that the report can be re-executed on a schedule.1

Connect deployment dialog box showing publication options

Step 4 (optional) - Set the report to update on a schedule

Automate a data refresh of your report by setting it up to run on a schedule. Open the Schedule content management pane to get started.

Read more about Scheduling in the Connect User Guide.

Back to top


  1. Connect will automatically provide these environment variables for you when you publish. If you are on an older version of Connect, or if this feature has been disabled by your admin, you should reference for how to create an API key and for how to input environment variables into the Vars pane of Connect.↩︎