From 3fc44bc6c34cf436a885d0e2ab4dc591d233d573 Mon Sep 17 00:00:00 2001 From: Mohammad Akhlaghi Date: Tue, 29 Oct 2019 19:18:49 +0000 Subject: 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. --- .file-metadata | Bin 6572 -> 6651 bytes 1 file changed, 0 insertions(+), 0 deletions(-) (limited to '.file-metadata') diff --git a/.file-metadata b/.file-metadata index 69211e9..6a6b52c 100644 Binary files a/.file-metadata and b/.file-metadata differ -- cgit v1.2.1