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.
This diff is collapsed.
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