From 09651c27b63901d1f1eb5419e458f6950935ee10 Mon Sep 17 00:00:00 2001 From: jevans Date: Mon, 10 Feb 2014 19:38:37 -0500 Subject: [PATCH] No longer claiming any windows support. #167 --- docs/source/detailed_installation.rst | 22 +++++----------------- docs/source/introduction.rst | 8 +++----- docs/source/roadmap.rst | 4 +--- 3 files changed, 9 insertions(+), 25 deletions(-) diff --git a/docs/source/detailed_installation.rst b/docs/source/detailed_installation.rst index 4e17c4f..d1b3084 100644 --- a/docs/source/detailed_installation.rst +++ b/docs/source/detailed_installation.rst @@ -45,13 +45,6 @@ the path will be :: $XDG_CONFIG_HOME/glymur/glymurrc -On windows, the path to the configuration file can be determined -by starting up Python and typing :: - - import os - os.path.join(os.path.expanduser('~'), 'glymur', 'glymurrc') - - You may also include a line for the version 1.x openjpeg library if you have it installed in a non-standard place, i.e. :: @@ -70,9 +63,8 @@ packages/RPMs/ports/whatever without going through pip. Mac OS X -------- -All the necessary packages are available to use glymur with Python 2.6, 2.7, -and 3.3 via MacPorts. For python 3.3, you should install the following set of -ports: +All the necessary packages are available to use glymur with MacPorts. +For python 3.3, you should install the following set of ports: * python33 * py33-numpy @@ -108,12 +100,8 @@ difficulties: Windows ------- -32-bit WinPython 2.7.5 seemed to work with OpenJPEG 1.X, 2.0, and the -development version, but still required contextlib2 and mock to be -installed via pip. WinPython 3.3.2, however, seems to have trouble -with OpenJPEG 2.0, so I would suggest using the development version with -that configuration. I no longer have any access to a windows machine, -so I cannot currently offer much guidance here. +The 0.6.x series of Glymur is untested on windows and I make no promises here. +I suggest that windows users check the 0.5.x series. ''''''' @@ -145,5 +133,5 @@ OpenJPEG counterparts are already failing, and others which do pass but still produce heaps of output on stderr. Rather than let this swamp the signal (that most of those tests are actually passing), they've been filtered out for now. There are also more skipped tests on Python 2.7 -than on Python 3.3. The important part is whether or not any test +than on Python3. The important part is whether or not any test errors are reported at the end. diff --git a/docs/source/introduction.rst b/docs/source/introduction.rst index 23698e3..38193eb 100644 --- a/docs/source/introduction.rst +++ b/docs/source/introduction.rst @@ -11,8 +11,8 @@ In regards to metadata, most JP2 boxes are properly interpreted. Certain optional JP2 boxes can also be written, including XML boxes and XMP UUIDs. There is some very limited support for reading JPX metadata. -Glymur 0.6 works on Python versions 2.7, 3.3 and 3.4. If you have 2.6, you should -use the 0.5 series. +Glymur 0.6 works on Python versions 2.7, 3.3 and 3.4. If you have Python 2.6, +you should use the 0.5 series of Glymur. OpenJPEG Installation ===================== @@ -24,9 +24,7 @@ OpenJPEG, please consult http://www.openjpeg.org. If you use MacPorts or if you have a sufficiently recent version of Linux, your package manager should already provide you with a version of -OpenJPEG 1.X which glymur can already use. If your platform is windows, -I suggest using the windows installers provided to you by the OpenJPEG -folks at https://code.google.com/p/openjpeg/downloads/list . +OpenJPEG 1.X which glymur can already use. Glymur Installation =================== diff --git a/docs/source/roadmap.rst b/docs/source/roadmap.rst index c29d4f4..6651587 100644 --- a/docs/source/roadmap.rst +++ b/docs/source/roadmap.rst @@ -5,6 +5,4 @@ Roadmap Here's an incomplete list of what I'd like to focus on in the future. * continue to monitor upstream changes in the openjp2 library - * investigate using CFFI or cython instead of ctypes to wrap openjp2 - * investigate adding write support for UUID/XMP boxes (potentially a big project) - * investigate JPIP (likely to be an even bigger project) + * investigate JPIP (likely to be a big project)