| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since Intel's default openmp implementation is available in the same src
tarball, we can just include it in the package. This means that `mkl` now "just
works" without any environment variables, fragile setup-hooks, or forced
propagation.
Since the openmp implementation is only needed at runtime (and for test cases),
users can substitute a different one if they prefer by exporting it with
`LD_PRELOAD`, which is how Intel recommends handling this. If they do not do so,
`libiomp.so` lives next to `libmkl_rt.so` and thus will be in the RPATH as a
sane default.
Since this still comes from the same src tarball, we can ship it without losing
the fixed-output derivation; likewise, since Hydra is not building or caching
these, shipping these proprietary packages costs no bandwidth for the nix
community.
|
| |
|
|
| |
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|
| |\ |
|
| | |
| |
| |
| | |
The default for `python3` is currently `python36`.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Python 3.4 will receive it's final patch release in March 2019 and there won't
be any releases anymore after that, so also not during NixOS 2019.03.
Python 3.4 is not used anymore in Nixpkgs. In any case, migrating code from
3.4 to 3.4+ is trivial.
|
| |\|
| |
| |
| | |
Conflict: rename of pythondaemon -> python-daemon.
|
| | |
| |
| |
| |
| |
| | |
This commit renames the pythondaemon module to match its module name, github
name, and pypi name, which makes it easier to find and reference. In order to
avoid breaking any external users, I've left an alias with a deprecated warning.
|
| | |
| |
| |
| |
| | |
With Python 3.7 now at 3.7.1, and Python 3.6 at it's final maintenance
mode release, it is time to move on to 3.7 as the default interpreter.
|
| |/
|
|
| |
This adds support building with MKL.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This touches up a handful of places in the python documentation to try to make
the current best-practices more obvious. In particular, I often find the
function signatures (what to pass, what not to pass) confusing and have added
them to the docs.
Also updated the metas to be more consistent with the most frequently used
modern style.
|
| |
|
|
| |
https://github.com/NixOS/nixpkgs/pull/45822#issuecomment-417566642
|
| |
|
|
| |
cc @FRidh, @dotlambda
|
| |
|
|
|
| |
Clarify the issue encountered at
https://github.com/NixOS/nixpkgs/issues/45503
|
| | |
|
| |
|
|
|
|
| |
Use example package `zerobin` instead of `bepasty-server` which
is no longer part of python-packages.
This fixes the examples for current nixpkgs versions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Use the same approach like in the overlay example:
Override `python` instead of `pythonPackages` so that
`python.pkgs` refers to the new package set like `pythonPackages`.
This also fixes a bug in the original example where
`pkgs.fetchgit` was not in scope.
Add an extra example to illustrate how to override just a
package set.
2. Fix mix-up between `super` and `self` in the explanation text.
Also, simplify the explanation.
|
| |
|
|
| |
The `pythonPackages` definition is redundant
|
| | |
|
| |
|
| |
Using a recursive attribute set is not recommended.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Explain `toPythonApplication` and `toPythonModule` as well as some minor improvements.
|
| |
|
|
|
| |
Encountered one of these when using check-meta, did a quick
search to find other instances.
|
|
|
This makes a makefile-driven developer workflow nicer.
|