1.0 Roadmap

[amaloney]

Here are some ideas for taking datashader to a 1.0 release. I'm sure there will be more, but this is a start so we can begin discussion. @jbednar @hoxbro

• create a src layout see https://packaging.python.org/en/latest/discussions/src-layout-vs-flat-layout/
• move tests into a top-level tests directory
• update readme to describe using pixi for development
• moving to standardize numba decorators, i.e. @ngjit replaced with (its more verbose, but standard to the numba documentation) @jit(nopython=True, nogil=True)
• use ruff for formatting
  • make pre-commit hooks for formatting
  • same for linting
  • thoughts on typing requirements?
  • document all these steps for devs
• apply type hints everywhere, and strive to use a static type checker for future work
• look over the code to ensure loops can use numba
  • and also determine if we can replace numba.jit with numba.vectorize or numba.guvectorize for better NumPy ufunc integrations
• update docstrings to conform to NumPy style guides
• clean up branches
• revisit issues, and determine if they are still issues or not

[jbednar]

Thanks!

moving to standardize numba decorators, i.e. @ngjit replaced with (its more verbose, but standard to the numba documentation) @jit(nopython=True, nogil=True)

The background behind using a special decorator was:

So nowadays @ngjit can be replaced with @jit(nogil=True).

[jbednar]

move tests into a top-level tests directory

This should follow whatever the prevailing standard in HoloViz is, after discussion with other HoloViz developers.