Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • U uPython-mirror
  • 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
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • 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
  • TASTETASTE
  • uPython-mirror
  • Repository
  • uPython-mirror
  • py
  • compile.c
Find file Blame History Permalink
  • Damien George's avatar
    py: For viper compile errors, add traceback with function and filename. · 84d59c28
    Damien George authored Jul 27, 2015
    ViperTypeError now includes filename and function name where the error
    occurred.  The line number is the line number of the start of the
    function definition, which is the best that can be done without a lot
    more work.
    
    Partially addresses issue #1381.
    84d59c28