Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • C cpython
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • cpython
  • Repository
  • cpython
  • Python
  • import.c
Find file BlameHistoryPermalink
  • Thomas Wouters's avatar
    Replace the run-time 'future-bytecode-stream-inspection' hack to find out · dd13e4f9
    Thomas Wouters authored Aug 27, 2000
    how 'import' was called with a compiletime mechanism: create either a tuple
    of the import arguments, or None (in the case of a normal import), add it to
    the code-block constants, and load it onto the stack before calling
    IMPORT_NAME.
    dd13e4f9
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7