Releasing 0.6.0
Skipping a test that segfaults only on 1.5.0 and 2.0.0. The test was test_NR_DEC_issue188_beach_64bitsbox_jp2_41_decode. It was not introduced until the 2.1.x series and the fix was backported to 2.0.1. glymur.test.test_jp2k.TestJp2k.test_no_cxform_pclr_jpx was failing on 1.5.2 only. It's a pretty obscure test, so just skipping it on that release. Some tests for warnings are being skipped.
This commit is contained in:
parent
5311eb731b
commit
f88218d482
12 changed files with 52 additions and 20 deletions
|
|
@ -11,13 +11,13 @@ take a shortcut by supplying -1 as the
|
|||
resolution level. ::
|
||||
|
||||
>>> import glymur
|
||||
>>> file = glymur.data.nemo()
|
||||
>>> jp2 = glymur.Jp2k(file)
|
||||
>>> jp2file = glymur.data.nemo()
|
||||
>>> jp2 = glymur.Jp2k(jp2file)
|
||||
>>> thumbnail = jp2.read(rlevel=-1)
|
||||
|
||||
... display metadata?
|
||||
=====================
|
||||
There are two ways. From the unix command line, the script *jp2dump* is
|
||||
There are two ways. From the unix command line, the script **jp2dump** is
|
||||
available. ::
|
||||
|
||||
$ jp2dump /path/to/glymur/installation/data/nemo.jp2
|
||||
|
|
@ -25,8 +25,8 @@ available. ::
|
|||
From within Python, it is as simple as printing the Jp2k object, i.e. ::
|
||||
|
||||
>>> import glymur
|
||||
>>> file = glymur.data.nemo()
|
||||
>>> jp2 = glymur.Jp2k(file)
|
||||
>>> jp2file = glymur.data.nemo()
|
||||
>>> jp2 = glymur.Jp2k(jp2file)
|
||||
>>> print(jp2)
|
||||
File: nemo.jp2
|
||||
JPEG 2000 Signature Box (jP ) @ (0, 12)
|
||||
|
|
@ -241,8 +241,8 @@ you can use the :py:meth:`wrap` method with no box argument: ::
|
|||
|
||||
>>> import glymur
|
||||
>>> glymur.set_printoptions(codestream=False)
|
||||
>>> jfile = glymur.data.goodstuff()
|
||||
>>> j2k = glymur.Jp2k(jfile)
|
||||
>>> jp2file = glymur.data.goodstuff()
|
||||
>>> j2k = glymur.Jp2k(jp2file)
|
||||
>>> jp2 = j2k.wrap("newfile.jp2")
|
||||
>>> print(jp2)
|
||||
File: newfile.jp2
|
||||
|
|
@ -524,8 +524,8 @@ You can also build up XMP metadata from scratch. For instance, if we try to
|
|||
wrap `goodstuff.j2k` again::
|
||||
|
||||
>>> import glymur
|
||||
>>> jfile = glymur.data.goodstuff()
|
||||
>>> j2k = glymur.Jp2k(jfile)
|
||||
>>> j2kfile = glymur.data.goodstuff()
|
||||
>>> j2k = glymur.Jp2k(j2kfile)
|
||||
>>> jp2 = j2k.wrap("goodstuff.jp2")
|
||||
|
||||
Now build up the metadata piece-by-piece. It would help to have the XMP
|
||||
|
|
|
|||
|
|
@ -15,9 +15,9 @@ Contents:
|
|||
introduction
|
||||
detailed_installation
|
||||
how_do_i
|
||||
roadmap
|
||||
api
|
||||
whatsnew/index
|
||||
roadmap
|
||||
|
||||
------------------
|
||||
Indices and tables
|
||||
|
|
|
|||
|
|
@ -27,10 +27,10 @@ but you should also be able to install Glymur via pip ::
|
|||
|
||||
$ pip install glymur
|
||||
|
||||
This will install the **jp2dump** script that can be used from the unix command
|
||||
line, so you should adjust your **$PATH**
|
||||
to take advantage of it. For example, if you install with pip's
|
||||
`--user` option on linux ::
|
||||
This will install a script **jp2dump** that can be used from the unix command
|
||||
line for dumping JP2 metadata, so you should adjust your **$PATH**
|
||||
environment variable to take advantage of it. For example, if you install
|
||||
with pip's `--user` option on linux ::
|
||||
|
||||
$ export PATH=$HOME/.local/bin:$PATH
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,11 @@
|
|||
------------
|
||||
Known Issues
|
||||
------------
|
||||
|
||||
* Creating a Jp2 file with the irreversible option does not work
|
||||
on windows.
|
||||
* Eval-ing a :py:meth:`repr` string does not work on windows.
|
||||
|
||||
-------
|
||||
Roadmap
|
||||
-------
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue