GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Prefer flat namespace over using typing.io and typing.re · Issue #589 · python/typing

Prefer flat namespace over using typing.io and typing.re #589

New issue
Copy link
New issue
Copy link
Closed
Closed
Prefer flat namespace over using typing.io and typing.re#589
Copy link

Description

@srittau
srittau
opened on Oct 28, 2018
Issue body actions

The conclusion of python/typeshed#1652 says that importing from typing instead of typing.io and typing.re should be encouraged. That requires changes to PEP 484 as well the standard library documentation.

Activity

  1. srittau commented on Oct 28, 2018

    @srittau
    srittau
    on Oct 28, 2018
    CollaboratorAuthor
    More actions

    Opened https://bugs.python.org/issue35089 for the documentation issue, python/cpython#10173 for the corresponding PR.

  2. srittau commented on Oct 29, 2018

    @srittau
    srittau
    on Oct 29, 2018
    CollaboratorAuthor
    More actions

    I think this is done now.

  3. srittau
    closed this as completedon Oct 29, 2018

  4. gvanrossum commented on Oct 29, 2018

    @gvanrossum
    gvanrossum
    on Oct 29, 2018
    Member
    More actions

    The io and re namespaces still exist for backward compatibility, right? Could we ever start deprecating those?

  5. srittau commented on Oct 29, 2018

    @srittau
    srittau
    on Oct 29, 2018
    CollaboratorAuthor
    More actions

    It seems that typeshed never included those namespaces, so I guess using them in type checkers has never worked. That seems like a indication that deprecating them should not be too disrupting.

  6. gvanrossum commented on Oct 29, 2018

    @gvanrossum
    gvanrossum
    on Oct 29, 2018 via email
    Member
    More actions
    Ah cool.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.