Re: [Numpy-discussion] StackOverflow documentation

[josef . pktd]

On Thu, Jul 21, 2016 at 3:10 PM, Pauli Virtanen  wrote:
> Thu, 21 Jul 2016 16:24:15 +0200, mail kirjoitti:
> [clip]
>> Since it is run by the community, perhaps it's not a bad idea to
>> encourage people to share their examples.
>
> I would perhaps rather encourage people to improve the "Numpy User Guide"
> or the main documentation. Of course, working on that requires a somewhat
> different level of committment than editing what's essentially
> Stackexchange-provided wiki (where content gets relicensed with
> attribution clauses where you have to reference stackexchange and not the
> original author directly).


The way it looks right now, it is more of an example collection by
topic, similar to the old scipy wiki examples for numpy.
http://stackoverflow.com/documentation/python/196/comprehensions#t=201607212153155953853

It doesn't look like it will be a substitute for proper API
documentation, docstrings with numpy standard.
Longer examples or recipes on stackoverflow also have the problem that
code doesn't have a different license and falls under the
documentation license.
So, I don't think it will become a substitute for good notebook or
blog post examples either.

(license is the usual one way street, they copy, we cannot copy back
under our license)

Josef

>
> --
> Pauli Virtanen
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Adding covariance matrix of fitted parameters to fit methods of numpy.polynomial

[Tom Bird]

See issue #7780: https://github.com/numpy/numpy/issues/7780

Would be good if the numpy.polynomial fit methods (e.g. 
numpy.polynomial.legendre.Legendre.fit) could return the covariance matrix of 
the fitted parameters, in the same way as numpy.polyfit.

Let me know if there are any suggestions/concerns. Otherwise I’m happy to add 
the code and update the docs.

Tom




___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] StackOverflow documentation

[Pauli Virtanen]

Thu, 21 Jul 2016 16:24:15 +0200, mail kirjoitti:
[clip]
> Since it is run by the community, perhaps it's not a bad idea to
> encourage people to share their examples.

I would perhaps rather encourage people to improve the "Numpy User Guide" 
or the main documentation. Of course, working on that requires a somewhat 
different level of committment than editing what's essentially 
Stackexchange-provided wiki (where content gets relicensed with 
attribution clauses where you have to reference stackexchange and not the 
original author directly).

-- 
Pauli Virtanen

___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Python 3 dict support (issue #5718)

[Joseph Fox-Rabinovitz]

I will do my best. I am not that familiar with rst or numpy docs, but
that's what PRs are for after all.

-Joe

On Thu, Jul 21, 2016 at 12:09 PM, Marten van Kerkwijk
 wrote:
> Yes, indeed, where should this be!?
>
> The logical place would be in the developer documentation, under
> "understanding the code & getting started" [1], but that is right now just a
> single paragraph.
>
> Others should definitely correct me if wrong, but I *think* this simply does
> not exist, and would suggest to move that subsection to its own section, and
> make your contribution a first entry in it ("the path to creating an array"
> or so). Hopefully, someone else will at some point add, e.g., a section on
> how ufuncs work (I always get quite confused following the long chain
> there...).  Or even something as simple as copying an array (where
> transposing axes can have major impacts on speed).
>
> All the best,
>
> Marten
>
> [1]
> http://docs.scipy.org/doc/numpy-dev/dev/development_environment.html#understanding-the-code-getting-started
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] StackOverflow documentation

[mail]

>> StackOverflow now also has documentation, and there already is a NumPy tag:
>>
>> http://stackoverflow.com/documentation/numpy
>>
>> Not sure what, if anything, do we want to do with this, nor how to handle
>> not having to different sources with the same information. Any thoughts?

>From what I understand, it's not meant to replace real documentation. It's 
>rather a collection of crowd-sourced instructive examples with explanations:

https://stackoverflow.com/tour/documentation

Since it is run by the community, perhaps it's not a bad idea to encourage 
people to share their examples.

Cheers,

Bartosz
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] StackOverflow documentation

[Charles R Harris]

On Thu, Jul 21, 2016 at 5:47 AM, Jaime Fernández del Río <
jaime.f...@gmail.com> wrote:

> StackOverflow now also has documentation, and there already is a NumPy tag:
>
> http://stackoverflow.com/documentation/numpy
>
> Not sure what, if anything, do we want to do with this, nor how to handle
> not having to different sources with the same information. Any thoughts?
>
>
That's interesting. Not sure what to do there, maybe upload some of our
documentation? I'm a bit worried as numpy documentation changes with every
release.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Python 3 dict support (issue #5718)

[Marten van Kerkwijk]

I know it is slightly obnoxious to hold the "making a suggestion is to
volunteer for it" -- but usually a PR to the docs is best made by someone
who is trying to understand it rather than someone who already knows
everything
-- Marten
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] StackOverflow documentation

[Jaime Fernández del Río]

StackOverflow now also has documentation, and there already is a NumPy tag:

http://stackoverflow.com/documentation/numpy

Not sure what, if anything, do we want to do with this, nor how to handle
not having to different sources with the same information. Any thoughts?

Jaime

