Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F flatland-book
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Flatland
  • flatland-book
  • Merge requests
  • !4

Open
Created Aug 04, 2020 by alex_zharichenko@alex_zharichenko
  • Report abuse
Report abuse

Switching NamedTuple declaration to the preferred declaration for typing NamedTuple

  • Overview 0
  • Commits 2
  • Pipelines 2
  • Changes 2

namedtuple is preferablly done with just declaring everything in one line.

But, if using the typing version NamedTuple it's preferable to use the class definition as it helps with the readability problem the occurs when adding typing information to a namedtuple.

Source: https://docs.python.org/3/library/typing.html#typing.NamedTuple

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master