Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • cube-doctor cube-doctor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • cubicweb
  • cube-doctorcube-doctor
  • Issues
  • #6
Closed
Open
Created Nov 13, 2020 by Laurent Peuch@bramMaintainer

explore on how feasable it is to parse existing code base to fix modification we are already aware of

Instead of waiting for warning to raises and fix them this way, some of the modification we make seems actually quite easy to detect and pre-fix in advance.

We might want to explore this way to win some time and avoid unexpected crash in the future when the warning based approach failed.

It's not a problem if we don't catch all of them, the idea is to move forward.

For example: logilab.common.deprecated -> logilab.common.callable_deprecated

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking