[SciPy-User] ANN: SciPy 1.0 beta release

[Joe Harrington]

Ok, I saw the -Wd at the end, but it just requests the default, so how
does this change anything?  If it's just an ipython benefit, say that
it's recommended for ipython users.

Also, remember that for the vast majority of users, they don't install a
new version, they suddenly discover that their system now has one,
through some software update.  Think students and casual users, as
opposed to PhD research scientists experienced in software management.

But, what we really need is more information about what to DO about the
deprecations.  Not, "we pulled the rug out from under you", but "so that
we don't pull the rug out from under you, do this".  And, in a
more-obvious place than the release notes, which most users don't ever
see.

--jh--

>Um...  This commit has to do with wheels, not deprecations.  Great that
>we're flying with wheels up, though. :-)
>
>--jh--
>
>On Thu, 28 Sep 2017 21:48:41 +1300,  Ralf Gommers <ralf.gommers at gmail.com>
>wrote:
>
>> Done in https://github.com/scipy/scipy/pull/7947
>
>>> On Mon, Sep 18, 2017 at 1:16 AM, Joe Harrington <jh at physics.ucf.edu>
>>> wrote:
>>>
>>>> On Sun, 17 Sep 2017 22:48:35 +1200 Ralf Gommers <ralf.gommers at gmail.com>
>>>> wrote:
>>>>
>>>> > I'm excited to be able to announce the availability of the first beta
>>>> > release of Scipy 1.0.
>>>> >
>>>> [I won't quote the entire release notes!]
>>>>
>>>> Awesome news, looooong in the making!
>>>>
>>>> The number of deprecations and removals is understandably large.
>>>> I think we need a centralized resource for navigating deprecations,
>>>> removals, and changes.  It could be a simple web page, or a more
>>>> involved database.  It should list the change, give or link to the
>>>> rationale, and state the date and package version number.  Most
>>>> importantly, it should give the suggested replacement(s).
>>>>
>>>> Googling "scipy deprecation" found only this page, plus a bunch of
>>>> release notes and discussions.  The page was last updated on Jan 16,
>>>> 2017, and is limited to C-API deprecations:
>>>>
>>>> https://docs.scipy.org/doc/numpy-dev/reference/c-api.deprecations.html
>>>>
>>>> Even once such a document/page/searchable database exists, many will be
>>>> unaware of it, or not know where to find it, so referring to it at the
>>>> top of any list of deprecations/removals would be good.
>>>>
>>>> Once it exists, deprecations could be entered before being implemented,
>>>> and deprecation warnings could refer to an index number in this
>>>> resource, where the user could go for more information on how to fix the
>>>> issue.
>>>>
>>>
>>> Thanks for your thoughts Joe! I'm not sure a database is the way to go,
>>> but you make a good point. We have to guide users a bit more in what to do
>>> about deprecations. I think clear instructions about upgrading in both the
>>> html docs and release announcements would be useful. I don't think there's
>>> many users who run ``python -Wd my_code.py`` .(making depreacations that
>>> affect your code visible) ....
>>>
>>
>
>