diff options
| author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2019-10-29 19:18:49 +0000 |
|---|---|---|
| committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2019-10-29 19:24:14 +0000 |
| commit | 3fc44bc6c34cf436a885d0e2ab4dc591d233d573 (patch) | |
| tree | fa551bec3a3aa6072554addcb6f06eb3a00448ed /.file-metadata | |
| parent | cd39335965eea96dc7fe9d5d115e74dcdaf5c8ba (diff) | |
lmfit and its dependencies added, Python tarballs as prerequisite
Python's `lmfit' module and all its major dependencies (`asteval',
`corner', `emcee' and `uncertainties') have been included in the template.
While doing this I noticed that if the tarballs are the last prerequisite
of each software building rule, then when building in parallel, the
template will immediately start building packages as soon as the first one
is downloaded. Not like the current way that it will attempt to download
several, then start building. For now, this has been implemented in the
Python build rules for all the modules and we'll later do the same for the
other programs and libraries. This also motivated a simplification of the
`pybuild' function: it now internally looks into the prerequisites and
selects the tarball from the prerequisite that is in the tarballs
directory.
This isn't a problem for the build, but I just don't understand why Python
can't recognize the version of `emcee', Python reads the version of `emcee'
as `0.0.0'! But it doesn't cause any crash in the build, so for now its
fine.
Diffstat (limited to '.file-metadata')
| -rw-r--r-- | .file-metadata | bin | 6572 -> 6651 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/.file-metadata b/.file-metadata Binary files differindex 69211e9..6a6b52c 100644 --- a/.file-metadata +++ b/.file-metadata |