Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A arch-historical-archive
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch LinuxArch Linux
  • arch-historical-archive
  • Repository
  • arch-historical-archive
  • upload_pkg_internetarchive.py
Find file BlameHistoryPermalink
  • Florian Pritz's avatar
    Show exception stacktraces when we handle exceptions · ed70229b
    Florian Pritz authored May 25, 2019
    
    
    For a KeyError, print(e) just prints the key name that wasn't found.
    That's not even remotely helpful/obvious. Now we get a stacktrace and
    the usual "KeyError: foo" message, which is much better and actually
    what I wanted when I changed this.
    
    Signed-off-by: Florian Pritz's avatarFlorian Pritz <bluewind@xinu.at>
    ed70229b