[SciPy-dev] backporting changes in scipy.stats

[josef.pktd at gmail.com]

On Thu, May 14, 2009 at 4:16 PM, Bruce Southey <bsouthey at gmail.com> wrote:
> josef.pktd at gmail.com wrote:
>> On Thu, May 14, 2009 at 2:58 PM, Charles R Harris
>> <charlesr.harris at gmail.com> wrote:
>>
>>> On Thu, May 14, 2009 at 8:37 AM, <josef.pktd at gmail.com> wrote:
>>>
>>>> Most of the changes in scipy.stats could be backported to scipy 7.1
>>>>
>>>> changesets: 5591, 5592, 5597, 5599, 5601, 5600, 5602, 5604, 5623,
>>>> 5636, 5637, 5638, 5646, 5672(replay) are (mostly) bugfixes and
>>>> improvement in numerical precision.
>>>> changesets: 5598, 5645 are additional tests
>>>> changesets: 5562, 5564, 5565, 5566, 5567, 5587 are switching to
>>>> np.mean, np.var and can be backported or not
>>>>
>>>> I never did any backporting and I'm currently not set up for it.
>>>> I would appreciate if someone could backport these changes, otherwise
>>>> I will try to do it next weekend.
>>>>
>>>> Thanks,
>>>>
>>> If the changes are all specific to a certain file/directory and there are no
>>> changes you *don't* want to backport from that file/directory, the easiest
>>> thing to do is check out the 7.1.x branch, copy over the files/directory
>>> from the trunk, and check in the result. There are doubtless more
>>> sophisticated ways if you happen to have the whole repository including
>>> branches checked out, but I think that is the simplest and safest.
>>>
>>>
>>
>>
>>
>> Thanks, that sounds easy enough. I have usually only the trunk checked out.
>> There is one set of changes, the removal of stats.mean, var, std and
>> median, that we don't want to backport, but this could be confined to
>> the four functions. I'm very used to winmerge, so I can do this by the
>> end of the week.
>>
>> Josef
>> _______________________________________________
>> Scipy-dev mailing list
>> Scipy-dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/scipy-dev
>>
> Hi,
> Can you also add ticket 877 (Depreciation of samplevar in scipy.stats)
> since it is the same reason as removing stats.std?
>
> The other possibility is ticket 906 Depreciate erfc function.
>

What's the policy for depreciation warnings, should they be
backported?  I can commit and backport them, but do the functions
remain available during the 0.8.x cycle.

erfc, samplevar and samplestd are redundant, but I'm starting to
change my mind a bit about the removal of stats.var and stats.mean.

see my comments to http://projects.scipy.org/scipy/ticket/604

Josef