1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
========================
How to install and test?
========================
How to install?
===============
Requirements
------------
* python **2.7** or python **3.3** or newer
* pyparsing **2.0.3** or newer
Package manager (recommended for those OS users)
------------------------------------------------
* `Archlinux <https://aur.archlinux.org/packages/python-bibtexparser/>`_
* `Debian <https://packages.debian.org/en/sid/main/python-bibtexparser>`_
pip (recommended to other users)
---------------------------------
To install with pip:
.. code-block:: sh
pip install bibtexparser
Manual installation (recommended for packagers)
-----------------------------------------------
Download the archive on `Pypi <http://pypi.python.org/pypi/bibtexparser/>`_.
.. code-block:: sh
python setup.py install
How to run the test suite?
==========================
This paragraph briefly describes how to run the test suite.
This is useful for contributors, for packagers but also for users who wants to check their environment.
Virtualenv
----------
You can make a virtualenv. I like `pew <https://pypi.python.org/pypi/pew/>`_ for that because the API is easier.
The first time, you need to make a virtualenv
.. code-block:: sh
pew mkproject bibtexparser
pip install -r requirements.txt
python setup.py install
nosetest
If you already have a virtualenv, you can use workon
.. code-block:: sh
pew workon bibtexparser
Tox
---
The advantage of `Tox <https://pypi.python.org/pypi/tox>`_ is that you can build and test the code against several versions of python.
Of course, you need tox to be installed on your system.
The configuration file is tox.ini, in the root of the project. There, you can change the python versions.
.. code-block:: sh
tox # and nothing more :)
|
