Files
superset2/docs/developer_docs_versioned_docs/version-6.1.0/contributing/pkg-resources-migration.md
Superset Dev 752ebd47cb docs: cut 6.1.0 versions for docs, admin_docs, developer_docs, components
- Snapshot all four versioned docs sections at v6.1.0; master continues to
  serve as "Next" (lastVersion: current, banner: unreleased) so editing
  master keeps updating the canonical URLs
- Enable the previously-disabled components plugin and version it
- Rename stale "developer_portal" references to "developer_docs" across
  package.json scripts, manage-versions.mjs, theme files (DocVersionBadge,
  DocVersionBanner), DOCS_CLAUDE.md, and README.md (URL backward-compat
  redirect /developer_portal/* preserved)
- Add admin_docs version scripts; drop dead "tutorials" plugin id from
  the version badge
- Generalize fixVersionedImports in manage-versions.mjs to walk every
  section's snapshot and rewrite ../../src/ and ../../data/ imports,
  catching admin_docs and components files that previous version cuts
  would have broken
- Remove orphan files: developer_portal_versions.json,
  tutorials_versions.json, and stray empty versions.json files inside
  components/ and developer_docs/ content directories
2026-05-02 11:53:56 -07:00

2.8 KiB

title, sidebar_position
title sidebar_position
pkg_resources Migration Guide 9

pkg_resources Deprecation and Migration Guide

Background

As of setuptools 81.0.0, the pkg_resources API is deprecated and will be removed. This affects several packages in the Python ecosystem.

Current Status

Superset Codebase

The Superset codebase has already migrated away from pkg_resources to the modern importlib.metadata API:

  • superset/db_engine_specs/__init__.py - Uses from importlib.metadata import entry_points
  • All entry point loading uses the modern API

Production Dependencies

Some third-party dependencies may still use pkg_resources. Monitor your dependency tree for packages that haven't migrated yet.

Migration Path

Short-term Solution

Pin setuptools to version 80.x to prevent breaking changes:

# requirements/base.in
setuptools<81

This prevents the removal of pkg_resources while dependent packages are updated.

Long-term Solution

Update all dependencies to use importlib.metadata instead of pkg_resources:

Migration Example

Old (deprecated):

import pkg_resources

version = pkg_resources.get_distribution("package_name").version
entry_points = pkg_resources.iter_entry_points("group_name")

New (recommended):

from importlib.metadata import version, entry_points

pkg_version = version("package_name")
eps = entry_points(group="group_name")

Action Items

For Superset Maintainers

  1. The Superset codebase already uses importlib.metadata
  2. Monitor third-party dependencies for updates
  3. Update setuptools pin once the ecosystem is ready

For Extension Developers

  1. Update your packages to use importlib.metadata instead of pkg_resources
  2. Test with setuptools >= 81.0.0 once all packages are migrated

References