Commit 1fb0017a authored by dugupeiwen's avatar dugupeiwen
Browse files

init 0.58

parents
# configuration file used by run_coverage.py
[run]
branch = True
source = numba
concurrency = multiprocessing
parallel = True
[report]
omit =
*/__main__.py
# Vendored packages
numba/misc/appdirs.py
numba/cloudpickle/__init__.py
numba/cloudpickle/cloudpickle.py
numba/cloudpickle/cloudpickle_fast.py
numba/cloudpickle/compat.py
numba/_version.py
exclude_lines =
pragma: no cover
if __name__ == .__main__.:
[html]
[flake8]
ignore =
# Extra space in brackets
E20,
# Multiple spaces around ","
E231,E241,
# Comments
E26,
# Assigning lambda expression
E731,
# Ambiguous variable names
E741,
# line break before binary operator
W503,
# line break after binary operator
W504,
max-line-length = 80
exclude =
__pycache__
.git
*.pyc
*~
*.o
*.so
*.cpp
*.c
*.h
__init__.py
# Ignore vendored files
numba/cloudpickle/*
versioneer.py
# Grandfather in existing failing files. This list should shrink over time
numba/stencils/stencil.py
numba/core/transforms.py
numba/core/tracing.py
numba/core/withcontexts.py
numba/_version.py
numba/core/ir_utils.py
numba/core/pylowering.py
numba/python_utils.py
numba/parfors/parfor.py
numba/misc/numba_entry.py
numba/stencils/stencilparfor.py
numba/core/ir.py
numba/core/generators.py
numba/misc/appdirs.py
numba/core/caching.py
numba/core/debuginfo.py
numba/core/annotations/pretty_annotate.py
numba/misc/dummyarray.py
numba/core/dataflow.py
numba/core/pythonapi.py
numba/core/decorators.py
numba/core/typeconv/rules.py
numba/core/typeconv/castgraph.py
numba/core/rewrites/registry.py
numba/core/rewrites/macros.py
numba/core/rewrites/static_binop.py
numba/core/rewrites/ir_print.py
numba/core/types/abstract.py
numba/core/types/misc.py
numba/core/types/npytypes.py
numba/core/types/common.py
numba/core/types/iterators.py
numba/core/types/scalars.py
numba/core/fastmathpass.py
numba/cpython/setobj.py
numba/core/options.py
numba/cpython/printimpl.py
numba/cpython/cmathimpl.py
numba/cpython/tupleobj.py
numba/cpython/mathimpl.py
numba/core/registry.py
numba/core/imputils.py
numba/cpython/builtins.py
numba/misc/quicksort.py
numba/cpython/randomimpl.py
numba/np/npyimpl.py
numba/cpython/slicing.py
numba/cpython/numbers.py
numba/cpython/listobj.py
numba/core/removerefctpass.py
numba/core/boxing.py
numba/misc/cffiimpl.py
numba/np/linalg.py
numba/cpython/rangeobj.py
numba/np/npyfuncs.py
numba/cpython/iterators.py
numba/core/codegen.py
numba/np/polynomial.py
numba/misc/mergesort.py
numba/core/base.py
numba/np/npdatetime.py
numba/pycc/cc.py
numba/pycc/compiler.py
numba/pycc/llvm_types.py
numba/pycc/platform.py
numba/pycc/decorators.py
numba/core/runtime/nrtdynmod.py
numba/core/runtime/context.py
numba/tests/test_support.py
numba/tests/test_llvm_version_check.py
numba/tests/test_builtins.py
numba/tests/test_jitmethod.py
numba/tests/test_inlining.py
numba/tests/test_array_manipulation.py
numba/tests/test_dummyarray.py
numba/tests/test_smart_array.py
numba/tests/test_linalg.py
numba/tests/test_threadsafety.py
numba/tests/test_utils.py
numba/tests/cfunc_cache_usecases.py
numba/tests/enum_usecases.py
numba/tests/test_func_lifetime.py
numba/tests/test_typeinfer.py
numba/tests/test_return_values.py
numba/tests/test_npdatetime.py
numba/tests/test_fancy_indexing.py
numba/tests/support.py
numba/tests/test_print.py
numba/tests/test_debug.py
numba/tests/test_interproc.py
numba/tests/test_typeconv.py
numba/tests/test_tracing.py
numba/tests/usecases.py
numba/tests/test_vectorization_type_inference.py
numba/tests/matmul_usecase.py
numba/tests/complex_usecases.py
numba/tests/test_array_exprs.py
numba/tests/test_polynomial.py
numba/tests/test_wrapper.py
numba/tests/test_obj_lifetime.py
numba/tests/test_intwidth.py
numba/tests/test_remove_dead.py
numba/tests/serialize_usecases.py
numba/tests/test_del.py
numba/tests/test_gil.py
numba/tests/cffi_usecases.py
numba/tests/test_slices.py
numba/tests/test_mandelbrot.py
numba/tests/compile_with_pycc.py
numba/tests/test_looplifting.py
numba/tests/test_storeslice.py
numba/tests/recursion_usecases.py
numba/tests/dummy_module.py
numba/tests/test_operators.py
numba/tests/test_comprehension.py
numba/tests/ctypes_usecases.py
numba/tests/test_locals.py
numba/tests/test_dicts.py
numba/tests/test_optional.py
numba/tests/test_mathlib.py
numba/tests/test_numberctor.py
numba/tests/test_globals.py
numba/tests/test_typingerror.py
numba/tests/test_copy_propagate.py
numba/tests/test_ctypes.py
numba/tests/test_typeof.py
numba/tests/test_usecases.py
numba/tests/test_auto_constants.py
numba/tests/test_cffi.py
numba/tests/test_sort.py
numba/tests/test_cfunc.py
numba/tests/test_conversion.py
numba/tests/test_indexing.py
numba/tests/test_pycc.py
numba/tests/annotation_usecases.py
numba/tests/test_alignment.py
numba/tests/test_multi3.py
numba/tests/test_overlap.py
numba/tests/test_array_attr.py
numba/tests/test_array_methods.py
numba/tests/test_enums.py
numba/tests/test_profiler.py
numba/tests/test_numpyadapt.py
numba/tests/cache_usecases.py
numba/tests/true_div_usecase.py
numba/tests/test_dataflow.py
numba/tests/test_tuples.py
numba/tests/test_svml.py
numba/tests/test_array_iterators.py
numba/tests/test_buffer_protocol.py
numba/tests/test_casting.py
numba/tests/test_lists.py
numba/tests/test_array_analysis.py
numba/tests/test_serialize.py
numba/tests/test_iteration.py
numba/tests/test_recarray_usecases.py
numba/tests/test_target_overloadselector.py
numba/tests/test_compile_cache.py
numba/tests/test_array_reductions.py
numba/tests/test_dyn_func.py
numba/tests/test_unpack_sequence.py
numba/tests/test_cgutils.py
numba/tests/test_complex.py
numba/tests/test_hashing.py
numba/tests/test_sys_stdin_assignment.py
numba/tests/pdlike_usecase.py
numba/tests/test_range.py
numba/tests/test_nrt_refct.py
numba/misc/timsort.py
numba/tests/test_nested_calls.py
numba/tests/test_chained_assign.py
numba/tests/test_withlifting.py
numba/tests/test_parfors.py
numba/tests/test_sets.py
numba/tests/test_dyn_array.py
numba/tests/test_objects.py
numba/tests/test_random.py
numba/tests/test_nan.py
numba/tests/pycc_distutils_usecase/source_module.py
numba/tests/npyufunc/test_ufuncbuilding.py
numba/tests/npyufunc/test_errors.py
numba/tests/npyufunc/test_vectorize_decor.py
numba/tests/npyufunc/test_parallel_ufunc_issues.py
numba/tests/npyufunc/test_parallel_env_variable.py
numba/tests/npyufunc/test_gufunc.py
numba/core/typing/cmathdecl.py
numba/core/typing/bufproto.py
numba/core/typing/mathdecl.py
numba/core/typing/listdecl.py
numba/core/typing/builtins.py
numba/core/typing/randomdecl.py
numba/core/typing/setdecl.py
numba/core/typing/npydecl.py
numba/core/typing/arraydecl.py
numba/core/typing/collections.py
numba/core/typing/ctypes_utils.py
numba/core/typing/enumdecl.py
numba/core/typing/cffi_utils.py
numba/core/typing/npdatetime.py
numba/core/annotations/type_annotations.py
numba/testing/ddt.py
numba/testing/loader.py
numba/testing/notebook.py
numba/testing/main.py
numba/np/unsafe/ndarray.py
numba/np/ufunc/deviceufunc.py
numba/np/ufunc/sigparse.py
numba/parfors/parfor_lowering.py
numba/np/ufunc/array_exprs.py
numba/np/ufunc/decorators.py
numba/core/datamodel/models.py
numba/core/datamodel/packer.py
numba/core/datamodel/testing.py
numba/core/datamodel/manager.py
per-file-ignores =
# Ignore star imports, unused imports, and "may be defined by star imports"
# errors in device_init because its purpose is to bring together a lot of
# the public API to be star-imported in numba.cuda.__init__
numba/cuda/device_init.py:F401,F403,F405
# libdevice.py is an autogenerated file containing stubs for all the device
# functions. Some of the lines in docstrings are a little over-long, as they
# contain the URLs of the reference pages in the online libdevice
# documentation.
numba/cuda/libdevice.py:E501
# Ignore too-long lines in the doc examples, prioritising readability
# in the docs over line length in the example source (especially given that
# the test code is already indented by 8 spaces)
numba/cuda/tests/doc_examples/test_random.py:E501
numba/cuda/tests/doc_examples/test_cg.py:E501
numba/cuda/tests/doc_examples/test_matmul.py:E501
numba/tests/doc_examples/test_interval_example.py:E501
numba/_version.py export-subst
# Numba's codeowners file is dual purpose, it:
#
# 1. Provides information to github about who should be requested to review a PR
# 2. Provides contributors/czars general information about who to contact
# first about various parts of the code base. A lot of concepts in Numba are
# necessarily spread throughout the code base, consequently some of the
# "code ownership"/first contact is concept based opposed to file/directory
# based.
#
# ------------------------------------------------------------------------------
# Information for github
# ------------------------------------------------------------------------------
# Owners of specific parts of the code, will be requested to review if a PR
# touches code in the matched pattern
/numba/cuda/ @gmarkall
/numba/parfors/ @DrTodd13
/numba/stencils/ @DrTodd13
/numba/core/byteflow.py @sklam
/numba/core/typeinfer.py @sklam
/numba/core/interpreter.py @sklam
# ------------------------------------------------------------------------------
# Information for contributors
# ------------------------------------------------------------------------------
# This section provides a rough list of who to contact first for help with
# various parts/concepts in the code base, first contact does not imply
# ownership!
#
# Parts of the code base:
#
# * Parfors/Parallel Accelerator (@DrTodd13)
# - Array Analysis (@DrTodd13)
# - Parfors transforms (@DrTodd13)
# * Stencils (@DrTodd13)
# * Experimental:
# - Jitclasses (@sklam)
# - StructRef (@sklam)
# * Typed containers:
# - Typed.List (@esc)
# - Typed.Dict (@sklam)
# * Documentation (Needs first contact/owner)
# * NumPy (Needs first contact/owner)
# - ufuncs (Needs first contact/owner)
# - linalg (@stuartarchibald)
# - Implementation of specific functions (Needs first contact/owner)
# - Parallel backends/threading layers (@stuartarchibald)
# * CPython implementation (Needs first contact/owner)
# * Extension API (Needs first contact/owner)
# * AOT (Needs first contact/owner)
# * Compiler:
# - Type inference (@sklam)
# - Bytecode analysis/CFA/DFA (@sklam)
# - Compiler Pipeline infrastructure (@stuartarchibald)
# - Compiler passes:
# - Rewrites (Needs first contact/owner)
# - Branch pruning (@stuartarchibald)
# - Literal unroll (@stuartarchibald)
# - Rewrite Semantic Constants (@stuartarchibald)
# - MakeFunction To Jit function (@stuartarchibald)
# - Overload and function inlining (@stuartarchibald)
# - With Lifting (@sklam)
# - Exception handling (@sklam)
# - Literally (@sklam)
# - SSA (@sklam)
# - lowering.py, codegen.py (@sklam)
# - Datamodels/call conventions (@sklam)
# - Inlining in general (@stuartarchibald)
#
# Additional Concepts:
#
# * Reference counting and NRT (@sklam)
# * Testing (Needs first contact/owner)
# * CI:
# - public CI (azure) (Needs first contact/owner)
# - Numba build farm (@esc)
# * Integration testing (https://github.com/numba/numba-integration-testing)
# (@esc)
# * ASV profiling (@esc)
# * Type Annotations (@luk-f-a and @EPronovost)
# * Ufunc/GUfunc (Needs first contact/owner)
# * Profiling (Needs first contact/owner (and code!))
# * Debugging:
# - DWARF (@sklam)
# - gdb support (@stuartarchibald)
# * Hardware targets:
# - The CUDA target (@gmarkall)
# - The ROCm target (@stuartarchibald)
# - ARM* (@stuartarchibald)
# - POWER (Needs first contact/owner)
# - X86* (Needs first contact/owner)
# * OS:
# - Linux (@stuartarchibald)
# - OSX
# - Windows
# - BSD (@stuartarchibald)
#
# Anything not covered by someone else... ping @sklam and @stuartarchibald
---
name: Bug Report
about: Report a bug. Not for asking general questions - see below.
---
<!--
Thanks for opening an issue! To help the Numba team handle your information
efficiently, please first ensure that there is no other issue present that
already describes the issue you have
(search at https://github.com/numba/numba/issues?&q=is%3Aissue).
-->
## Reporting a bug
<!--
Before submitting a bug report please ensure that you can check off these boxes:
-->
- [ ] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
- [ ] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.
<!--
Please include details of the bug here, including, if applicable, what you
expected to happen!
-->
---
name: Feature Request
about: Tell us about something in the Python language/NumPy you'd like Numba to support. Not for asking general questions - see below.
---
<!--
Thanks for opening an issue! To help the Numba team handle your information
efficiently, please first ensure that there is no other issue present that
already describes the issue you have
(search at https://github.com/numba/numba/issues?&q=is%3Aissue).
-->
## Feature request
<!--
Please include details of the feature you would like to see, why you would
like to see it/the use case.
-->
blank_issues_enabled: false
contact_links:
- name: General Question
url: https://numba.discourse.group/c/numba/community-support/
about: "If you have a general question (not a bug report or feature request) then please ask on Numba's discourse instance."
- name: Quick Question/Just want to say Hi!
url: https://gitter.im/numba/numba
about: "If you have a quick question or want chat to users/developers in real time then please use gitter.im/numba/numba"
- name: Discuss an involved feature
url: https://numba.discourse.group/c/numba/development/
about: "If you would like to suggest a more involved feature like *Can a new compiler pass be added to do X* then please start a discussion on Numba's discourse instance."
---
name: First Release Candidate Checklist (maintainer only)
about: Checklist template for the first release of every series
title: Numba X.Y.Zrc1 Checklist (FIXME)
labels: task
---
## Numba X.Y.Z
* [ ] Merge to main.
- [ ] "remaining Pull-Requests from milestone".
* [ ] Check Numba's version support table documentation. Update via PR if
needed.
* [ ] Review deprecation schedule and notices. Make PRs if need be.
* [ ] Merge change log changes.
- [ ] "PR with changelog entries".
* [ ] Create X.Y release branch.
* [ ] Create PR against the release branch to make `numba/testing/main.py`
to refer to `origin/releaseX.Y` instead of `origin/main`.
* [ ] Dependency version pinning on release branch
* [ ] Pin llvmlite to `0.A.*`.
* [ ] Pin NumPy if needed
* [ ] Pin TBB if needed
* [ ] Run the HEAD of the release branch through the build farm and confirm:
* [ ] Build farm CPU testing has passed.
* [ ] Build farm CUDA testing has passed.
* [ ] Build farm wheel testing has passed.
* [ ] Annotated tag `X.Y.Zrc1` on release branch (no `v` prefix).
* [ ] Build and upload conda packages on buildfarm (check "upload").
* [ ] Build wheels and sdist on the buildfarm (check "upload").
* [ ] Verify packages uploaded to Anaconda Cloud and move to `numba/label/main`.
* [ ] Upload wheels and sdist to PyPI (upload from `ci_artifacts`).
* [ ] Verify wheels for all platforms arrived on PyPi.
* [ ] Initialize and verify ReadTheDocs build.
* [ ] Post announcement to discourse group and ping the release testers group
using `@RC_Testers`.
* [ ] Post link to Twitter.
### Post Release:
* [ ] Clean up `ci_artifacts` by moving files to sub-directories
* [ ] Tag `X.Y+1.0dev0` to start new development cycle on `main`.
* [ ] Update llvmlite dependency via PR to `main`, PR includes version updates
to:
* [ ] `setup.py`
* [ ] `numba/__init__.py`
* [ ] `docs/environment.yml`
* [ ] `buildscripts/incremental/setup_conda_environment.sh`
* [ ] `buildscripts/incremental/setup_conda_environment.cmd`
* [ ] `buildscripts/condarecipe.local/meta.yaml`
* [ ] Update release checklist template with any additional bullet points that
may have arisen during the release.
* [ ] Close milestone (and then close this release issue).
---
name: Subsequent Release Candidate Checklist (maintainer only)
about: Checklist template for all subsequent releases (RC 2-N, FINAL and PATCH) of every series
title: Numba X.Y.Zrc1 Checklist (FIXME)
labels: task
---
## numba X.Y.Z
* [ ] Cherry-pick items from the X.Y.Z milestone into a cherry-pick PR.
* [ ] Update the "version support table" in the documentation with the final
release date (FINAL ONLY) and add to cherry-pick PR
* [ ] Update `CHANGE_LOG` on cherry-pick PR
* [ ] Check if any dependency pinnings need an update (e.g. NumPy)
* [ ] Approve cherry-pick PR
* [ ] Merge cherry-pick PR to X.Y release branch.
* [ ] https://github.com/numba/numba/pull/XXXX
* [ ] Review, merge and check execution of release notebook. (FINAL ONLY)
* [ ] Run the HEAD of the release branch through the build farm and confirm:
* [ ] Build farm CPU testing has passed.
* [ ] Build farm CUDA testing has passed
* [ ] Build farm wheel testing has passed
* [ ] Annotated tag X.Y.Z on release branch (no `v` prefix).
`git tag -am "Version X.Y.Z" X.Y.Z
* [ ] Build and upload conda packages on buildfarm (check `upload`).
* [ ] Build wheels and sdist on the buildfarm (check "upload").
* [ ] Verify packages uploaded to Anaconda Cloud and move to
`numba/label/main`.
* [ ] Upload wheels and sdist to PyPI (upload from `ci_artifacts`).
* [ ] Verify wheels for all platforms arrived on PyPi.
* [ ] Verify ReadTheDocs build.
* [ ] Post link to Twitter.
* [ ] Post announcement to discourse group and ping the release testers group
using `@RC_Testers` (RC ONLY).
* [ ] Post link to python-announce-list@python.org.
### Post release
* [ ] Cherry-pick change-log and version support table modifications to `main`
* [ ] Snapshot Build Farm config
* [ ] Clean up `ci_artifacts` by moving files to subdirectories
* [ ] Update release checklist template with any additional bullet points that
may have arisen during the release.
* [ ] Ping Anaconda Distro team to trigger a build for `defaults` (FINAL ONLY).
* [ ] Create a release on Github at https://github.com/numba/numba/releases (FINAL ONLY).
* [ ] Close milestone (and then close this release issue).
<!--
Thanks for wanting to contribute to Numba :)
First, if you need some help or want to chat to the core developers, please
visit https://gitter.im/numba/numba for real time chat or post to the Numba
forum https://numba.discourse.group/.
Here's some guidelines to help the review process go smoothly.
0. Please write a description in this text box of the changes that are being
made.
1. Please ensure that you have written units tests for the changes made/features
added.
2. If you are closing an issue please use one of the automatic closing words as
noted here: https://help.github.com/articles/closing-issues-using-keywords/
3. If your pull request is not ready for review but you want to make use of the
continuous integration testing facilities here, please click the arrow besides
"Create Pull Request" and choose "Create Draft Pull Request".
When it's ready for review, you can click the button "ready to review" near
the end of the pull request
(besides "This pull request is still a work in progress".)
The maintainers will then be automatically notified to review it.
4. Once review has taken place please do not add features or make changes out of
the scope of those requested by the reviewer (doing this just add delays as
already reviewed code ends up having to be re-reviewed/it is hard to tell
what is new etc!). Further, please do not rebase your branch on main/force
push/rewrite history, doing any of these causes the context of any comments
made by reviewers to be lost. If conflicts occur against main they should
be resolved by merging main into the branch used for making the pull
request.
Many thanks in advance for your cooperation!
-->
name: 'Mark stale issues'
on:
schedule:
- cron: '30 1 * * *'
permissions:
contents: read
jobs:
stale:
permissions:
issues: write # for actions/stale to close stale issues
pull-requests: write # for actions/stale to close stale PRs
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v7
with:
# issues
stale-issue-message: >
This issue is marked as stale as it has had no activity in the past
30 days. Please close this issue if no further response or action is
needed. Otherwise, please respond with any updates and confirm that
this issue still needs to be addressed.
stale-issue-label: 'stale'
any-of-issue-labels: 'question,needtriage,more info needed'
days-before-issue-stale: 30
days-before-issue-close: 7
# pull requests
stale-pr-message: >
This pull request is marked as stale as it has had no activity in
the past 3 months. Please respond to this comment if you're still
interested in working on this. Many thanks!
days-before-pr-stale: 90 # 3 months
days-before-pr-close: 7
any-of-pr-labels: '2 - In progress,4 - Waiting on author'
stale-pr-label: 'stale'
close-pr-label: 'abandoned - stale'
name: Check Release Notes
on:
pull_request: {}
jobs:
check:
name: Check release notes
if: ${{ !contains(github.event.pull_request.labels.*.name, 'skip_release_notes') }}
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
fetch-depth: 0
- name: Set up Python 3.9
uses: actions/setup-python@v4
with:
python-version: 3.9
- name: Install towncrier
run: |
python3 -m pip install towncrier==23.6 "importlib_resources<6"
- name: Run towncrier
run: |
git fetch --no-tags origin +refs/heads/${BASE_BRANCH}:refs/remotes/origin/${BASE_BRANCH}
towncrier check --compare-with remotes/origin/${BASE_BRANCH}
env:
BASE_BRANCH: ${{ github.base_ref }}
*.pyc
*.o
*.so
*.dylib
*.pyd
*.pdb
*.egg-info
*.sw[po]
*.out
*.ll
.coverage
.nfs*
tags
MANIFEST
build/
docs/_build/
docs/gh-pages/
dist/
htmlcov/
.idea/
.vscode/
.ycm_extra_conf.py
.mypy_cache/
.ipynb_checkpoints/
__pycache__/
docs/source/developer/autogen*
repos:
- repo: https://github.com/PyCQA/flake8
rev: 3.7.8
hooks:
- id: flake8
version: 2
build:
os: ubuntu-20.04
tools:
python: mambaforge-4.10
sphinx:
configuration: docs/source/conf.py
python:
install:
- method: setuptools
path: .
conda:
environment: docs/environment.yml
formats:
- pdf
The contents of this file has been removed. The change log can now be found at:
docs/source/release/*
and:
docs/source/release-notes.rst
We welcome people who want to make contributions to Numba, big or small!
Even simple documentation improvements are encouraged.
# Asking questions
Numba has a [discourse forum](https://numba.discourse.group/) for longer/more
involved questions and an IRC channel on
[gitter.im](https://gitter.im/numba/numba) for quick questions and interactive
help.
# Ways to help:
There's lots of ways to help improve Numba, some of these require creating code
changes, see **contributing patches** below.
## Quick things:
* Answer a question asked on [discourse](https://numba.discourse.group/) or
[gitter.im](https://gitter.im/numba/numba).
* Review a page of documentation, check it makes sense, that it's clear and
still relevant, that the examples are present, good and working. Fix anything
that needs updating in a pull request.
## More involved things:
* Review a pull request, you don't need to be a compiler engineer to do an
initial review of a pull request. It's incredibly helpful to have pull
requests go through a review to just make sure the code change is well formed,
documented, efficient and clear. Further, if the code is fixing a bug, making
sure that tests are present demonstrating it is fixed! Look out for PRs with
the [`needs initial review`](https://github.com/numba/numba/labels/needs%20initial%20review)
label. There are also time boxed tasks available on the
[contributor self-service board](https://github.com/orgs/numba/projects/7).
* Work on fixing or implementing something in the code base, there are a lot of
[`good first issue's`](https://github.com/numba/numba/labels/good%20first%20issue)
and [`good second issue's`](https://github.com/numba/numba/labels/good%20first%20issue).
For implementing new features/functionality, the extension API is the best
thing to use and a guide to using `@overload` in particular is
[here](https://numba.readthedocs.io/en/latest/extending/overloading-guide.html)
and the API documentation is [here](https://numba.readthedocs.io/en/latest/extending/high-level.html#implementing-functions).
## Contributing patches
Please fork the Numba repository on Github, and create a new branch
containing your work. When you are done, open a pull request.
# Further reading
Please read the [contributing guide](
https://numba.readthedocs.io/en/latest/developer/contributing.html).
Copyright (c) 2012, Anaconda, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The Numba source tree includes vendored libraries governed by the following
licenses.
appdirs
-------
# This is the MIT license
Copyright (c) 2010 ActiveState Software Inc.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
NetworkX
--------
The dominance frontier algorithm is from a pull request
https://github.com/numba/numba/pull/4149/files which is based
on the implementation of NetworkX of dominance. NetworkX has the following
license:
NetworkX is distributed with the 3-clause BSD license.
::
Copyright (C) 2004-2019, NetworkX Developers
Aric Hagberg <hagberg@lanl.gov>
Dan Schult <dschult@colgate.edu>
Pieter Swart <swart@lanl.gov>
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided
with the distribution.
* Neither the name of the NetworkX Developers nor the names of its
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
jquery.graphviz.svg (https://github.com/mountainstorm/jquery.graphviz.svg/)
---------------------------------------------------------------------------
The DAG roadmap rendering code in docs/dagmap/ uses Javascript from this
package to draw graphs in HTML.
Copyright (c) 2015 Mountainstorm
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
CPython (https://github.com/python/cpython)
-------------------------------------------
Numba source code that references URLs starting with:
https://github.com/python/cpython/
relates to use/inclusion of CPython source code which has the following license:
A. HISTORY OF THE SOFTWARE
==========================
Python was created in the early 1990s by Guido van Rossum at Stichting
Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands
as a successor of a language called ABC. Guido remains Python's
principal author, although it includes many contributions from others.
In 1995, Guido continued his work on Python at the Corporation for
National Research Initiatives (CNRI, see http://www.cnri.reston.va.us)
in Reston, Virginia where he released several versions of the
software.
In May 2000, Guido and the Python core development team moved to
BeOpen.com to form the BeOpen PythonLabs team. In October of the same
year, the PythonLabs team moved to Digital Creations, which became
Zope Corporation. In 2001, the Python Software Foundation (PSF, see
https://www.python.org/psf/) was formed, a non-profit organization
created specifically to own Python-related Intellectual Property.
Zope Corporation was a sponsoring member of the PSF.
All Python releases are Open Source (see http://www.opensource.org for
the Open Source Definition). Historically, most, but not all, Python
releases have also been GPL-compatible; the table below summarizes
the various releases.
Release Derived Year Owner GPL-
from compatible? (1)
0.9.0 thru 1.2 1991-1995 CWI yes
1.3 thru 1.5.2 1.2 1995-1999 CNRI yes
1.6 1.5.2 2000 CNRI no
2.0 1.6 2000 BeOpen.com no
1.6.1 1.6 2001 CNRI yes (2)
2.1 2.0+1.6.1 2001 PSF no
2.0.1 2.0+1.6.1 2001 PSF yes
2.1.1 2.1+2.0.1 2001 PSF yes
2.1.2 2.1.1 2002 PSF yes
2.1.3 2.1.2 2002 PSF yes
2.2 and above 2.1.1 2001-now PSF yes
Footnotes:
(1) GPL-compatible doesn't mean that we're distributing Python under
the GPL. All Python licenses, unlike the GPL, let you distribute
a modified version without making your changes open source. The
GPL-compatible licenses make it possible to combine Python with
other software that is released under the GPL; the others don't.
(2) According to Richard Stallman, 1.6.1 is not GPL-compatible,
because its license has a choice of law clause. According to
CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1
is "not incompatible" with the GPL.
Thanks to the many outside volunteers who have worked under Guido's
direction to make these releases possible.
B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON
===============================================================
PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
--------------------------------------------
1. This LICENSE AGREEMENT is between the Python Software Foundation
("PSF"), and the Individual or Organization ("Licensee") accessing and
otherwise using this software ("Python") in source or binary form and
its associated documentation.
2. Subject to the terms and conditions of this License Agreement, PSF hereby
grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
analyze, test, perform and/or display publicly, prepare derivative works,
distribute, and otherwise use Python alone or in any derivative version,
provided, however, that PSF's License Agreement and PSF's notice of copyright,
i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Python Software Foundation;
All Rights Reserved" are retained in Python alone or in any derivative version
prepared by Licensee.
3. In the event Licensee prepares a derivative work that is based on
or incorporates Python or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python.
4. PSF is making Python available to Licensee on an "AS IS"
basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.
7. Nothing in this License Agreement shall be deemed to create any
relationship of agency, partnership, or joint venture between PSF and
Licensee. This License Agreement does not grant permission to use PSF
trademarks or trade name in a trademark sense to endorse or promote
products or services of Licensee, or any third party.
8. By copying, installing or otherwise using Python, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.
BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
-------------------------------------------
BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
Individual or Organization ("Licensee") accessing and otherwise using
this software in source or binary form and its associated
documentation ("the Software").
2. Subject to the terms and conditions of this BeOpen Python License
Agreement, BeOpen hereby grants Licensee a non-exclusive,
royalty-free, world-wide license to reproduce, analyze, test, perform
and/or display publicly, prepare derivative works, distribute, and
otherwise use the Software alone or in any derivative version,
provided, however, that the BeOpen Python License is retained in the
Software, alone or in any derivative version prepared by Licensee.
3. BeOpen is making the Software available to Licensee on an "AS IS"
basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
5. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.
6. This License Agreement shall be governed by and interpreted in all
respects by the law of the State of California, excluding conflict of
law provisions. Nothing in this License Agreement shall be deemed to
create any relationship of agency, partnership, or joint venture
between BeOpen and Licensee. This License Agreement does not grant
permission to use BeOpen trademarks or trade names in a trademark
sense to endorse or promote products or services of Licensee, or any
third party. As an exception, the "BeOpen Python" logos available at
http://www.pythonlabs.com/logos.html may be used according to the
permissions granted on that web page.
7. By copying, installing or otherwise using the software, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.
CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
---------------------------------------
1. This LICENSE AGREEMENT is between the Corporation for National
Research Initiatives, having an office at 1895 Preston White Drive,
Reston, VA 20191 ("CNRI"), and the Individual or Organization
("Licensee") accessing and otherwise using Python 1.6.1 software in
source or binary form and its associated documentation.
2. Subject to the terms and conditions of this License Agreement, CNRI
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use Python 1.6.1
alone or in any derivative version, provided, however, that CNRI's
License Agreement and CNRI's notice of copyright, i.e., "Copyright (c)
1995-2001 Corporation for National Research Initiatives; All Rights
Reserved" are retained in Python 1.6.1 alone or in any derivative
version prepared by Licensee. Alternately, in lieu of CNRI's License
Agreement, Licensee may substitute the following text (omitting the
quotes): "Python 1.6.1 is made available subject to the terms and
conditions in CNRI's License Agreement. This Agreement together with
Python 1.6.1 may be located on the Internet using the following
unique, persistent identifier (known as a handle): 1895.22/1013. This
Agreement may also be obtained from a proxy server on the Internet
using the following URL: http://hdl.handle.net/1895.22/1013".
3. In the event Licensee prepares a derivative work that is based on
or incorporates Python 1.6.1 or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python 1.6.1.
4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.
7. This License Agreement shall be governed by the federal
intellectual property law of the United States, including without
limitation the federal copyright law, and, to the extent such
U.S. federal law does not apply, by the law of the Commonwealth of
Virginia, excluding Virginia's conflict of law provisions.
Notwithstanding the foregoing, with regard to derivative works based
on Python 1.6.1 that incorporate non-separable material that was
previously distributed under the GNU General Public License (GPL), the
law of the Commonwealth of Virginia shall govern this License
Agreement only as to issues arising under or with respect to
Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
License Agreement shall be deemed to create any relationship of
agency, partnership, or joint venture between CNRI and Licensee. This
License Agreement does not grant permission to use CNRI trademarks or
trade name in a trademark sense to endorse or promote products or
services of Licensee, or any third party.
8. By clicking on the "ACCEPT" button where indicated, or by copying,
installing or otherwise using Python 1.6.1, Licensee agrees to be
bound by the terms and conditions of this License Agreement.
ACCEPT
CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
--------------------------------------------------
Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
The Netherlands. All rights reserved.
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation, and that the name of Stichting Mathematisch
Centrum or CWI not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission.
STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
CPython unicode (https://github.com/python/cpython)
---------------------------------------------------
Numba's unicode support includes source code/algorithms from CPython's unicode
implementation, Numba source code that has a reference starting with:
https://github.com/python/cpython/
and contains in the path "Objects/unicodeobject.c" relates to use/inclusion of
CPython source code which has the following license along with the standard
CPython license:
Unicode implementation based on original code by Fredrik Lundh,
modified by Marc-Andre Lemburg <mal@lemburg.com>.
Major speed upgrades to the method implementations at the Reykjavik
NeedForSpeed sprint, by Fredrik Lundh and Andrew Dalke.
Copyright (c) Corporation for National Research Initiatives.
--------------------------------------------------------------------
The original string type implementation is:
Copyright (c) 1999 by Secret Labs AB
Copyright (c) 1999 by Fredrik Lundh
By obtaining, using, and/or copying this software and/or its
associated documentation, you agree that you have read, understood,
and will comply with the following terms and conditions:
Permission to use, copy, modify, and distribute this software and its
associated documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appears in all
copies, and that both that copyright notice and this permission notice
appear in supporting documentation, and that the name of Secret Labs
AB or the author not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission.
SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR
ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
--------------------------------------------------------------------
cloudpickle
-----------
This module was extracted from the `cloud` package, developed by
PiCloud, Inc.
Copyright (c) 2015, Cloudpickle contributors.
Copyright (c) 2012, Regents of the University of California.
Copyright (c) 2009 PiCloud, Inc. http://www.picloud.com.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of the University of California, Berkeley nor the
names of its contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
© 2020 GitHub, Inc.
NumPy (https://github.com/numpy/numpy)
--------------------------------------
Numba source code that references URLs starting with:
https://github.com/numpy/numpy
relates to use of/inclusion of/derivate work based on NumPy source code which
has the following license:
Copyright (c) 2005-2021, NumPy Developers.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided
with the distribution.
* Neither the name of the NumPy Developers nor the names of any
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
CUDA Half Precision Headers
---------------------------
The files numba/cuda/cuda_fp16.h and numba/cuda/cuda_fp16.hpp are vendored from
the CUDA Toolkit version 11.2.2 under the terms of the NVIDIA Software License
Agreement and CUDA Supplement to Software License Agreement, available at:
https://docs.nvidia.com/cuda/archive/11.2.2/eula/index.html
These files are distributable as listed in Attachment A:
https://docs.nvidia.com/cuda/archive/11.2.2/eula/index.html#attachment-a
include MANIFEST.in
include README.rst setup.py runtests.py versioneer.py CHANGE_LOG LICENSE
recursive-include numba *.c *.cpp *.h *.hpp *.inc
recursive-include docs *.ipynb *.txt *.py Makefile *.rst
recursive-include examples *.py
prune docs/_build
include numba/_version.py
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment