puremagic is a pure python module that will identify a file based off it's magic numbers.
It is designed to be minimalistic and inherently cross platform compatible. It is also designed to be a stand in for python-magic, it incorporates the functions from_file(filename[, mime]) and from_string(string[, mime]) however the magic_file() and magic_string() are more powerful and will also display confidence and duplicate matches.
It does NOT try to match files off non-magic string. In other words it will not search for a string within a certain window of bytes like others might.
Advantages over using a wrapper for 'file' or 'libmagic':
- Cross platform compatible
- No dependencies
- Does not have as many file types
- No multilingual comments
- Duplications due to small or reused magic numbers
(Help fix the first two disadvantages by contributing!)
- Python 2.7+
- Python 3.4+
Using travis-ci to run continuous integration tests on listed platforms.
In either a virtualenv or globally, simply run:
$ python setup.py install
It has no dependencies (other than the 2.7+ built-in argparse)
"from_file" will return the most likely file extension. "magic_file" will give you every possible result it finds, as well as the confidence.
import puremagic filename = "test/resources/images/test.gif" ext = puremagic.from_file(filename) # '.gif' puremagic.magic_file(filename) # [['.gif', 'image/gif', 'Graphics interchange format file (GIF87a)', 0.7], # ['.gif', '', 'GIF file', 0.5]]
With "magic_file" it gives each match, highest confidence first:
- possible extension(s)
- mime type
- confidence (All headers have to perfectly match to make the list, however this orders it by longest header, therefore most precise, first)
$ python -m puremagic [options] filename <filename2>...
$ python -m puremagic test/resources/images/test.gif 'test/resources/images/test.gif' : .gif $ python -m puremagic -m test/resources/images/test.gif test/resources/audio/test.mp3 'test/resources/images/test.gif' : image/gif 'test/resources/audio/test.mp3' : audio/mpeg
The file type is actually X but it's showing up as Y with higher confidence?
This can happen when the file's signature happens to match a subset of a file standard. The subset signature will be longer, therefore report with greater confidence, because it will have both the base file type signature plus the additional subset one.
You don't have sliding offsets that could better detect plenty of common formats, why's that?
Design choice, so it will be a lot faster and more accurate. Without more intelligent or deeper identification past a sliding offset I don't feel comfortable including it as part of a 'magic number' library.
Your version isn't as complete as I want it to be, where else should I look?
Look into python modules that wrap around libmagic or use something like Apache Tika.
Gary C. Kessler
For use of his File Signature Tables, available at: http://www.garykessler.net/library/file_sigs.html
For use of their shared-mime-info file (even if they do use XML, blea), available at: https://cgit.freedesktop.org/xdg/shared-mime-info/
MIT Licenced, see LICENSE, Copyright (c) 2013-2020 Chris Griffith