Skip to content

testing submodules' master in .travis.yml #1145

@jGaboardi

Description

@jGaboardi

Problem

When using

pip install https://github.com/pysal/libpysal/archive/master.zip;

in the install section of .travis.yml only the current available release is tested, not the current master leading to something like:

Requirement already satisfied: libpysal>=4.0.0 in ./miniconda/envs/test-env/lib/python3.6/site-packages (from spreg==1.1.0) (4.1.1)

This appears to be true for any current master (libpysal, esda, mapclassify, etc.) desired to be tested against that is found in a requirements*.txt file and installed during the before_install stage (prior to the $PYSAL_PYPI install boolean being applied).

Solution

Using

git clone https://github.com/pysal/libpysal.git;
cd libpysal; pip install .; cd ../;

in place of the above (.../archive/master.zip) solves this problem resulting in the actual current master being installed:

Installing collected packages: libpysal
Found existing installation: libpysal 4.1.1
  Uninstalling libpysal-4.1.1:
    Successfully uninstalled libpysal-4.1.1
Successfully installed libpysal-4.1.1

(Seemingly) Affected Submodules

Related

Question

I can either take care of all these, or they can be left up to the respective lead maintainers. Just let me know.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions