Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • I importlib_metadata
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • python-devs
  • importlib_metadata
  • Merge requests
  • !125

Remove importlib_metadata.__version__.

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Jason R. Coombs requested to merge bugfix/remove-dunder-version into master Jun 14, 2020
  • Overview 5
  • Commits 1
  • Pipelines 2
  • Changes 3

As discussed in importlib_resources#100 (closed), there's little value in exposing a __version__, despite PEP 396 recommending one.

What do you think, Barry? Are we on the cusp of a post-PEP-396 world? Should we create a new pep to supersede 396 that recommends against __version__ and recommends instead that packages not present a __version__ if they are part of a distribution package (i.e. have metadata)?

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: bugfix/remove-dunder-version