-- 
(\__/)
( O.o)
( > <) Este es Conejo. Copia a Conejo en tu firma y ayúdale en sus planes
de dominación mundial.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Python 3 dict support (issue #5718)

[Jaime Fernández del Río]

On Wed, Jul 20, 2016 at 9:39 PM, Hannah  wrote:

> I second (and third & fourth &...) this
>
> Thanks so much for this, Jaime, it's exactly what I was looking for and
> couldn't find. Maybe this can be linked to in the contribute docs as an
> "orienting yourself in the codebase" page?
>
Glad to know it helped, realizing how this works was one of the big leaps
in understanding the code base for myself too.  We (my wife and I) have
sent the kids on vacation with their grandparents, so when we are done
enjoying our shortly recovered freedom hunting for Pokemons around Zurich,
I'll try to find time to write this up in a form suitable for the docs,
hopefully over the next couple of weeks.

I have been known to not keep commitments like this in the past, so don't
hold your breath just in case...

Jaime


>
> On Wed, Jul 20, 2016 at 11:07 AM, Joseph Fox-Rabinovitz <
> jfoxrabinov...@gmail.com> wrote:
>
>> Jaime,
>>
>> This is a great intro for people looking to jump into the C side of
>> things. I have been trying to figure out which bits are the important
>> ones from looking at the code and the docs. Your post cut out most of
>> the confusion. Is there some way you would consider adding something
>> like this this to the docs?
>>
>> -Joe
>>
>>
>> On Wed, Jul 20, 2016 at 8:52 AM, Jaime Fernández del Río
>>  wrote:
>> > On Wed, Jul 20, 2016 at 4:28 AM, Hannah  wrote:
>> >>
>> >> Hi,
>> >> I started venturing down the rabbit hole of trying to write a patch to
>> add
>> >> support for numpy to convert python 3 dictionary keys
>> >> (collections.abc.ViewMapping objects), which is open issue #5718 and am
>> >> having trouble orienting myself. I'm unclear as to where the python
>> entry
>> >> point into array is (basically, what function np.array drops into and
>> if
>> >> this is in Python or C) and where/what language (fine with writing
>> either) a
>> >> patch that supports MappingViews would go. Any help getting oriented
>> would
>> >> be much appreciated.
>> >
>> >
>> > Hi Hannah,
>> >
>> > ǹp.array is written in C, and is part of the multiarray module that is
>> > defined here:
>> >
>> >
>> https://github.com/numpy/numpy/blob/maintenance/1.11.x/numpy/core/src/multiarray/multiarraymodule.c
>> >
>> > The "array" name is mapped here:
>> >
>> >
>> https://github.com/numpy/numpy/blob/maintenance/1.11.x/numpy/core/src/multiarray/multiarraymodule.c#L4093
>> >
>> > to the function _array_fromobject defined here:
>> >
>> >
>> https://github.com/numpy/numpy/blob/maintenance/1.11.x/numpy/core/src/multiarray/multiarraymodule.c#L1557
>> >
>> > That functions does some checking and has a couple of fast paths for the
>> > case where the input is already an array or a subclass, but for the
>> general
>> > case it relies on PyArray_CheckFromAny:
>> >
>> >
>> https://github.com/numpy/numpy/blob/maintenance/1.11.x/numpy/core/src/multiarray/ctors.c#L1848
>> >
>> > which in turn calls Pyarray_FromAny:
>> >
>> >
>> https://github.com/numpy/numpy/blob/maintenance/1.11.x/numpy/core/src/multiarray/ctors.c#L1674
>> >
>> > You will also haveto take a look at what goes on in
>> > PyArray_GetArrayParamsFromObject, which gets called by PyArray_FromAny;
>> >
>> >
>> https://github.com/numpy/numpy/blob/maintenance/1.11.x/numpy/core/src/multiarray/ctors.c#L1428
>> >
>> > as well as several other places, but I think they are all (or most of
>> them)
>> > in ctors.c.
>> >
>> > You may also want to take a llok at PyArray_FromIter, which is the
>> function
>> > that ultimately takes care of calls to np.fromiter:
>> >
>> >
>> https://github.com/numpy/numpy/blob/maintenance/1.11.x/numpy/core/src/multiarray/ctors.c#L3657
>> >
>> > It's messy, but not that bad once you get used to it: good luck!
>> >
>> > Jaime
>> >
>> >>
>> >>
>> >> The reasoning for the patch is s that dicts are one of the most common
>> >> Python datatypes and this specifically is because of an upstream issue
>> of
>> >> wanting dict support in matplotlib.
>> >>
>> >> Thanks,
>> >> Hannah
>> >>
>> >> ___
>> >> NumPy-Discussion mailing list
>> >> NumPy-Discussion@scipy.org
>> >> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>> >>
>> >
>> >
>> >
>> > --
>> > (\__/)
>> > ( O.o)
>> > ( > <) Este es Conejo. Copia a Conejo en tu firma y ayúdale en sus
>> planes de
>> > dominación mundial.
>> >
>> > ___
>> > NumPy-Discussion mailing list
>> > NumPy-Discussion@scipy.org
>> > https://mail.scipy.org/mailman/listinfo/numpy-discussion
>> >
>> ___
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>


-- 
(\__/)
( O.o)
( > <) Este es Conejo.