The MagicMock trick I used to get the docs to build is causing the method call signatures in the built documentation to look wonky.

The ibei module depends on physicalproperty, but its build on travis-ci is failing because the 1.0.1 build of physicalproperty on binstar was build only for OSX. Therefore, the physicalproperty package should specify noarch since it is a pure python module.

The solution is to set noarch_python: True in meta.yaml.

The build of physicalproperty with python 2.6 fails. The failure occurs in build.sh:

VERSION=`python -c 'execfile("physicalproperty/version.py")

Even if the above code worked, the build would fail in setup.py as a result of the

execfile("physicalproperty/version.py")

line introduced to close #7.

Solution

It looks like the best practice is to use the with open... pattern to replace the execfile command as noted in this SO post.

The documentation doesn't have to be vast, but should be similar to what is written for ibei.

Release version 1.0.1. This issue closes when milestone 1.0.1 is reached.

Since this project is a python module, the versioning scheme should be PEP 440 compatible.

This note should occur in README.rst. It should mention that the easiest way to get set up with a numpy environment is to use the anaconda distribution.

Add the following to meta.yaml:

build:
    string: {{ environ.get('GIT_BUILD_STR', '') }}

In this way the commit hash (more or less) will be set as the conda build string and therefore I will be able to identify from which commit a particular conda build was produced.

Similar to issue 33 in ibei.

Since the package is at release 1.0.0 the development status should be "stable."

Closing tec issue 138 would be easier if find_PhysicalProperty was an iterator instead of just returning a list.

This method doesn't necessarily need to be refactored, another method could be written with this functionality.

Related issues:

• tec issue 138