Repository navigation
numba-dppy extension #76
Description
Activity
From @diptorupd:
- What if
dpCtlis installed andnumba-dppyis not? - How
numba-dppywill understand thatIntelPython/numbais installed?
- What if
I need a way to build new package with all modifications (i.e. removing
numba.dpplfolder) but make it different from packages we build before. Build number I think is not visible enough. Using next version 0.51.3 loses connection to base Numba version. Using 0.51.2rc1 is also not related to upstream version. Possibly, introducing new end number 0.51.2.1 is ok. Also it is pretty close in goal to buildnumber but more visible.a way to build new package with all modifications (i.e. removing
numba.dpplfolder) but make it different from packages we build beforeWe decided to use build number which is significantly different from previous one. I.e. use build number 20 when the last one was 12.
Update:
PRs with patches (after refactoring it could be proposed to upstream, it is for starting discussion about this changes):
- Patch for with context #96 @AlexanderKalistratov
- Use TargetDispatcher from numba_dppy #118 @PokhodenkoSA - update for moving to
numba-dppy - Upstream patch https://github.com/IntelPython/numba/pull/96 #176
- Use TargetDispatcher from numba_dppy #118 @PokhodenkoSA - update for moving to
- Patch for lowering #98 @reazulhoque @AlexanderKalistratov @DrTodd13 - reviewed - redesign and upstream
- Patch for change numpy functions mapping #99 @reazulhoque - reviewed - redesign and upstream - 2 separate changes
- Patch for addrspace #92 @DrTodd13 @reazulhoque - reviewed - discussion and upstream
- Initial support for Numpy subclasses (for dparray) - common branch on top of patched #139 (Initial support for Numpy subclasses (for dparray) #116) @DrTodd13 @PokhodenkoSA
- Refactoring ParforDiagnostics #135 (f.k.a. Refactoring ParforDiagnostics #130) @1e-to @PokhodenkoSA - could be upstreamed
- Patch for with context #96 @AlexanderKalistratov
@reazulhoque why did you decide to make a copy of part of description and do not modify description itself?
I intended to update the ticket. Modifying the descripton would change the original and stops from keeping versions and updates separate.
Reorganize code base and initial version of numba-dppy extension
numba.dpplpackage to its own repository (i.e.numba-dppy)PRs for cleaning unintended changes (make branch
pydpplas close as possible torelease0.51branch):cpu_dispatchermodifies global state #89 @PokhodenkoSAcpu_dispatchermodifies global state #89PRs with patches (after refactoring it could be proposed to upstream, it is for starting discussion about this changes):
numba-dppywith device_contextnumba/numba#6899ufunc_dbvia context numba/numba#6467replace_functions_mapvia PreParforPass instance numba/numba#6468All upstream patches has label https://github.com/numba/numba/labels/dpPy.
PRs which should me moved to
numba-dppypackage:numba-dppy#109 @PokhodenkoSA - reviewed with @reazulhoquenumba-dppy#110 @PokhodenkoSA - reviewed with @reazulhoquenumba-dppy#107 @PokhodenkoSA - reviewed with @reazulhoquenumba-dppynumba/dppl- delete it after all other PRsnumba-dppyProcess current PRs to numba:
numba-dppyPatched version: #124
How to see our changes:
git diff release0.51..pydpplRecommended way of development now:
python setup.py develop.python setup.py develop.python setup.py develop.python setup.py developshows that some packages are not installed.Branches status
patched- containsrelease0.51branch, minimal set of patches.pydppl- contains all history, code similar topatched,numba-dppysubtree.clean- contains all history, all patches removed,numba-dppysubtree removed - code the same asrelease0.51patched-history- containsclean, minimal set of patches.You should target your PRs to
patchedbranch, because it is simpler thanpydpplbut contains the same code.