Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openpyxl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 243
    • Issues 243
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • openpyxl
  • openpyxl
  • Merge requests
  • !326

manifest: use private mime type database

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Bitbucket Importer requested to merge bitbucket/merged-pr-326 into branch/2.6 Mar 07, 2019
  • Overview 1
  • Commits 1
  • Pipelines 0
  • Changes 2

Created originally on Bitbucket by Hans-Jakob (Hans-Jakob Holtz)

Was already merged in Bitbucket before import, marked as merged by the import user

manifest: use private mime type database

This fixes #1221

The private mime database starts out as a copy of the global mime database.
In particular, it contains all well-known types like image/jpeg and image/png.
We add/overwrite our own types into that database instead of the global one.
This private database is immune to subsequent changes to the global mime
database, such as mimetypes.init() or conflicting add_type(...) calls.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: bitbucket/merged-pr-326