Fixed: dpkg needs the package to be installed already. |
|
More...
|
about 12 years ago
|
Attempting to locate the apt-get-installed Python 3. |
|
More...
|
about 12 years ago
|
NumPy not found by Python. A theory: the apt-get install… numpy installs *another* Python 3 than the one called with the "python" command. Trying to see where the python3 setup through apt-get is. |
|
More...
|
about 12 years ago
|
Investigating the "no NumPy" installed for Python 3 problem. |
|
More...
|
about 12 years ago
|
python3-numpy gets installed; "nose uncertainties" runs Python 3 but does not find NumPY. |
|
More...
|
about 12 years ago
|
Trying to find a simple way of installing NumPy for Python 3. |
|
More...
|
about 12 years ago
|
Of course, pip fetches the PyPI version and does not use the local version. Trying again the local setup.py, but this time without --user. |
|
More...
|
about 12 years ago
|
Fixed typo. Maybe that's why ruby was run instead of Python. |
|
More...
|
about 12 years ago
|
Travis CI ran "ruby", with the previous version. Trying to recover… |
|
More...
|
about 12 years ago
|
A "python setup.py install --user" install does not find the module with "nosetests uncertainties". |
|
More...
|
about 12 years ago
|
Yet another attempt at testing the Python 3 version when Python 3 is used by Travis (instead of testing the Python 2 version). |
|
More...
|
about 12 years ago
|
The Python version test is now in a different Travis section: hopefully this will solve the problem of it not being run, apparently. |
|
More...
|
about 12 years ago
|
Trying to fix the Python 3 test for running 2to3. |
|
More...
|
about 12 years ago
|
Trying to fix incorrect test syntax. |
|
More...
|
about 12 years ago
|
Attempt at having 2to3 run when Python 3+ is selected. |
|
More...
|
about 12 years ago
|
Trying Python 3, now that Python 2 works as expected. A difficulty is getting the Python 3 version built: how to do this depending on the Python version selected through the 'python:' entry? |
|
More...
|
about 12 years ago
|
Simpler wording. |
|
More...
|
about 12 years ago
|
pdflatex was found, but "! Font T1/cmr/m/n/10=ecrm1000 at 10.0pt not loadable: Metric (TFM) file not found." Trying to solve this. |
|
More...
|
about 12 years ago
|
More informed package choice (http://packages.debian.org/search?searchon=contents&keywords=pdflatex). |
|
More...
|
about 12 years ago
|
Trying yet another Debian package, with the hope of getting pdflatex. |
|
More...
|
about 12 years ago
|
Added Python version printing for making sure that the correct tests are run by Travis CI. |
|
More...
|
about 12 years ago
|
Confirmed: the "deactivate" command replaces the Python interpreter. Removed. |
|
More...
|
about 12 years ago
|
Experimenting with Travis (see comment). |
|
More...
|
about 12 years ago
|
Experimenting with Travis. Goal: make sure that the right nosetests is used (the one that corresponds to the Python version). |
|
More...
|
about 12 years ago
|
Trying yet another package for pdflatex. The previous packages were not found. |
|
More...
|
about 12 years ago
|
tetex-bin seems to be the Debian package that contains pdflatex (http://linux.derkeiler.com/Mailing-Lists/Debian/2006-09/msg00130.html): trying this. |
|
More...
|
about 12 years ago
|
pdflatex is hopefully in the texlive-latex package. |
|
More...
|
about 12 years ago
|
Putting NUMPY=true first, so that the most common configuration is tested first. |
|
More...
|
about 12 years ago
|
Removing explicit references to python3 and nosetests3 executables, as the python command runs python 3 when Python 3 is selected by the "python:" entry of the Travis configuration file. |
|
More...
|
about 12 years ago
|
Trying to have the Travis Continuous Integration system use setup.py so that Python 3 code is actually run (currently, the Python 2 code is run by Python 3). |
|
More...
|
about 12 years ago
|