Hi everyone,
Please take a look at the latest roadmap proposal:
https://github.com/numpy/numpy/pull/11611
This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities.
Best regards, Stéfan
Looks great! Thank you for doing this!
Gaël
On Tue, Jul 24, 2018 at 12:04:49PM -0700, Stefan van der Walt wrote:
Hi everyone,
Please take a look at the latest roadmap proposal:
This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities.
Best regards, Stéfan _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Stefan and Ralf -- thanks for finishing this up! I'm quite happy with the state of this.
On Tue, Jul 24, 2018 at 1:17 PM Gael Varoquaux < gael.varoquaux@normalesup.org> wrote:
Looks great! Thank you for doing this!
Gaël
On Tue, Jul 24, 2018 at 12:04:49PM -0700, Stefan van der Walt wrote:
Hi everyone,
Please take a look at the latest roadmap proposal:
This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities.
Best regards, Stéfan _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
-- Gael Varoquaux Senior Researcher, INRIA Parietal NeuroSpin/CEA Saclay , Bat 145, 91191 Gif-sur-Yvette France Phone: ++ 33-1-69-08-79-68 <+33%201%2069%2008%2079%2068> http://gael-varoquaux.info http://twitter.com/GaelVaroquaux _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Hey Stefan/Ralf/Stephan,
This looks nice, generally what the community agrees on. Great work, and thanks for putting this together.
Best regards, Hameer Abbasi Sent from Astro https://www.helloastro.com for Mac
On 24. Jul 2018 at 21:04, Stefan van der Walt stefanv@berkeley.edu wrote:
Hi everyone,
Please take a look at the latest roadmap proposal:
https://github.com/numpy/numpy/pull/11611
This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities.
Best regards, Stéfan _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Great work, thanks!
I see this:
“- Fixed width encoded strings (utf8, latin1, ...)”
And a bit of discussion in the PR.
But I think there are key questions to be addressed in handling strings in numpy. I know we’ve had a lot of discussion about it on this list over the years — but is there a place that has captured that discussion / and or we can start a new one?
For example, I am very wary of putting a non-fixed width encoding (e.g. Utf-8) in a fixed width field.
But this PR is not the place to discuss that.
-CHB
Sent from my iPhone
On Jul 24, 2018, at 3:21 PM, Hameer Abbasi einstein.edison@gmail.com wrote:
Hey Stefan/Ralf/Stephan,
This looks nice, generally what the community agrees on. Great work, and thanks for putting this together.
Best regards, Hameer Abbasi Sent from Astro https://www.helloastro.com for Mac
On 24. Jul 2018 at 21:04, Stefan van der Walt stefanv@berkeley.edu wrote:
Hi everyone,
Please take a look at the latest roadmap proposal:
https://github.com/numpy/numpy/pull/11611
This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities.
Best regards, Stéfan _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Hi Chris,
On Wed, 25 Jul 2018 08:13:26 -0700, Chris Barker - NOAA Federal wrote:
For example, I am very wary of putting a non-fixed width encoding (e.g. Utf-8) in a fixed width field.
But this PR is not the place to discuss that.
Since you've followed that discussion closely, can you push a commit to my PR with text that more accurately captures the situation?
Thanks! Stéfan
On Wed, Jul 25, 2018 at 4:02 PM Stefan van der Walt stefanv@berkeley.edu wrote:
Hi Chris,
On Wed, 25 Jul 2018 08:13:26 -0700, Chris Barker - NOAA Federal wrote:
For example, I am very wary of putting a non-fixed width encoding (e.g. Utf-8) in a fixed width field.
But this PR is not the place to discuss that.
Since you've followed that discussion closely, can you push a commit to my PR with text that more accurately captures the situation?
Thanks! Stéfan
Hi Chris,
Obviously the string dtype proposal in the roadmap is only a sketch at this point :).
I do think that options listed currently (encoded strings with fixed-width storage and variable length strings) cover the breadth of proposals from last time. We may not want to implement all of them in NumPy, but I think we can agree that there are use cases for all them, even if only as external dtypes?
Would it help to add "and/or" after the first bullet? Mostly I care about having like to have "improve string dtypes" in some form on the roadmap, and thought it would be helpful to list the concrete proposals that I recall. The actual design choices (especially if we proposal to change any default behavior) will certainly need a NEP.
Best, Stephan
Obviously the string dtype proposal in the roadmap is only a sketch at this point :).
I do think that options listed currently (encoded strings with fixed-width storage and variable length strings) cover the breadth of proposals from last time. We may not want to implement all of them in NumPy, but I think we can agree that there are use cases for all them, even if only as external dtypes?
Maybe :-) — but I totally agree that more complete handling of strings should be on the roadmap.
Would it help to add "and/or" after the first bullet? Mostly I care about having like to have "improve string dtypes" in some form on the roadmap, and thought it would be helpful to list the concrete proposals that I recall.
Sure, something like and/or that makes it clear that the details are yet to be determined would be great.
The actual design choices (especially if we proposal to change any default behavior) will certainly need a NEP.
Then that will be the place to hash out the details — perfect.
I just got a little concerned that s not-well vetted solution was getting nailed down in the roadmap.
-CHB
On Thu, Jul 26, 2018 at 12:41 AM, Chris Barker - NOAA Federal < chris.barker@noaa.gov> wrote:
Obviously the string dtype proposal in the roadmap is only a sketch at
this point :).
I do think that options listed currently (encoded strings with
fixed-width storage and variable length strings) cover the breadth of proposals from last time. We may not want to implement all of them in NumPy, but I think we can agree that there are use cases for all them, even if only as external dtypes?
Maybe :-) — but I totally agree that more complete handling of strings should be on the roadmap.
Would it help to add "and/or" after the first bullet? Mostly I care
about having like to have "improve string dtypes" in some form on the roadmap, and thought it would be helpful to list the concrete proposals that I recall.
Sure, something like and/or that makes it clear that the details are yet to be determined would be great.
The actual design choices (especially if we proposal to change any
default behavior) will certainly need a NEP.
+1 the roadmap just contains topics/directions of interest. It's not the place for any technical decisions.
Related note: we are now using the "wish list" issue label for anything that is too small to put on a roadmap or write a NEP for. Right now there's a lot of random stuff in that label though ([1]), so I think we have to clean that up. Examples of good wish list items that are on there now:
- Document API generation with setup.py, genapi.py, etc. (gh-9203) - Feature request: signal broadcasting is OK over core dimension (gh-8811) - Multidimensional fftfreq/rfftfreq (gh-9094)
I plan to go through and remove the label from issues that don't fit in the next couple of days.
Cheers, Ralf
[1] https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%2223+-...
On Wed, Jul 25, 2018 at 9:19 PM, Ralf Gommers ralf.gommers@gmail.com wrote:
On Thu, Jul 26, 2018 at 12:41 AM, Chris Barker - NOAA Federal < chris.barker@noaa.gov> wrote:
Obviously the string dtype proposal in the roadmap is only a sketch at
this point :).
I do think that options listed currently (encoded strings with
fixed-width storage and variable length strings) cover the breadth of proposals from last time. We may not want to implement all of them in NumPy, but I think we can agree that there are use cases for all them, even if only as external dtypes?
Maybe :-) — but I totally agree that more complete handling of strings should be on the roadmap.
Would it help to add "and/or" after the first bullet? Mostly I care
about having like to have "improve string dtypes" in some form on the roadmap, and thought it would be helpful to list the concrete proposals that I recall.
Sure, something like and/or that makes it clear that the details are yet to be determined would be great.
The actual design choices (especially if we proposal to change any
default behavior) will certainly need a NEP.
+1 the roadmap just contains topics/directions of interest. It's not the place for any technical decisions.
Related note: we are now using the "wish list" issue label for anything that is too small to put on a roadmap or write a NEP for. Right now there's a lot of random stuff in that label though ([1]), so I think we have to clean that up. Examples of good wish list items that are on there now:
- Document API generation with setup.py, genapi.py, etc. (gh-9203)
- Feature request: signal broadcasting is OK over core dimension (gh-8811)
- Multidimensional fftfreq/rfftfreq (gh-9094)
I plan to go through and remove the label from issues that don't fit in the next couple of days.
This is done now. Reduced from 36 to 10 issues. Would be good if we could try for a while to use this label consistently for tasks/enhancements that fall below the "put on the roadmap" threshold but are larger than, e.g., adding a keyword to one function.
Cheers, Ralf
[1] https://github.com/numpy/numpy/issues?q=is%3Aopen+is% 3Aissue+label%3A%2223+-+Wish+List%22
On Tue, Jul 24, 2018 at 12:04 PM, Stefan van der Walt stefanv@berkeley.edu wrote:
Hi everyone,
Please take a look at the latest roadmap proposal:
https://github.com/numpy/numpy/pull/11611
This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities.
The green button was pressed, the roadmap is now live on http://www.numpy.org/neps/. Thanks all!
Cheers, Ralf
On Thu, 2018-08-02 at 05:47 -0700, Ralf Gommers wrote:
On Tue, Jul 24, 2018 at 12:04 PM, Stefan van der Walt <stefanv@berkel ey.edu> wrote:
Hi everyone,
Please take a look at the latest roadmap proposal:
https://github.com/numpy/numpy/pull/11611
This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities.
The green button was pressed, the roadmap is now live on http://www.n umpy.org/neps/. Thanks all!
Great, I hope we can check off some of them soon! :)
- Sebastian
Cheers, Ralf
NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
participants (7)
-
Chris Barker - NOAA Federal -
Gael Varoquaux -
Hameer Abbasi -
Ralf Gommers -
Sebastian Berg -
Stefan van der Walt -
Stephan Hoyer