1. 18 Mar, 2021 1 commit
    • Viacheslav Ostroukh's avatar
      require Python 3.7 · bde145b2
      Viacheslav Ostroukh authored
      Merge request !370 was supposed to make Python 3.7 minimal required version,
      but in some places 3.6 sneaked from attention. This commit fixes that.
      bde145b2
  2. 03 Mar, 2021 1 commit
  3. 22 Dec, 2020 2 commits
  4. 13 Apr, 2020 3 commits
  5. 10 Apr, 2020 1 commit
  6. 16 Mar, 2020 1 commit
    • Joseph Weston's avatar
      update libraries for linking against Mumps in conda-forge · 014df638
      Joseph Weston authored
      Recently conda-forge updated their packaging so that sequential
      Mumps is a separate package,
      [mumps-seq](https://anaconda.org/conda-forge/mumps-seq),
      which names the libraries with a suffix '_seq' (contrary to how
      Debian does it).
      In addition we no longer need to explicitly link against Scotch,
      pord or gfortran as the conda-forge built mumps libraries already
      do this.
      All tests still pass without explicitly linking against mpiseq,
      so it is left out.
      014df638
  7. 15 Dec, 2019 1 commit
  8. 13 Nov, 2019 1 commit
  9. 12 Nov, 2019 1 commit
  10. 21 Oct, 2019 1 commit
  11. 15 Feb, 2019 2 commits
  12. 06 Feb, 2019 1 commit
  13. 20 Dec, 2018 1 commit
  14. 01 Aug, 2018 1 commit
  15. 27 Feb, 2018 1 commit
  16. 26 Feb, 2018 1 commit
  17. 15 Nov, 2017 1 commit
    • Bas Nijholt's avatar
      add numpy includes later in the extension config · b9c2b0c2
      Bas Nijholt authored
      Previously, the numpy 'include_dirs' would be shadowed by
      any 'include_dirs' provided in 'build.conf'. We want to avoid
      burdening people with remembering to specify the numpy 'include_dirs'
      every time, and if custom numpy headers is the desired behaviour, these
      can still be specified in 'build.conf', and will take precedence.
      b9c2b0c2
  18. 26 Oct, 2017 1 commit
  19. 13 Sep, 2017 2 commits
  20. 12 Sep, 2017 1 commit
  21. 25 Jul, 2017 1 commit
    • Christoph Groth's avatar
      move tutorial script generation, reorganize doc/source · 9fdd41e8
      Christoph Groth authored
      I assume that most people encounter the tutorial example scripts by
      reading the documentation, and not by viewing the tutorial subdirectory
      of a checked-out Kwant source.
      
      That's the motivation for moving all the manipulations of tutorial
      scripts from setup.py to doc/Makefile.  Previously, a successful 'make
      html' would require a preceding execution of 'setup.py build_tut'.  Now,
      a simple 'make html' is enough.
      
      While at it, I reorganized where the example scripts and their outputs
      are stored.  Everything is now in 'doc/source/code' with its three
      subdirectories 'download' (to be shown to readers), 'include' (with
      include markers), and 'figure' (figure generation & figures).  This
      organization is clearer and also makes the generation of figures
      separate from the tutorial.
      9fdd41e8
  22. 20 Jul, 2017 1 commit
  23. 20 Jun, 2017 2 commits
  24. 19 Jun, 2017 1 commit
  25. 24 May, 2017 1 commit
  26. 23 May, 2017 1 commit
  27. 19 May, 2017 2 commits
  28. 11 May, 2017 1 commit
  29. 04 May, 2017 1 commit
  30. 25 Apr, 2017 1 commit
  31. 12 Apr, 2017 1 commit
    • Christoph Groth's avatar
      move ensure_python() from setup.py into Kwant and use it · 874b6c29
      Christoph Groth authored
      This allows to provide a helpful error message when someone tries to
      import Kwant with Python 2.
      
      Note that I moved the version code into a module of its own:
      kwant.version.  The rationale is to separate this code from unrelated
      stuff in kwant._common that requires various external libs.  The
      kwant.version module should work on its own without any third-party
      libraries.
      874b6c29
  32. 14 Mar, 2017 1 commit
    • Joseph Weston's avatar
      fix discretizer packaging and optional testing · 7cb76722
      Joseph Weston authored
      Previously the testing/importing 'continuum' would fail if sympy was not
      installed. Now we do the following:
      
          * add sympy as an optional dependency in 'extras_require'
          * force pytest to ignore tests in packages that have uninstalled
            dependencies by defining a hook in 'conftest.py'
          * use the 'class as a module' hack when importing 'continuum'.
            When sympy is not installed the continuum module will be replaced
            with an instance of 'ExtensionUnavailable' that will raise a runtime
            error on attribute access.
          * no warning is raised if sympy is not installed (it is an
            optional dependency).
      7cb76722
  33. 02 Feb, 2017 1 commit