File python-mathdom.spec of Package python-mathdom

Overview Repositories Revisions Requests Users Attributes Meta

File python-mathdom.spec of Package python-mathdom

#
# spec file for package python-mathdom
#
# Copyright (c) 2008 SUSE LINUX Products GmbH, Nuernberg, Germany.
# This file and all modifications and additions to the pristine
# package are under the same license as the package itself.
#
# Please submit bugfixes or comments via http://bugs.opensuse.org/

%define _name mathdom
%define version 0.8
%define unmangled_version 0.8
%define release 1

Summary:   MathDOM - Content MathML in Python
Name:      python-%{_name}
Version:   %{version}
Release:   %{release}
Source0:   %{_name}-%{unmangled_version}.tar.bz2
License:   MIT
Group:     Development/Libraries/Python
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot
#BuildArch:  noarch
Vendor:    Stefan Behnel <scoder@users.sourceforge.net>
Url:       http://mathdom.sourceforge.net/
BuildRequires:  bzip2 python-devel
Requires:  pyxml python-lxml python-parsing

%description
MathDOM - Content MathML in Python

MathDOM is a set of Python 2.4 modules (using PyXML_ or lxml_, and
pyparsing_) that import mathematical terms as a `Content MathML`_
DOM. It currently parses MathML and literal infix terms into a DOM
document and writes out MathML and literal infix/prefix/postfix/Python
terms. The DOM elements are enhanced by domain specific methods that
make using the DOM a little easier. Implementations based on PyXML and
lxml/libxml2 are available.

_lxml:                  http://codespeak.net/lxml/
 _pyparsing:             http://pyparsing.sourceforge.net/
 _PyXML:                 http://pyxml.sourceforge.net/
 _`Content MathML`:      http://www.w3.org/TR/MathML2/chapter4.html
 _MathML:                http://www.w3.org/TR/MathML2/
 _PyMathML:              http://pymathml.sourceforge.net/

You can call it the shortest way between different term
representations and a Content MathML DOM. Ever noticed the annoying
differences between terms in different programming languages? Build
your application around the DOM and stop caring about the term
representation that users prefer or that your machine can execute. If
you need a different representation, add a converter, but don't change
the model of your application. Literal terms are connected through an
intermediate AST step that makes writing converters for
SQL/Java/Lisp/*your-favourite* easy.

%prep
%setup -q -n %{_name}-%{unmangled_version}

%build
%{__python} setup.py build

%install
%{__python} setup.py install \
      --root=$RPM_BUILD_ROOT \
      --prefix=%{_prefix} \
      --record-rpm=INSTALLED_FILES

%clean
%{__rm} -rf $RPM_BUILD_ROOT

%files -f INSTALLED_FILES
%defattr(-,root,root)
%doc examples html

%changelog

Places

File python-mathdom.spec of Package python-mathdom

Places