debian/0000755000000000000000000000000012146073300007162 5ustar debian/python-pyx-doc.docs0000644000000000000000000000015712063407313012744 0ustar AUTHORS faq/_build/latex/pyxfaq.pdf faq/_build/faq manual/_build/latex/manual.pdf manual/_build/manual gallery debian/python-pyx-doc.doc-base.faq0000644000000000000000000000071212063620476014243 0ustar Document: pyx-faq Title: Some frequently and not so frequently asked questions about PyX Author: Gert-Ludwig Ingold Abstract: FAQ for the PyX plotting library for preparing scientific plots using Python and LaTeX. Section: Science/Data Analysis Format: HTML Index: /usr/share/doc/python-pyx-doc/faq/index.html Files: /usr/share/doc/python-pyx-doc/faq/*.html Format: PDF Files: /usr/share/doc/python-pyx-doc/pyxfaq.pdf debian/python-pyx.docs0000644000000000000000000000001711255520144012174 0ustar README AUTHORS debian/python-pyx-doc.doc-base.gallery0000644000000000000000000000110712063407212015121 0ustar Document: pyx-gallery Title: PyX gallery Author: Jörg Lehmann , Michael Schindler , André Wobst Abstract: More complicated or real world examples of the PyX plotting library, illustrating various aspects of this Python library for plotting scientific data. The code is designed to be a starting point for your own experiments with PyX. Section: Science/Data Analysis Format: Text Files: /usr/share/doc/python-pyx-doc/gallery/* Index: /usr/share/doc/python-pyx-doc/gallery/README debian/watch0000644000000000000000000000005411211313104010201 0ustar version=2 http://sf.net/pyx/PyX-(.*).tar.gz debian/README.source0000644000000000000000000000027311264665103011353 0ustar This package uses quilt to manage Debian-specific changes to the upstream source. Install the "quilt" package and consult: /usr/share/doc/quilt/README.source for further details. debian/test0000644000000000000000000000446611211313104010065 0ustar #!/usr/bin/python2.3 # $Id: test 92 2006-06-11 05:12:16Z graham $ # # A script for testing all of the example files shipped with PyX. Requires # Ghostscript and ImageMagick. import os.path import shutil import sys import os gs_args = ['-r400', '-dQUIET', '-dEPSCrop', '-dNOPAUSE', '-dBATCH', '-sDEVICE=ppmraw'] def run_test(interp, file): """Execute the example code and return the output filename.""" base, ext = os.path.splitext(file) base = os.path.basename(base) print base + ":", name = {} for ft in ('eps', 'ppm', 'png'): name[ft] = "%s-%s.%s" % (base, interp, ft) if os.spawnlpe(os.P_WAIT, interp, interp, file, new_env): print interp + " FAILED" return if not os.path.exists(base + '.eps'): print "no EPS file" return else: os.rename(base + '.eps', name['eps']) gs_cmd = ['gs'] + gs_args + ['-sOutputFile=' + name['ppm'], name['eps']] if os.spawnvp(os.P_WAIT, 'gs', gs_cmd): print "gs FAILED" return os.unlink(name['eps']) convert_cmd = ['convert', '-resize', '25%', name['ppm'], name['png']] if os.spawnvp(os.P_WAIT, 'convert', convert_cmd): print "convert FAILED" return os.unlink(name['ppm']) print "ok" return name['png'] # Are we in the correct directory? if not os.path.exists("debian/changelog") or not os.path.exists("examples"): print "must be in the toplevel directory of the PyX source" sys.exit(1) # Set $PYTHONPATH so that we point to the correct location of the module. new_env = os.environ.copy() if not os.environ.has_key("SYS_PYX"): new_env["PYTHONPATH"] = os.getcwd() # Setup a directory for output. if not os.path.isdir("debian/output"): os.mkdir("debian/output") # Build a list of files to test. def get_files(dir): r = [] for (dirpath, dirnames, filenames) in os.walk(dir): if ".svn" in dirnames: dirnames.remove(".svn") for file in filenames: full = os.path.join(dirpath, file) full = os.path.abspath(full) if file.endswith(".py"): r.append(full) elif file.endswith(".dat") or file.endswith(".jpg"): # The .dat and .jpg files are used by some of # the examples. shutil.copy(full, "debian/output") return r files = get_files("examples") files += get_files("gallery") os.chdir("debian/output") tests = 0 failed = 0 for file in files: tests += 1 if not run_test("python", file): failed += 1 print tests, "tests,", failed, "FAILED" debian/source/0000755000000000000000000000000012146073143010467 5ustar debian/source/format0000644000000000000000000000001411373112130011664 0ustar 3.0 (quilt) debian/patches/0000755000000000000000000000000012146073143010616 5ustar debian/patches/series0000644000000000000000000000013512063617001012025 0ustar sphinx-mathjax.patch setup.cfg.patch pyxrc.patch pyxrc-load.patch createlfs-no-foiltex.patch debian/patches/setup.cfg.patch0000644000000000000000000000107011565320413013532 0ustar Description: Include C extensions when building. Author: Stuart Prescott --- a/setup.cfg +++ b/setup.cfg @@ -2,11 +2,11 @@ # In this section you can specify which c extension modules should be built # C extension module for fast t1font decoding and encoding -build_t1code=0 +build_t1code=1 # Python bindings for the kpathsea library. You need the kpathsea header # and library and you may need to specify their location below. -build_pykpathsea=0 +build_pykpathsea=1 # use setuptools instead of distutils use_setuptools=0 debian/patches/createlfs-no-foiltex.patch0000644000000000000000000000131211570475256015701 0ustar Description: Don't generate font details using foiltex Author: Stuart Prescott --- a/pyx/data/lfs/createlfs.py +++ b/pyx/data/lfs/createlfs.py @@ -28,10 +28,7 @@ ("10ptex", "article", "10pt", "\\usepackage{exscale}" , ), ("11ptex", "article", "11pt", "\\usepackage{exscale}" , ), ("12ptex", "article", "12pt", "\\usepackage{exscale}" , ), - ("foils17pt", "foils", "17pt", "" , ), - ("foils20pt", "foils", "20pt", "" , ), - ("foils25pt", "foils", "25pt", "" , ), - ("foils30pt", "foils", "30pt", "" , ), ) + ) for style in styles: os.system("echo \'%s\n%s\n%s\n%s\'|latex createlfs.tex" % style) debian/patches/pyxrc-load.patch0000644000000000000000000000066211565320331013723 0ustar Description: Include /etc/pyxrc in the list of config files read Author: Stuart Prescott --- a/pyx/config.py +++ b/pyx/config.py @@ -27,6 +27,7 @@ config = ConfigParser.ConfigParser() config.readfp(filelocator.locator_classes["internal"]().openers("pyxrc", [], [""], "r")[0]()) +config.read("/etc/pyxrc") config.read(os.path.expanduser("~/.pyxrc")) def get(section, option, default=_marker): debian/patches/sphinx-mathjax.patch0000644000000000000000000000137712063617105014612 0ustar Description: Switch mathjax to pngmath for documentation build Author: Stuart Prescott --- a/manual/conf.py +++ b/manual/conf.py @@ -27,7 +27,7 @@ # Add any Sphinx extension module names here, as strings. They can be extensions # coming with Sphinx (named 'sphinx.ext.*') or your custom ones. -extensions = ['sphinx.ext.mathjax', 'sphinx.ext.todo'] +extensions = ['sphinx.ext.pngmath', 'sphinx.ext.todo'] # Add any paths that contain templates here, relative to this directory. templates_path = ['_templates'] @@ -226,5 +226,4 @@ # -- Other options ------------------------------------------------------------ -mathjax_path = 'http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=default' todo_include_todos = True debian/patches/pyxrc.patch0000644000000000000000000000067211565320372013014 0ustar Description: Use the texipc system for extracting DVIs Author: Stuart Prescott --- a/pyx/data/pyxrc +++ b/pyx/data/pyxrc @@ -45,7 +45,7 @@ # You will gain immediate access to the dvi-output of TeX by that, # which will substantially improve the performance of certain # operations (e.g. the usage of PyX markers). -texipc = 0 +texipc = 1 [filelocator] # runtime configuration of file search mechanism debian/compat0000644000000000000000000000000212063216555010371 0ustar 9 debian/python-pyx-doc.doc-base.examples0000644000000000000000000000116612063407014015305 0ustar Document: pyx-examples Title: PyX examples Author: Jörg Lehmann , Michael Schindler , André Wobst Abstract: Simple examples of the PyX plotting library, illustrating various aspects of this Python library for plotting scientific data, including: controlling axes, tick labels, reading data from files, plotting equations, adding pictures to plots, adding labels and text to plots. Section: Science/Data Analysis Format: Text Files: /usr/share/doc/python-pyx-doc/examples/* Index: /usr/share/doc/python-pyx-doc/examples/README debian/python-pyx-doc.doc-base.manual0000644000000000000000000000074012063410421014735 0ustar Document: pyx-manual Title: PyX Programming Manual Author: Jörg Lehmann , André Wobst Abstract: Programming reference for the PyX plotting library for preparing scientific plots using Python and LaTeX. Section: Science/Data Analysis Format: HTML Index: /usr/share/doc/python-pyx-doc/manual/manual.html Files: /usr/share/doc/python-pyx-doc/manual/*.html Format: PDF Files: /usr/share/doc/python-pyx-doc/manual.pdf debian/python-pyx-doc.examples0000644000000000000000000000001311261147526013627 0ustar examples/* debian/changelog0000644000000000000000000002355312146073054011052 0ustar pyx (0.12.1-2) unstable; urgency=low * Upload to unstable. -- Stuart Prescott Sun, 19 May 2013 16:50:09 +1000 pyx (0.12.1-1) experimental; urgency=low * New upstream release * Update maintainer address. * Update copyright format URL. * Bump standards version to 3.9.4 (no changes required). * Drop postinst that was needed for lenny->squeeze upgrades. -- Stuart Prescott Mon, 17 Dec 2012 13:45:12 +0000 pyx (0.11.1-2) unstable; urgency=low * Add texlive-latex-base to Build-Depends to correctly rebuild lfs files if only binary packages are being built (LP: #896924). * Use the sphinx debhelper module to check over the sphinx documentation. * Build-depend on debhelper >= 8.9.5 to stop dh_compress compressing sphinx files. -- Stuart Prescott Sun, 27 Nov 2011 21:09:42 +0000 pyx (0.11.1-1) unstable; urgency=low * New upstream release. * Change documentation build system to sphinx in line with new upstream docs. * Rebuild lfs files as part of build process. * Refresh patchs for new version: - drop manual-latex-define.patch no longer needed with sphinx. - drop siteconfig-static.patch: not needed with new build system - drop pyx-text-warnings26.patch: warnings fixed upstream * Add patch sphinx-mathjax.patch to use pngmath in sphinx rather than mathjax which is not yet in Debian. * Add patch createlfs-no-foiltex.patch to skip generation of foiltex-based lfs files that would require non-free components. * Switch to dpkg-source 3.0 (quilt) format. * Switch from python-support to dh_python2 as build helper. * Update copyright format to newer DEP-5 specification. * Add new files to copyright file. * Bump standards version to 3.9.2 (no changes required). * Set DM-Upload-Allowed: yes -- Stuart Prescott Fri, 20 May 2011 00:13:52 +0100 pyx (0.10-2) unstable; urgency=low * Build-depend on new python-old-doctools package that provides tools no longer in python 2.6 (closes: #568046). * Bump standards version to 3.8.4 (no changes required). -- Stuart Prescott Wed, 10 Feb 2010 16:06:53 +0000 pyx (0.10-1) unstable; urgency=low * New maintainer (closes: #552750). * Revert unneeded versioned build-dependency on python-all-dev. * Add a preinst script to clean up after python-central (working around bug #479852 in python-central) (closes: #553271). * Convert packaging to quilt. -- Stuart Prescott Thu, 29 Oct 2009 23:47:39 +0000 pyx (0.10-0+nmu3) unstable; urgency=low * Non-maintainer upload. * Build-Depend on python-all-dev (>= 2.5.4) for python.mk. -- Kumar Appaiah Mon, 19 Oct 2009 17:21:33 -0500 pyx (0.10-0+nmu2) unstable; urgency=low * Non-maintainer upload * Fix build system for compatibility with Python 2.6 (closes: #547872) - change debhelper compat level to dh7. - remove unneeded sections of debian/rules. - remove versioned depends/conflicts/replaces for packages that haven't existed since Sarge. * Silence DeprecationWarning output from Python 2.6. * Move doc package to doc section. * Add doc-base entries for documentation. * Bump standards version to 3.8.3 (no changes required). -- Stuart Prescott Wed, 30 Sep 2009 01:09:13 +0100 pyx (0.10-0+nmu1) unstable; urgency=low * Non-maintainer upload * New upstream release (closes: #454765) * Update build-deps to use texlive rather than tetex * Update depends to use texlive rather than tetex (closes: #467207) * Recommend a smaller latex package to reduce the installation size. texlive-latex-base seems to be the smallest package that allows at least the (trivial) examples to be built (closes: #503577) * Fix copyright file to include names and years of upstream authors -- Stuart Prescott Fri, 15 May 2009 00:23:04 +0100 pyx (0.9-4) unstable; urgency=low * New maintainer (closes: #408140). -- Ernesto Nadir Crespo Avila Mon, 29 Jan 2007 21:22:39 -0400 pyx (0.9-3) unstable; urgency=low * New maintainer. Thank you for more than three years of maintenance, Graham! Closes: #400087 * Don't hard-code python 2.3 in manual/Makefile. Thanks to Matthias Klose for the bug report and patch. Closes: #392634 * Remove obsolete dh_python call from debian/rules. -- Thomas Viehmann Sun, 26 Nov 2006 14:04:53 +0100 pyx (0.9-2) unstable; urgency=low * Support the new Python policy. (closes: #373372) -- Graham Wilson Thu, 15 Jun 2006 05:53:37 +0000 pyx (0.9-1) unstable; urgency=low * New upstream release. * Umm... don't build-depend libkpathsea4-dev. * Move examples to -doc package, since their number seems to be growing; they also seem more appropriate in that package. * Update standards version; no changes. * test script changes: - test files in the gallery directory as well - make the output less verbose -- Graham Wilson Sun, 11 Jun 2006 05:04:08 +0000 pyx (0.8.1-2) unstable; urgency=low * Rebuild against libkpathsea4. * Output number of tests that were run. * Use a variable for the python executable in rules, to make it easier to build for a different Python version. -- Graham Wilson Tue, 28 Feb 2006 08:46:25 +0000 pyx (0.8.1-1) unstable; urgency=low * New upstream release. - don't try to build the examples.pdf file anymore - update siteconfig.py to reflect new variable names * Only install .py and .dat files into the examples directory. * Don't build python2.?-pyx packages, just build for the current python. * Update the watch file to support uscan's new syntax. * Updated standards version (no changes). * Don't build depend on gs, since it isn't needed any longer. * Don't attempt to support noopt in DEB_BUILD_OPTIONS, since it apparently hasn't been working for some time. * Update the FSF's address in the copyright file. * Suggest python-imaging. * Minor changes to the test script: - reduce images 4x so they come out the correct size - copy .jpg files as well as .dat files - count how many tests failed - check if SYS_PYX is set, and if so, use the system's copy of PyX -- Graham Wilson Sun, 04 Sep 2005 22:34:53 +0000 pyx (0.7.1-2) unstable; urgency=low * Make python-pyx depend on the same version of python2.x-pyx. (closes: #287950) * Build depend on gs-gpl or gs. (closes: #287548) -- Graham Wilson Thu, 06 Jan 2005 03:35:40 +0000 pyx (0.7.1-1) unstable; urgency=low * New upstream bugfix release. * Strip the shebang-python line from the module so dh_python doesn't generate dependencies on the python package. Should also stop some linda warnings. * In the test script, don't die if one of the programs fails, just move on to the next test. Also remove the generated EPS file. * Set build depends indep to packages needed for building the documentation (tetex-extra and tipa). -- Graham Wilson Sat, 25 Dec 2004 06:42:57 +0000 pyx (0.7-3) unstable; urgency=low * Enable texipc by default in pyxrc. -- Graham Wilson Mon, 29 Nov 2004 23:35:22 +0000 pyx (0.7-2) experimental; urgency=low * Install pyxrc into the -common package. -- Graham Wilson Sun, 14 Nov 2004 00:38:29 +0000 pyx (0.7-1) experimental; urgency=low * New upstream release. (closes: #280861) * Build documentaion, since upstream no longer includes it in the source. * Build depend on tipa. * Remove manual/*.png files on clean. * Call setup.py build_ext, not build. * Install example files into -common, and add symlinks from the versioned packages. * Ensure siteconfig.py points to the correct locations. * Add the missing INDEX files in the examples subdirectories. * Add a test script. -- Graham Wilson Sat, 13 Nov 2004 16:57:18 +0000 pyx (0.6.3-3) unstable; urgency=low * Correct the URL in the watch file. * Build depend on python. -- Graham Wilson Thu, 08 Jul 2004 23:47:56 +0000 pyx (0.6.3-2) unstable; urgency=low * Call dh_installdocs with -a (not -A) in binary-arch. * Remove build depends indep, since we don't exactly build anything. * Build-depend on tetex-bin for kpsewhich. (closes: #248630) * Recommend tetex-extra. -- Graham Wilson Wed, 12 May 2004 20:08:36 +0000 pyx (0.6.3-1) unstable; urgency=low * The -pyx packages now depend on an explicit version of -common. * Add a watch file for uscan. * New upstream release. (closes: #241669) * Don't build documentation, just install what is distributed. * Generate list of example files at build time. -- Graham Wilson Sun, 02 May 2004 01:59:13 +0000 pyx (0.4.1-4) unstable; urgency=low * Argh. Only build the manual when building arch-indep packages. - tetex-extra and gs are now build-depends-indep. - Hopefully all the autobuilders can build PyX now. -- Graham Wilson Wed, 24 Sep 2003 01:54:06 +0000 pyx (0.4.1-3) unstable; urgency=low * Build depend on tetex-extra. -- Graham Wilson Tue, 23 Sep 2003 03:57:03 +0000 pyx (0.4.1-2) unstable; urgency=low * Set PYTHONPATH correctly when building manual. -- Graham Wilson Mon, 22 Sep 2003 18:17:16 +0000 pyx (0.4.1-1) unstable; urgency=low * Set encoding header in a couple of files to ISO-8859-1. * New upstream version. * Build the manual as PDF. Don't compress it. -- Graham Wilson Wed, 17 Sep 2003 18:35:07 +0000 pyx (0.4-1) unstable; urgency=low * Initial Debian release. (closes: #192100) -- Graham Wilson Thu, 11 Sep 2003 04:42:57 +0000 vim:ts=2:sw=2:et: debian/copyright0000644000000000000000000005246112063407731011134 0ustar Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: PyX Upstream-Contact: Jörg Lehmann Michael Schindler André Wobst Source: http://pyx.sourceforge.net/ Files: * Copyright: © 2002-2012, Jörg Lehmann © 2003-2012, Michael Schindler © 2002-2012, André Wobst License: GPL-2+ Files: pyx/data/afm/* Copyright: © 1985-1997, Adobe Systems Incorporated License: other Core 14 AFM Files - ReadMe This file and the 14 PostScript(R) AFM files it accompanies may be used, copied, and distributed for any purpose and without charge, with or without modification, provided that all copyright notices are retained; that the AFM files are not distributed without this file; that all modifications to this file or any of the AFM files are prominently noted in the modified file(s); and that this paragraph is not modified. Adobe Systems has no responsibility or obligation to support the use of the AFM files. Files: pyx/data/def/pyx.def Copyright: © 2003, 2006, Michael Schindler License: LPPL-1+ Comment: pyx.def is based on dvips.def which can be found at http://www.tug.org/texlive/svn/ or in the texlive-latex-base package. Files: debian/* Copyright: © 2003-2006, Graham Wilson © 2007, Thomas Viehmann © 2007, Ernesto Nadir Crespo Avila © 2009-2012 Stuart Prescott License: GPL-2+ License: GPL-2+ On Debian systems, the complete text of the GNU General Public License, can be found in /usr/share/common-licenses/GPL-2. License: LPPL-1+ The LaTeX Project Public License =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- . LPPL Version 1.3c 2008-05-04 . Copyright 1999 2002-2008 LaTeX3 Project Everyone is allowed to distribute verbatim copies of this license document, but modification of it is not allowed. . . PREAMBLE ======== . The LaTeX Project Public License (LPPL) is the primary license under which the LaTeX kernel and the base LaTeX packages are distributed. . You may use this license for any work of which you hold the copyright and which you wish to distribute. This license may be particularly suitable if your work is TeX-related (such as a LaTeX package), but it is written in such a way that you can use it even if your work is unrelated to TeX. . The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE', below, gives instructions, examples, and recommendations for authors who are considering distributing their works under this license. . This license gives conditions under which a work may be distributed and modified, as well as conditions under which modified versions of that work may be distributed. . We, the LaTeX3 Project, believe that the conditions below give you the freedom to make and distribute modified versions of your work that conform with whatever technical specifications you wish while maintaining the availability, integrity, and reliability of that work. If you do not see how to achieve your goal while meeting these conditions, then read the document `cfgguide.tex' and `modguide.tex' in the base LaTeX distribution for suggestions. . . DEFINITIONS =========== . In this license document the following terms are used: . `Work' Any work being distributed under this License. . `Derived Work' Any work that under any applicable law is derived from the Work. . `Modification' Any procedure that produces a Derived Work under any applicable law -- for example, the production of a file containing an original file associated with the Work or a significant portion of such a file, either verbatim or with modifications and/or translated into another language. . `Modify' To apply any procedure that produces a Derived Work under any applicable law. . `Distribution' Making copies of the Work available from one person to another, in whole or in part. Distribution includes (but is not limited to) making any electronic components of the Work accessible by file transfer protocols such as FTP or HTTP or by shared file systems such as Sun's Network File System (NFS). . `Compiled Work' A version of the Work that has been processed into a form where it is directly usable on a computer system. This processing may include using installation facilities provided by the Work, transformations of the Work, copying of components of the Work, or other activities. Note that modification of any installation facilities provided by the Work constitutes modification of the Work. . `Current Maintainer' A person or persons nominated as such within the Work. If there is no such explicit nomination then it is the `Copyright Holder' under any applicable law. . `Base Interpreter' A program or process that is normally needed for running or interpreting a part or the whole of the Work. . A Base Interpreter may depend on external components but these are not considered part of the Base Interpreter provided that each external component clearly identifies itself whenever it is used interactively. Unless explicitly specified when applying the license to the Work, the only applicable Base Interpreter is a `LaTeX-Format' or in the case of files belonging to the `LaTeX-format' a program implementing the `TeX language'. . . . CONDITIONS ON DISTRIBUTION AND MODIFICATION =========================================== . 1. Activities other than distribution and/or modification of the Work are not covered by this license; they are outside its scope. In particular, the act of running the Work is not restricted and no requirements are made concerning any offers of support for the Work. . 2. You may distribute a complete, unmodified copy of the Work as you received it. Distribution of only part of the Work is considered modification of the Work, and no right to distribute such a Derived Work may be assumed under the terms of this clause. . 3. You may distribute a Compiled Work that has been generated from a complete, unmodified copy of the Work as distributed under Clause 2 above, as long as that Compiled Work is distributed in such a way that the recipients may install the Compiled Work on their system exactly as it would have been installed if they generated a Compiled Work directly from the Work. . 4. If you are the Current Maintainer of the Work, you may, without restriction, modify the Work, thus creating a Derived Work. You may also distribute the Derived Work without restriction, including Compiled Works generated from the Derived Work. Derived Works distributed in this manner by the Current Maintainer are considered to be updated versions of the Work. . 5. If you are not the Current Maintainer of the Work, you may modify your copy of the Work, thus creating a Derived Work based on the Work, and compile this Derived Work, thus creating a Compiled Work based on the Derived Work. . 6. If you are not the Current Maintainer of the Work, you may distribute a Derived Work provided the following conditions are met for every component of the Work unless that component clearly states in the copyright notice that it is exempt from that condition. Only the Current Maintainer is allowed to add such statements of exemption to a component of the Work. . a. If a component of this Derived Work can be a direct replacement for a component of the Work when that component is used with the Base Interpreter, then, wherever this component of the Work identifies itself to the user when used interactively with that Base Interpreter, the replacement component of this Derived Work clearly and unambiguously identifies itself as a modified version of this component to the user when used interactively with that Base Interpreter. . b. Every component of the Derived Work contains prominent notices detailing the nature of the changes to that component, or a prominent reference to another file that is distributed as part of the Derived Work and that contains a complete and accurate log of the changes. . c. No information in the Derived Work implies that any persons, including (but not limited to) the authors of the original version of the Work, provide any support, including (but not limited to) the reporting and handling of errors, to recipients of the Derived Work unless those persons have stated explicitly that they do provide such support for the Derived Work. . d. You distribute at least one of the following with the Derived Work: . 1. A complete, unmodified copy of the Work; if your distribution of a modified component is made by offering access to copy the modified component from a designated place, then offering equivalent access to copy the Work from the same or some similar place meets this condition, even though third parties are not compelled to copy the Work along with the modified component; . 2. Information that is sufficient to obtain a complete, unmodified copy of the Work. . 7. If you are not the Current Maintainer of the Work, you may distribute a Compiled Work generated from a Derived Work, as long as the Derived Work is distributed to all recipients of the Compiled Work, and as long as the conditions of Clause 6, above, are met with regard to the Derived Work. . 8. The conditions above are not intended to prohibit, and hence do not apply to, the modification, by any method, of any component so that it becomes identical to an updated version of that component of the Work as it is distributed by the Current Maintainer under Clause 4, above. . 9. Distribution of the Work or any Derived Work in an alternative format, where the Work or that Derived Work (in whole or in part) is then produced by applying some process to that format, does not relax or nullify any sections of this license as they pertain to the results of applying that process. . 10. a. A Derived Work may be distributed under a different license provided that license itself honors the conditions listed in Clause 6 above, in regard to the Work, though it does not have to honor the rest of the conditions in this license. . b. If a Derived Work is distributed under a different license, that Derived Work must provide sufficient documentation as part of itself to allow each recipient of that Derived Work to honor the restrictions in Clause 6 above, concerning changes from the Work. . 11. This license places no restrictions on works that are unrelated to the Work, nor does this license place any restrictions on aggregating such works with the Work by any means. . 12. Nothing in this license is intended to, or may be used to, prevent complete compliance by all parties with all applicable laws. . . NO WARRANTY =========== . There is no warranty for the Work. Except when otherwise stated in writing, the Copyright Holder provides the Work `as is', without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the Work is with you. Should the Work prove defective, you assume the cost of all necessary servicing, repair, or correction. . In no event unless required by applicable law or agreed to in writing will The Copyright Holder, or any author named in the components of the Work, or any other party who may distribute and/or modify the Work as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of any use of the Work or out of inability to use the Work (including, but not limited to, loss of data, data being rendered inaccurate, or losses sustained by anyone as a result of any failure of the Work to operate with any other programs), even if the Copyright Holder or said author or said other party has been advised of the possibility of such damages. . . MAINTENANCE OF THE WORK ======================= . The Work has the status `author-maintained' if the Copyright Holder explicitly and prominently states near the primary copyright notice in the Work that the Work can only be maintained by the Copyright Holder or simply that it is `author-maintained'. . The Work has the status `maintained' if there is a Current Maintainer who has indicated in the Work that they are willing to receive error reports for the Work (for example, by supplying a valid e-mail address). It is not required for the Current Maintainer to acknowledge or act upon these error reports. . The Work changes from status `maintained' to `unmaintained' if there is no Current Maintainer, or the person stated to be Current Maintainer of the work cannot be reached through the indicated means of communication for a period of six months, and there are no other significant signs of active maintenance. . You can become the Current Maintainer of the Work by agreement with any existing Current Maintainer to take over this role. . If the Work is unmaintained, you can become the Current Maintainer of the Work through the following steps: . 1. Make a reasonable attempt to trace the Current Maintainer (and the Copyright Holder, if the two differ) through the means of an Internet or similar search. . 2. If this search is successful, then enquire whether the Work is still maintained. . a. If it is being maintained, then ask the Current Maintainer to update their communication data within one month. . b. If the search is unsuccessful or no action to resume active maintenance is taken by the Current Maintainer, then announce within the pertinent community your intention to take over maintenance. (If the Work is a LaTeX work, this could be done, for example, by posting to comp.text.tex.) . 3a. If the Current Maintainer is reachable and agrees to pass maintenance of the Work to you, then this takes effect immediately upon announcement. . b. If the Current Maintainer is not reachable and the Copyright Holder agrees that maintenance of the Work be passed to you, then this takes effect immediately upon announcement. . 4. If you make an `intention announcement' as described in 2b. above and after three months your intention is challenged neither by the Current Maintainer nor by the Copyright Holder nor by other people, then you may arrange for the Work to be changed so as to name you as the (new) Current Maintainer. . 5. If the previously unreachable Current Maintainer becomes reachable once more within three months of a change completed under the terms of 3b) or 4), then that Current Maintainer must become or remain the Current Maintainer upon request provided they then update their communication data within one month. . A change in the Current Maintainer does not, of itself, alter the fact that the Work is distributed under the LPPL license. . If you become the Current Maintainer of the Work, you should immediately provide, within the Work, a prominent and unambiguous statement of your status as Current Maintainer. You should also announce your new status to the same pertinent community as in 2b) above. . . WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE ====================================================== . This section contains important instructions, examples, and recommendations for authors who are considering distributing their works under this license. These authors are addressed as `you' in this section. . Choosing This License or Another License ---------------------------------------- . If for any part of your work you want or need to use *distribution* conditions that differ significantly from those in this license, then do not refer to this license anywhere in your work but, instead, distribute your work under a different license. You may use the text of this license as a model for your own license, but your license should not refer to the LPPL or otherwise give the impression that your work is distributed under the LPPL. . The document `modguide.tex' in the base LaTeX distribution explains the motivation behind the conditions of this license. It explains, for example, why distributing LaTeX under the GNU General Public License (GPL) was considered inappropriate. Even if your work is unrelated to LaTeX, the discussion in `modguide.tex' may still be relevant, and authors intending to distribute their works under any license are encouraged to read it. . A Recommendation on Modification Without Distribution ----------------------------------------------------- . It is wise never to modify a component of the Work, even for your own personal use, without also meeting the above conditions for distributing the modified component. While you might intend that such modifications will never be distributed, often this will happen by accident -- you may forget that you have modified that component; or it may not occur to you when allowing others to access the modified version that you are thus distributing it and violating the conditions of this license in ways that could have legal implications and, worse, cause problems for the community. It is therefore usually in your best interest to keep your copy of the Work identical with the public one. Many works provide ways to control the behavior of that work without altering any of its licensed components. . How to Use This License ----------------------- . To use this license, place in each of the components of your work both an explicit copyright notice including your name and the year the work was authored and/or last substantially modified. Include also a statement that the distribution and/or modification of that component is constrained by the conditions in this license. . Here is an example of such a notice and statement: . %% pig.dtx %% Copyright 2005 M. Y. Name % % This work may be distributed and/or modified under the % conditions of the LaTeX Project Public License, either version 1.3 % of this license or (at your option) any later version. % The latest version of this license is in % http://www.latex-project.org/lppl.txt % and version 1.3 or later is part of all distributions of LaTeX % version 2005/12/01 or later. % % This work has the LPPL maintenance status `maintained'. % % The Current Maintainer of this work is M. Y. Name. % % This work consists of the files pig.dtx and pig.ins % and the derived file pig.sty. . Given such a notice and statement in a file, the conditions given in this license document would apply, with the `Work' referring to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being generated from `pig.dtx' using `pig.ins'), the `Base Interpreter' referring to any `LaTeX-Format', and both `Copyright Holder' and `Current Maintainer' referring to the person `M. Y. Name'. . If you do not want the Maintenance section of LPPL to apply to your Work, change `maintained' above into `author-maintained'. However, we recommend that you use `maintained', as the Maintenance section was added in order to ensure that your Work remains useful to the community even when you can no longer maintain and support it yourself. . Derived Works That Are Not Replacements --------------------------------------- . Several clauses of the LPPL specify means to provide reliability and stability for the user community. They therefore concern themselves with the case that a Derived Work is intended to be used as a (compatible or incompatible) replacement of the original Work. If this is not the case (e.g., if a few lines of code are reused for a completely different task), then clauses 6b and 6d shall not apply. . . Important Recommendations ------------------------- . Defining What Constitutes the Work . The LPPL requires that distributions of the Work contain all the files of the Work. It is therefore important that you provide a way for the licensee to determine which files constitute the Work. This could, for example, be achieved by explicitly listing all the files of the Work near the copyright notice of each file or by using a line such as: . % This work consists of all files listed in manifest.txt. . in that place. In the absence of an unequivocal list it might be impossible for the licensee to determine what is considered by you to comprise the Work and, in such a case, the licensee would be entitled to make reasonable conjectures as to which files comprise the Work. debian/python-pyx.install0000644000000000000000000000003511565314465012725 0ustar usr/lib/python*/*-packages/* debian/control0000644000000000000000000000327212063410161010567 0ustar Source: pyx Maintainer: Stuart Prescott Standards-Version: 3.9.4 Section: python Priority: optional Build-Depends: debhelper (>= 9~), python-all-dev (>= 2.6.6-3~), libkpathsea-dev, python, texlive-latex-base Build-Depends-Indep: python-sphinx (>= 1.0.7+dfsg), libjs-mathjax, python-imaging, ghostscript, texlive-latex-extra, texlive-latex-recommended, texlive-fonts-recommended, tipa Homepage: http://pyx.sourceforge.net/ Package: python-pyx Architecture: any Depends: ${shlibs:Depends}, ${python:Depends}, ${misc:Depends} Recommends: texlive-latex-base Suggests: python-pyx-doc, python-imaging, texlive-fonts-recommended Provides: ${python:Provides} Description: Python module for generating PostScript graphics PyX is a Python module for generating encapsulated PostScript figures using an abstraction of PostScript and TeX. . The module provides access to PostScript features such as paths, line-styles, fill patterns, transformations, and clipping. Geometric operations on paths such as intersections, transformations, and splitting are also supported. . PyX also allows flexible graph generation with many different graph and axis styles. Package: python-pyx-doc Architecture: all Section: doc Depends: libjs-jquery, ${misc:Depends}, ${sphinxdoc:Depends} Recommends: pdf-viewer Description: Python module for generating PostScript graphics (documentation) PyX is a Python module for generating encapsulated PostScript figures using an abstraction of PostScript and TeX. . This package contains the manual for PyX in PDF and HTML formats and examples. debian/rules0000755000000000000000000000153012063625173010252 0ustar #!/usr/bin/make -f %: dh $@ --with python2 doc: make -C faq all make -C manual all override_dh_auto_clean: make -C faq clean make -C manual clean rm -rf manual/_build faq/_build cd pyx/data/lfs; rm -f *.lfs *.aux *.log dh_auto_clean override_dh_auto_build-indep: doc override_dh_auto_build-arch: cd pyx/data/lfs; python createlfs.py dh_auto_build override_dh_auto_install: dh_auto_install rm $(CURDIR)/debian/tmp/usr/lib/python2.*/*-packages/pyx/data/lfs/createlfs.* override_dh_installdocs-indep: mv manual/_build/html/ manual/_build/manual/ mv faq/_build/html/ faq/_build/faq/ dh_installdocs -Xobjects.inv dh_sphinxdoc override_dh_compress: dh_compress --all -X.pdf override_dh_fixperms: dh_fixperms find debian/python-pyx-doc/usr/share/doc/python-pyx-doc/examples/ \ -type f -print0 | \ xargs -0r chmod 0644 .PHONY: doc