Re: [sympy] Re: SymPy 1.5 released

[Oscar Benjamin]

I'm not sure how to interpret the pypi download stats. There is a very
regular weekly rhythm and 80% of the downloads are for Linux which I
don't think is representative of the userbase. It looks to me more
like some servers are using sympy and installing it from pypi
thousands of times per day.

On Sun, 15 Dec 2019 at 11:50, Oscar Benjamin  wrote:
>
> In practical terms, maintaining an LTS just means that if a
> substantial problem arises with using SymPy 1.5 on Python 2.7 we could
> add a fix for it on the 1.5 branch and release 1.5.x with that fix. I
> can't see what that problem would be though apart from, say, an update
> to pypi that means 1.5 doesn't install any more.
>
> If something like that happened then I don't see why we couldn't issue
> a release but it seems unlikely that it would be necessary. In any
> case it doesn't require us to keep the the master branch working on
> 2.7 going forwards.
>
> --
> Oscar
>
>
> On Sun, 15 Dec 2019 at 06:00, Jason Moore  wrote:
> >
> > Python 2.7 seems to be about 30% of the downloads still: 
> > https://pypistats.org/packages/sympy
> >
> > Matplotlib is maintaining an LTS for Python 2.7 (I think), not sure about 
> > Jupyter.
> >
> > Jason
> > moorepants.info
> > +01 530-601-9791
> >
> >
> > On Sat, Dec 14, 2019 at 9:07 PM Aaron Meurer  wrote:
> >>
> >> Quite a few other large packages have already dropped Python 2 support
> >> for over a year. matplotlib and Jupyter already dropped it. I'm not
> >> aware of many issues.
> >>
> >> Aaron Meurer
> >>
> >> On Sat, Dec 14, 2019 at 4:47 PM Isuru Fernando  wrote:
> >> >
> >> > FYI, NumPy has already dropped python 2.7 support in 1.17.0 in July. 
> >> > They are supporting 1.16.x until January, 1 2020 and 1.16.x will no 
> >> > longer be supported.
> >> >
> >> > Isuru
> >> >
> >> > On Sat, Dec 14, 2019 at 5:36 PM Oscar Benjamin 
> >> >  wrote:
> >> >>
> >> >> I don't see why anything dramatic will happen when NumPy drops support
> >> >> for Python 2.7. The current releases of both NumPy and SymPy will
> >> >> still be available for Python 2.7. Gradually over time more new
> >> >> releases will emerge that can't be installed on Python 2.7 but nothing
> >> >> will immediately break for people who continue to use 2.7 with NumPy
> >> >> and/or SymPy. Those users will just be stuck with the current versions
> >> >> of 3rd party packages as well as an old version of the interpreter.
> >> >>
> >> >> On Sat, 14 Dec 2019 at 23:28, Jason Moore  wrote:
> >> >> >
> >> >> > I'd like for us to hang on to Py27 until we see what happens when 
> >> >> > NumPy drops it. I personally feel like shit might hit the fan.
> >> >> >
> >> >> > Jason
> >> >> > moorepants.info
> >> >> > +01 530-601-9791
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer  
> >> >> > wrote:
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin 
> >> >> >>  wrote:
> >> >> >>>
> >> >> >>> Python 2.7 support can be dropped in SymPy 1.6 (the next release). 
> >> >> >>> We
> >> >> >>> don't yet know though if we will need a 1.5.1 bugfix release though 
> >> >> >>> so
> >> >> >>> I'd prefer to give it a few weeks before dropping Python 2.7 from
> >> >> >>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
> >> >> >>> stop working on it because it will become unimportable within a few
> >> >> >>> PRs.
> >> >> >>
> >> >> >>
> >> >> >> We should make sure __init__.py stays importable so we can give an 
> >> >> >> error message about Python 2 not being supported.
> >> >> >>
> >> >> >>>
> >> >> >>>
> >> >> >>> Once 2.7 is removed from Travis there are a number of places in the
> >> >> >>> codebase that can be cleaned up (noted with the "dropping Python 2"
> >> >> >>> label) and a bunch of compat code that can be removed.
> >> >> >>>
> >> >> >>> SymPy's current Python version support policy is here
> >> >> >>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
> >> >> >>> and says that a version of Python is supported until it reaches EOL.
> >> >> >>> For Python 3.5 that is September 2020 according to the table here:
> >> >> >>> https://devguide.python.org/#status-of-python-branches
> >> >> >>>
> >> >> >>> Dropping 3.5 before then wouldn't match the support policy but if
> >> >> >>> there are strong advantages then it can be discussed.
> >> >> >>
> >> >> >>
> >> >> >> We might need to become more aggressive at some point. Python is 
> >> >> >> planning on speeding up their release cadence so with the current 
> >> >> >> policy there will be more Python versions for us to support.
> >> >> >>
> >> >> >> Aaron Meurer
> >> >> >>
> >> >> >>>
> >> >> >>>
> >> >> >>> --
> >> >> >>> Oscar
> >> >> >>>
> >> >> >>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi 
> >> >> >>>  wrote:
> >> >> >>> >
> >> >> >>> > Great new!
> >> >> >>> >
> >> >> >>> > Are we going to drop Python 2.7 and 3.4 support?
> >> >> >>> >
> >> >> >>> > There are two nice things to have:
> >> >> >>> >
> >> >> 

Re: [sympy] Re: SymPy 1.5 released

[Oscar Benjamin]

In practical terms, maintaining an LTS just means that if a
substantial problem arises with using SymPy 1.5 on Python 2.7 we could
add a fix for it on the 1.5 branch and release 1.5.x with that fix. I
can't see what that problem would be though apart from, say, an update
to pypi that means 1.5 doesn't install any more.

If something like that happened then I don't see why we couldn't issue
a release but it seems unlikely that it would be necessary. In any
case it doesn't require us to keep the the master branch working on
2.7 going forwards.

--
Oscar


On Sun, 15 Dec 2019 at 06:00, Jason Moore  wrote:
>
> Python 2.7 seems to be about 30% of the downloads still: 
> https://pypistats.org/packages/sympy
>
> Matplotlib is maintaining an LTS for Python 2.7 (I think), not sure about 
> Jupyter.
>
> Jason
> moorepants.info
> +01 530-601-9791
>
>
> On Sat, Dec 14, 2019 at 9:07 PM Aaron Meurer  wrote:
>>
>> Quite a few other large packages have already dropped Python 2 support
>> for over a year. matplotlib and Jupyter already dropped it. I'm not
>> aware of many issues.
>>
>> Aaron Meurer
>>
>> On Sat, Dec 14, 2019 at 4:47 PM Isuru Fernando  wrote:
>> >
>> > FYI, NumPy has already dropped python 2.7 support in 1.17.0 in July. They 
>> > are supporting 1.16.x until January, 1 2020 and 1.16.x will no longer be 
>> > supported.
>> >
>> > Isuru
>> >
>> > On Sat, Dec 14, 2019 at 5:36 PM Oscar Benjamin 
>> >  wrote:
>> >>
>> >> I don't see why anything dramatic will happen when NumPy drops support
>> >> for Python 2.7. The current releases of both NumPy and SymPy will
>> >> still be available for Python 2.7. Gradually over time more new
>> >> releases will emerge that can't be installed on Python 2.7 but nothing
>> >> will immediately break for people who continue to use 2.7 with NumPy
>> >> and/or SymPy. Those users will just be stuck with the current versions
>> >> of 3rd party packages as well as an old version of the interpreter.
>> >>
>> >> On Sat, 14 Dec 2019 at 23:28, Jason Moore  wrote:
>> >> >
>> >> > I'd like for us to hang on to Py27 until we see what happens when NumPy 
>> >> > drops it. I personally feel like shit might hit the fan.
>> >> >
>> >> > Jason
>> >> > moorepants.info
>> >> > +01 530-601-9791
>> >> >
>> >> >
>> >> >
>> >> > On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer  wrote:
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin 
>> >> >>  wrote:
>> >> >>>
>> >> >>> Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
>> >> >>> don't yet know though if we will need a 1.5.1 bugfix release though so
>> >> >>> I'd prefer to give it a few weeks before dropping Python 2.7 from
>> >> >>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
>> >> >>> stop working on it because it will become unimportable within a few
>> >> >>> PRs.
>> >> >>
>> >> >>
>> >> >> We should make sure __init__.py stays importable so we can give an 
>> >> >> error message about Python 2 not being supported.
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>> Once 2.7 is removed from Travis there are a number of places in the
>> >> >>> codebase that can be cleaned up (noted with the "dropping Python 2"
>> >> >>> label) and a bunch of compat code that can be removed.
>> >> >>>
>> >> >>> SymPy's current Python version support policy is here
>> >> >>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
>> >> >>> and says that a version of Python is supported until it reaches EOL.
>> >> >>> For Python 3.5 that is September 2020 according to the table here:
>> >> >>> https://devguide.python.org/#status-of-python-branches
>> >> >>>
>> >> >>> Dropping 3.5 before then wouldn't match the support policy but if
>> >> >>> there are strong advantages then it can be discussed.
>> >> >>
>> >> >>
>> >> >> We might need to become more aggressive at some point. Python is 
>> >> >> planning on speeding up their release cadence so with the current 
>> >> >> policy there will be more Python versions for us to support.
>> >> >>
>> >> >> Aaron Meurer
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> Oscar
>> >> >>>
>> >> >>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi 
>> >> >>>  wrote:
>> >> >>> >
>> >> >>> > Great new!
>> >> >>> >
>> >> >>> > Are we going to drop Python 2.7 and 3.4 support?
>> >> >>> >
>> >> >>> > There are two nice things to have:
>> >> >>> >
>> >> >>> > support for type annotations with enforcement in testing.
>> >> >>> > integration of MatchPy into SymPy (unfortunately this step requires 
>> >> >>> > to drop Python 3.5 support as well, as MatchPy is Python 3.6+ only).
>> >> >>> >
>> >> >>> >
>> >> >>> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
>> >> >>> >>
>> >> >>> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin 
>> >> >>> >>  wrote:
>> >> >>> >> >
>> >> >>> >> > Hi all,
>> >> >>> >> >
>> >> >>> >> > It is my pleasure to announce the release of SymPy 1.5 today. I 
>> >> >>> >> > have
>> >> >>> >> > uploaded the release files to for this 

Re: [sympy] Re: SymPy 1.5 released

[Jason Moore]

Python 2.7 seems to be about 30% of the downloads still:
https://pypistats.org/packages/sympy

Matplotlib is maintaining an LTS for Python 2.7 (I think), not sure about
Jupyter.

Jason
moorepants.info
+01 530-601-9791


On Sat, Dec 14, 2019 at 9:07 PM Aaron Meurer  wrote:

> Quite a few other large packages have already dropped Python 2 support
> for over a year. matplotlib and Jupyter already dropped it. I'm not
> aware of many issues.
>
> Aaron Meurer
>
> On Sat, Dec 14, 2019 at 4:47 PM Isuru Fernando  wrote:
> >
> > FYI, NumPy has already dropped python 2.7 support in 1.17.0 in July.
> They are supporting 1.16.x until January, 1 2020 and 1.16.x will no longer
> be supported.
> >
> > Isuru
> >
> > On Sat, Dec 14, 2019 at 5:36 PM Oscar Benjamin <
> oscar.j.benja...@gmail.com> wrote:
> >>
> >> I don't see why anything dramatic will happen when NumPy drops support
> >> for Python 2.7. The current releases of both NumPy and SymPy will
> >> still be available for Python 2.7. Gradually over time more new
> >> releases will emerge that can't be installed on Python 2.7 but nothing
> >> will immediately break for people who continue to use 2.7 with NumPy
> >> and/or SymPy. Those users will just be stuck with the current versions
> >> of 3rd party packages as well as an old version of the interpreter.
> >>
> >> On Sat, 14 Dec 2019 at 23:28, Jason Moore  wrote:
> >> >
> >> > I'd like for us to hang on to Py27 until we see what happens when
> NumPy drops it. I personally feel like shit might hit the fan.
> >> >
> >> > Jason
> >> > moorepants.info
> >> > +01 530-601-9791
> >> >
> >> >
> >> >
> >> > On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer 
> wrote:
> >> >>
> >> >>
> >> >>
> >> >> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin <
> oscar.j.benja...@gmail.com> wrote:
> >> >>>
> >> >>> Python 2.7 support can be dropped in SymPy 1.6 (the next release).
> We
> >> >>> don't yet know though if we will need a 1.5.1 bugfix release though
> so
> >> >>> I'd prefer to give it a few weeks before dropping Python 2.7 from
> >> >>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
> >> >>> stop working on it because it will become unimportable within a few
> >> >>> PRs.
> >> >>
> >> >>
> >> >> We should make sure __init__.py stays importable so we can give an
> error message about Python 2 not being supported.
> >> >>
> >> >>>
> >> >>>
> >> >>> Once 2.7 is removed from Travis there are a number of places in the
> >> >>> codebase that can be cleaned up (noted with the "dropping Python 2"
> >> >>> label) and a bunch of compat code that can be removed.
> >> >>>
> >> >>> SymPy's current Python version support policy is here
> >> >>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
> >> >>> and says that a version of Python is supported until it reaches EOL.
> >> >>> For Python 3.5 that is September 2020 according to the table here:
> >> >>> https://devguide.python.org/#status-of-python-branches
> >> >>>
> >> >>> Dropping 3.5 before then wouldn't match the support policy but if
> >> >>> there are strong advantages then it can be discussed.
> >> >>
> >> >>
> >> >> We might need to become more aggressive at some point. Python is
> planning on speeding up their release cadence so with the current policy
> there will be more Python versions for us to support.
> >> >>
> >> >> Aaron Meurer
> >> >>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Oscar
> >> >>>
> >> >>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi <
> franz.bona...@gmail.com> wrote:
> >> >>> >
> >> >>> > Great new!
> >> >>> >
> >> >>> > Are we going to drop Python 2.7 and 3.4 support?
> >> >>> >
> >> >>> > There are two nice things to have:
> >> >>> >
> >> >>> > support for type annotations with enforcement in testing.
> >> >>> > integration of MatchPy into SymPy (unfortunately this step
> requires to drop Python 3.5 support as well, as MatchPy is Python 3.6+
> only).
> >> >>> >
> >> >>> >
> >> >>> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
> >> >>> >>
> >> >>> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin <
> oscar.j...@gmail.com> wrote:
> >> >>> >> >
> >> >>> >> > Hi all,
> >> >>> >> >
> >> >>> >> > It is my pleasure to announce the release of SymPy 1.5 today.
> I have
> >> >>> >> > uploaded the release files to for this release to PyPI so you
> should
> >> >>> >> > be able to install or upgrade with
> >> >>> >> >
> >> >>> >> > $ pip install -U sympy
> >> >>> >>
> >> >>> >> I just realised I didn't give the hashes for the release files
> which are
> >> >>> >>
> >> >>> >> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
> >> >>> >> sympy-1.5-py2.py3-none-any.whl
> >> >>> >> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
> >> >>> >> sympy-1.5.tar.gz
> >> >>> >> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
> >> >>> >> sympy-docs-html-1.5.zip
> >> >>> >> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
> >> >>> >> sympy-docs-pdf-1.5.pdf
> >> >>> >>
> >> 

Re: [sympy] Re: SymPy 1.5 released

[Aaron Meurer]

Quite a few other large packages have already dropped Python 2 support
for over a year. matplotlib and Jupyter already dropped it. I'm not
aware of many issues.

Aaron Meurer

On Sat, Dec 14, 2019 at 4:47 PM Isuru Fernando  wrote:
>
> FYI, NumPy has already dropped python 2.7 support in 1.17.0 in July. They are 
> supporting 1.16.x until January, 1 2020 and 1.16.x will no longer be 
> supported.
>
> Isuru
>
> On Sat, Dec 14, 2019 at 5:36 PM Oscar Benjamin  
> wrote:
>>
>> I don't see why anything dramatic will happen when NumPy drops support
>> for Python 2.7. The current releases of both NumPy and SymPy will
>> still be available for Python 2.7. Gradually over time more new
>> releases will emerge that can't be installed on Python 2.7 but nothing
>> will immediately break for people who continue to use 2.7 with NumPy
>> and/or SymPy. Those users will just be stuck with the current versions
>> of 3rd party packages as well as an old version of the interpreter.
>>
>> On Sat, 14 Dec 2019 at 23:28, Jason Moore  wrote:
>> >
>> > I'd like for us to hang on to Py27 until we see what happens when NumPy 
>> > drops it. I personally feel like shit might hit the fan.
>> >
>> > Jason
>> > moorepants.info
>> > +01 530-601-9791
>> >
>> >
>> >
>> > On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer  wrote:
>> >>
>> >>
>> >>
>> >> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin 
>> >>  wrote:
>> >>>
>> >>> Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
>> >>> don't yet know though if we will need a 1.5.1 bugfix release though so
>> >>> I'd prefer to give it a few weeks before dropping Python 2.7 from
>> >>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
>> >>> stop working on it because it will become unimportable within a few
>> >>> PRs.
>> >>
>> >>
>> >> We should make sure __init__.py stays importable so we can give an error 
>> >> message about Python 2 not being supported.
>> >>
>> >>>
>> >>>
>> >>> Once 2.7 is removed from Travis there are a number of places in the
>> >>> codebase that can be cleaned up (noted with the "dropping Python 2"
>> >>> label) and a bunch of compat code that can be removed.
>> >>>
>> >>> SymPy's current Python version support policy is here
>> >>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
>> >>> and says that a version of Python is supported until it reaches EOL.
>> >>> For Python 3.5 that is September 2020 according to the table here:
>> >>> https://devguide.python.org/#status-of-python-branches
>> >>>
>> >>> Dropping 3.5 before then wouldn't match the support policy but if
>> >>> there are strong advantages then it can be discussed.
>> >>
>> >>
>> >> We might need to become more aggressive at some point. Python is planning 
>> >> on speeding up their release cadence so with the current policy there 
>> >> will be more Python versions for us to support.
>> >>
>> >> Aaron Meurer
>> >>
>> >>>
>> >>>
>> >>> --
>> >>> Oscar
>> >>>
>> >>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi 
>> >>>  wrote:
>> >>> >
>> >>> > Great new!
>> >>> >
>> >>> > Are we going to drop Python 2.7 and 3.4 support?
>> >>> >
>> >>> > There are two nice things to have:
>> >>> >
>> >>> > support for type annotations with enforcement in testing.
>> >>> > integration of MatchPy into SymPy (unfortunately this step requires to 
>> >>> > drop Python 3.5 support as well, as MatchPy is Python 3.6+ only).
>> >>> >
>> >>> >
>> >>> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
>> >>> >>
>> >>> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin  
>> >>> >> wrote:
>> >>> >> >
>> >>> >> > Hi all,
>> >>> >> >
>> >>> >> > It is my pleasure to announce the release of SymPy 1.5 today. I have
>> >>> >> > uploaded the release files to for this release to PyPI so you should
>> >>> >> > be able to install or upgrade with
>> >>> >> >
>> >>> >> > $ pip install -U sympy
>> >>> >>
>> >>> >> I just realised I didn't give the hashes for the release files which 
>> >>> >> are
>> >>> >>
>> >>> >> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
>> >>> >> sympy-1.5-py2.py3-none-any.whl
>> >>> >> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
>> >>> >> sympy-1.5.tar.gz
>> >>> >> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
>> >>> >> sympy-docs-html-1.5.zip
>> >>> >> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
>> >>> >> sympy-docs-pdf-1.5.pdf
>> >>> >>
>> >>> >> I'm interested to know: does anyone check these?
>> >>> >>
>> >>> >> --
>> >>> >> Oscar
>> >>> >
>> >>> > --
>> >>> > You received this message because you are subscribed to the Google 
>> >>> > Groups "sympy" group.
>> >>> > To unsubscribe from this group and stop receiving emails from it, send 
>> >>> > an email to sympy+unsubscr...@googlegroups.com.
>> >>> > To view this discussion on the web visit 
>> >>> > https://groups.google.com/d/msgid/sympy/b17bed68-2653-4bb9-8b54-fa19eaeb18e3%40googlegroups.com.
>> >>>
>> >>> --
>> >>> You 

Re: [sympy] Re: SymPy 1.5 released

[Isuru Fernando]

FYI, NumPy has already dropped python 2.7 support in 1.17.0 in July. They
are supporting 1.16.x until January, 1 2020 and 1.16.x will no longer be
supported.

Isuru

On Sat, Dec 14, 2019 at 5:36 PM Oscar Benjamin 
wrote:

> I don't see why anything dramatic will happen when NumPy drops support
> for Python 2.7. The current releases of both NumPy and SymPy will
> still be available for Python 2.7. Gradually over time more new
> releases will emerge that can't be installed on Python 2.7 but nothing
> will immediately break for people who continue to use 2.7 with NumPy
> and/or SymPy. Those users will just be stuck with the current versions
> of 3rd party packages as well as an old version of the interpreter.
>
> On Sat, 14 Dec 2019 at 23:28, Jason Moore  wrote:
> >
> > I'd like for us to hang on to Py27 until we see what happens when NumPy
> drops it. I personally feel like shit might hit the fan.
> >
> > Jason
> > moorepants.info
> > +01 530-601-9791
> >
> >
> >
> > On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer  wrote:
> >>
> >>
> >>
> >> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin <
> oscar.j.benja...@gmail.com> wrote:
> >>>
> >>> Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
> >>> don't yet know though if we will need a 1.5.1 bugfix release though so
> >>> I'd prefer to give it a few weeks before dropping Python 2.7 from
> >>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
> >>> stop working on it because it will become unimportable within a few
> >>> PRs.
> >>
> >>
> >> We should make sure __init__.py stays importable so we can give an
> error message about Python 2 not being supported.
> >>
> >>>
> >>>
> >>> Once 2.7 is removed from Travis there are a number of places in the
> >>> codebase that can be cleaned up (noted with the "dropping Python 2"
> >>> label) and a bunch of compat code that can be removed.
> >>>
> >>> SymPy's current Python version support policy is here
> >>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
> >>> and says that a version of Python is supported until it reaches EOL.
> >>> For Python 3.5 that is September 2020 according to the table here:
> >>> https://devguide.python.org/#status-of-python-branches
> >>>
> >>> Dropping 3.5 before then wouldn't match the support policy but if
> >>> there are strong advantages then it can be discussed.
> >>
> >>
> >> We might need to become more aggressive at some point. Python is
> planning on speeding up their release cadence so with the current policy
> there will be more Python versions for us to support.
> >>
> >> Aaron Meurer
> >>
> >>>
> >>>
> >>> --
> >>> Oscar
> >>>
> >>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi <
> franz.bona...@gmail.com> wrote:
> >>> >
> >>> > Great new!
> >>> >
> >>> > Are we going to drop Python 2.7 and 3.4 support?
> >>> >
> >>> > There are two nice things to have:
> >>> >
> >>> > support for type annotations with enforcement in testing.
> >>> > integration of MatchPy into SymPy (unfortunately this step requires
> to drop Python 3.5 support as well, as MatchPy is Python 3.6+ only).
> >>> >
> >>> >
> >>> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
> >>> >>
> >>> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin 
> wrote:
> >>> >> >
> >>> >> > Hi all,
> >>> >> >
> >>> >> > It is my pleasure to announce the release of SymPy 1.5 today. I
> have
> >>> >> > uploaded the release files to for this release to PyPI so you
> should
> >>> >> > be able to install or upgrade with
> >>> >> >
> >>> >> > $ pip install -U sympy
> >>> >>
> >>> >> I just realised I didn't give the hashes for the release files
> which are
> >>> >>
> >>> >> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
> >>> >> sympy-1.5-py2.py3-none-any.whl
> >>> >> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
> >>> >> sympy-1.5.tar.gz
> >>> >> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
> >>> >> sympy-docs-html-1.5.zip
> >>> >> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
> >>> >> sympy-docs-pdf-1.5.pdf
> >>> >>
> >>> >> I'm interested to know: does anyone check these?
> >>> >>
> >>> >> --
> >>> >> Oscar
> >>> >
> >>> > --
> >>> > You received this message because you are subscribed to the Google
> Groups "sympy" group.
> >>> > To unsubscribe from this group and stop receiving emails from it,
> send an email to sympy+unsubscr...@googlegroups.com.
> >>> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/b17bed68-2653-4bb9-8b54-fa19eaeb18e3%40googlegroups.com
> .
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups "sympy" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an email to sympy+unsubscr...@googlegroups.com.
> >>> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/CAHVvXxTr0NMn5w2ZKbbCTRdtZHp0Fq4H18vrHCFr8%2BK5KbO%2BbA%40mail.gmail.com
> .
> 

Re: [sympy] Re: SymPy 1.5 released

[Jason Moore]

I'm just suggesting we watch and see what happens when the most major
packages switch and then follow after witnessing if it goes smoothly or not.

Jason
moorepants.info
+01 530-601-9791


On Sat, Dec 14, 2019 at 3:36 PM Oscar Benjamin 
wrote:

> I don't see why anything dramatic will happen when NumPy drops support
> for Python 2.7. The current releases of both NumPy and SymPy will
> still be available for Python 2.7. Gradually over time more new
> releases will emerge that can't be installed on Python 2.7 but nothing
> will immediately break for people who continue to use 2.7 with NumPy
> and/or SymPy. Those users will just be stuck with the current versions
> of 3rd party packages as well as an old version of the interpreter.
>
> On Sat, 14 Dec 2019 at 23:28, Jason Moore  wrote:
> >
> > I'd like for us to hang on to Py27 until we see what happens when NumPy
> drops it. I personally feel like shit might hit the fan.
> >
> > Jason
> > moorepants.info
> > +01 530-601-9791
> >
> >
> >
> > On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer  wrote:
> >>
> >>
> >>
> >> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin <
> oscar.j.benja...@gmail.com> wrote:
> >>>
> >>> Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
> >>> don't yet know though if we will need a 1.5.1 bugfix release though so
> >>> I'd prefer to give it a few weeks before dropping Python 2.7 from
> >>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
> >>> stop working on it because it will become unimportable within a few
> >>> PRs.
> >>
> >>
> >> We should make sure __init__.py stays importable so we can give an
> error message about Python 2 not being supported.
> >>
> >>>
> >>>
> >>> Once 2.7 is removed from Travis there are a number of places in the
> >>> codebase that can be cleaned up (noted with the "dropping Python 2"
> >>> label) and a bunch of compat code that can be removed.
> >>>
> >>> SymPy's current Python version support policy is here
> >>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
> >>> and says that a version of Python is supported until it reaches EOL.
> >>> For Python 3.5 that is September 2020 according to the table here:
> >>> https://devguide.python.org/#status-of-python-branches
> >>>
> >>> Dropping 3.5 before then wouldn't match the support policy but if
> >>> there are strong advantages then it can be discussed.
> >>
> >>
> >> We might need to become more aggressive at some point. Python is
> planning on speeding up their release cadence so with the current policy
> there will be more Python versions for us to support.
> >>
> >> Aaron Meurer
> >>
> >>>
> >>>
> >>> --
> >>> Oscar
> >>>
> >>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi <
> franz.bona...@gmail.com> wrote:
> >>> >
> >>> > Great new!
> >>> >
> >>> > Are we going to drop Python 2.7 and 3.4 support?
> >>> >
> >>> > There are two nice things to have:
> >>> >
> >>> > support for type annotations with enforcement in testing.
> >>> > integration of MatchPy into SymPy (unfortunately this step requires
> to drop Python 3.5 support as well, as MatchPy is Python 3.6+ only).
> >>> >
> >>> >
> >>> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
> >>> >>
> >>> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin 
> wrote:
> >>> >> >
> >>> >> > Hi all,
> >>> >> >
> >>> >> > It is my pleasure to announce the release of SymPy 1.5 today. I
> have
> >>> >> > uploaded the release files to for this release to PyPI so you
> should
> >>> >> > be able to install or upgrade with
> >>> >> >
> >>> >> > $ pip install -U sympy
> >>> >>
> >>> >> I just realised I didn't give the hashes for the release files
> which are
> >>> >>
> >>> >> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
> >>> >> sympy-1.5-py2.py3-none-any.whl
> >>> >> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
> >>> >> sympy-1.5.tar.gz
> >>> >> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
> >>> >> sympy-docs-html-1.5.zip
> >>> >> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
> >>> >> sympy-docs-pdf-1.5.pdf
> >>> >>
> >>> >> I'm interested to know: does anyone check these?
> >>> >>
> >>> >> --
> >>> >> Oscar
> >>> >
> >>> > --
> >>> > You received this message because you are subscribed to the Google
> Groups "sympy" group.
> >>> > To unsubscribe from this group and stop receiving emails from it,
> send an email to sympy+unsubscr...@googlegroups.com.
> >>> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/b17bed68-2653-4bb9-8b54-fa19eaeb18e3%40googlegroups.com
> .
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups "sympy" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an email to sympy+unsubscr...@googlegroups.com.
> >>> To view this discussion on the web visit
> 

Re: [sympy] Re: SymPy 1.5 released

[Oscar Benjamin]

I don't see why anything dramatic will happen when NumPy drops support
for Python 2.7. The current releases of both NumPy and SymPy will
still be available for Python 2.7. Gradually over time more new
releases will emerge that can't be installed on Python 2.7 but nothing
will immediately break for people who continue to use 2.7 with NumPy
and/or SymPy. Those users will just be stuck with the current versions
of 3rd party packages as well as an old version of the interpreter.

On Sat, 14 Dec 2019 at 23:28, Jason Moore  wrote:
>
> I'd like for us to hang on to Py27 until we see what happens when NumPy drops 
> it. I personally feel like shit might hit the fan.
>
> Jason
> moorepants.info
> +01 530-601-9791
>
>
>
> On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer  wrote:
>>
>>
>>
>> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin  
>> wrote:
>>>
>>> Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
>>> don't yet know though if we will need a 1.5.1 bugfix release though so
>>> I'd prefer to give it a few weeks before dropping Python 2.7 from
>>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
>>> stop working on it because it will become unimportable within a few
>>> PRs.
>>
>>
>> We should make sure __init__.py stays importable so we can give an error 
>> message about Python 2 not being supported.
>>
>>>
>>>
>>> Once 2.7 is removed from Travis there are a number of places in the
>>> codebase that can be cleaned up (noted with the "dropping Python 2"
>>> label) and a bunch of compat code that can be removed.
>>>
>>> SymPy's current Python version support policy is here
>>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
>>> and says that a version of Python is supported until it reaches EOL.
>>> For Python 3.5 that is September 2020 according to the table here:
>>> https://devguide.python.org/#status-of-python-branches
>>>
>>> Dropping 3.5 before then wouldn't match the support policy but if
>>> there are strong advantages then it can be discussed.
>>
>>
>> We might need to become more aggressive at some point. Python is planning on 
>> speeding up their release cadence so with the current policy there will be 
>> more Python versions for us to support.
>>
>> Aaron Meurer
>>
>>>
>>>
>>> --
>>> Oscar
>>>
>>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi  
>>> wrote:
>>> >
>>> > Great new!
>>> >
>>> > Are we going to drop Python 2.7 and 3.4 support?
>>> >
>>> > There are two nice things to have:
>>> >
>>> > support for type annotations with enforcement in testing.
>>> > integration of MatchPy into SymPy (unfortunately this step requires to 
>>> > drop Python 3.5 support as well, as MatchPy is Python 3.6+ only).
>>> >
>>> >
>>> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
>>> >>
>>> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin  
>>> >> wrote:
>>> >> >
>>> >> > Hi all,
>>> >> >
>>> >> > It is my pleasure to announce the release of SymPy 1.5 today. I have
>>> >> > uploaded the release files to for this release to PyPI so you should
>>> >> > be able to install or upgrade with
>>> >> >
>>> >> > $ pip install -U sympy
>>> >>
>>> >> I just realised I didn't give the hashes for the release files which are
>>> >>
>>> >> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
>>> >> sympy-1.5-py2.py3-none-any.whl
>>> >> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
>>> >> sympy-1.5.tar.gz
>>> >> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
>>> >> sympy-docs-html-1.5.zip
>>> >> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
>>> >> sympy-docs-pdf-1.5.pdf
>>> >>
>>> >> I'm interested to know: does anyone check these?
>>> >>
>>> >> --
>>> >> Oscar
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google Groups 
>>> > "sympy" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send an 
>>> > email to sympy+unsubscr...@googlegroups.com.
>>> > To view this discussion on the web visit 
>>> > https://groups.google.com/d/msgid/sympy/b17bed68-2653-4bb9-8b54-fa19eaeb18e3%40googlegroups.com.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "sympy" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to sympy+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sympy/CAHVvXxTr0NMn5w2ZKbbCTRdtZHp0Fq4H18vrHCFr8%2BK5KbO%2BbA%40mail.gmail.com.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "sympy" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sympy+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sympy/CAKgW%3D6JgEuAWSX%2B37dfDkRvxGJYd23NFHAvy%2BaCD59VShLFqQg%40mail.gmail.com.
>
> --
> You received this message because you are subscribed 

Re: [sympy] Re: SymPy 1.5 released

[Jason Moore]

I'd like for us to hang on to Py27 until we see what happens when NumPy
drops it. I personally feel like shit might hit the fan.

Jason
moorepants.info
+01 530-601-9791



On Sat, Dec 14, 2019 at 3:05 PM Aaron Meurer  wrote:

>
>
> On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin 
> wrote:
>
>> Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
>> don't yet know though if we will need a 1.5.1 bugfix release though so
>> I'd prefer to give it a few weeks before dropping Python 2.7 from
>> Travis. I think that as soon as Python 2.7 is not tested SymPy will
>> stop working on it because it will become unimportable within a few
>> PRs.
>
>
> We should make sure __init__.py stays importable so we can give an error
> message about Python 2 not being supported.
>
>
>>
>> Once 2.7 is removed from Travis there are a number of places in the
>> codebase that can be cleaned up (noted with the "dropping Python 2"
>> label) and a bunch of compat code that can be removed.
>>
>> SymPy's current Python version support policy is here
>> https://github.com/sympy/sympy/wiki/Python-version-support-policy
>> and says that a version of Python is supported until it reaches EOL.
>> For Python 3.5 that is September 2020 according to the table here:
>> https://devguide.python.org/#status-of-python-branches
>>
>> Dropping 3.5 before then wouldn't match the support policy but if
>> there are strong advantages then it can be discussed.
>
>
> We might need to become more aggressive at some point. Python is planning
> on speeding up their release cadence so with the current policy there will
> be more Python versions for us to support.
>
> Aaron Meurer
>
>
>>
>> --
>> Oscar
>>
>> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi 
>> wrote:
>> >
>> > Great new!
>> >
>> > Are we going to drop Python 2.7 and 3.4 support?
>> >
>> > There are two nice things to have:
>> >
>> > support for type annotations with enforcement in testing.
>> > integration of MatchPy into SymPy (unfortunately this step requires to
>> drop Python 3.5 support as well, as MatchPy is Python 3.6+ only).
>> >
>> >
>> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
>> >>
>> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin 
>> wrote:
>> >> >
>> >> > Hi all,
>> >> >
>> >> > It is my pleasure to announce the release of SymPy 1.5 today. I have
>> >> > uploaded the release files to for this release to PyPI so you should
>> >> > be able to install or upgrade with
>> >> >
>> >> > $ pip install -U sympy
>> >>
>> >> I just realised I didn't give the hashes for the release files which
>> are
>> >>
>> >> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
>> >> sympy-1.5-py2.py3-none-any.whl
>> >> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
>> >> sympy-1.5.tar.gz
>> >> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
>> >> sympy-docs-html-1.5.zip
>> >> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
>> >> sympy-docs-pdf-1.5.pdf
>> >>
>> >> I'm interested to know: does anyone check these?
>> >>
>> >> --
>> >> Oscar
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "sympy" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an email to sympy+unsubscr...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sympy/b17bed68-2653-4bb9-8b54-fa19eaeb18e3%40googlegroups.com
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sympy" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sympy+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sympy/CAHVvXxTr0NMn5w2ZKbbCTRdtZHp0Fq4H18vrHCFr8%2BK5KbO%2BbA%40mail.gmail.com
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sympy+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/CAKgW%3D6JgEuAWSX%2B37dfDkRvxGJYd23NFHAvy%2BaCD59VShLFqQg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAP7f1AiJqLahHrRVk%3D3UiYCvh5ERVrKqwLAOS0GZyUEi9CYCbA%40mail.gmail.com.

Re: [sympy] Re: SymPy 1.5 released

[Aaron Meurer]

On Sat, Dec 14, 2019 at 2:31 PM Oscar Benjamin 
wrote:

> Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
> don't yet know though if we will need a 1.5.1 bugfix release though so
> I'd prefer to give it a few weeks before dropping Python 2.7 from
> Travis. I think that as soon as Python 2.7 is not tested SymPy will
> stop working on it because it will become unimportable within a few
> PRs.


We should make sure __init__.py stays importable so we can give an error
message about Python 2 not being supported.


>
> Once 2.7 is removed from Travis there are a number of places in the
> codebase that can be cleaned up (noted with the "dropping Python 2"
> label) and a bunch of compat code that can be removed.
>
> SymPy's current Python version support policy is here
> https://github.com/sympy/sympy/wiki/Python-version-support-policy
> and says that a version of Python is supported until it reaches EOL.
> For Python 3.5 that is September 2020 according to the table here:
> https://devguide.python.org/#status-of-python-branches
>
> Dropping 3.5 before then wouldn't match the support policy but if
> there are strong advantages then it can be discussed.


We might need to become more aggressive at some point. Python is planning
on speeding up their release cadence so with the current policy there will
be more Python versions for us to support.

Aaron Meurer


>
> --
> Oscar
>
> On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi 
> wrote:
> >
> > Great new!
> >
> > Are we going to drop Python 2.7 and 3.4 support?
> >
> > There are two nice things to have:
> >
> > support for type annotations with enforcement in testing.
> > integration of MatchPy into SymPy (unfortunately this step requires to
> drop Python 3.5 support as well, as MatchPy is Python 3.6+ only).
> >
> >
> > On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
> >>
> >> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin 
> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > It is my pleasure to announce the release of SymPy 1.5 today. I have
> >> > uploaded the release files to for this release to PyPI so you should
> >> > be able to install or upgrade with
> >> >
> >> > $ pip install -U sympy
> >>
> >> I just realised I didn't give the hashes for the release files which are
> >>
> >> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
> >> sympy-1.5-py2.py3-none-any.whl
> >> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
> >> sympy-1.5.tar.gz
> >> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
> >> sympy-docs-html-1.5.zip
> >> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
> >> sympy-docs-pdf-1.5.pdf
> >>
> >> I'm interested to know: does anyone check these?
> >>
> >> --
> >> Oscar
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sympy" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sympy+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/b17bed68-2653-4bb9-8b54-fa19eaeb18e3%40googlegroups.com
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sympy+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/CAHVvXxTr0NMn5w2ZKbbCTRdtZHp0Fq4H18vrHCFr8%2BK5KbO%2BbA%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAKgW%3D6JgEuAWSX%2B37dfDkRvxGJYd23NFHAvy%2BaCD59VShLFqQg%40mail.gmail.com.

Re: [sympy] Re: SymPy 1.5 released

[Oscar Benjamin]

Python 2.7 support can be dropped in SymPy 1.6 (the next release). We
don't yet know though if we will need a 1.5.1 bugfix release though so
I'd prefer to give it a few weeks before dropping Python 2.7 from
Travis. I think that as soon as Python 2.7 is not tested SymPy will
stop working on it because it will become unimportable within a few
PRs.

Once 2.7 is removed from Travis there are a number of places in the
codebase that can be cleaned up (noted with the "dropping Python 2"
label) and a bunch of compat code that can be removed.

SymPy's current Python version support policy is here
https://github.com/sympy/sympy/wiki/Python-version-support-policy
and says that a version of Python is supported until it reaches EOL.
For Python 3.5 that is September 2020 according to the table here:
https://devguide.python.org/#status-of-python-branches

Dropping 3.5 before then wouldn't match the support policy but if
there are strong advantages then it can be discussed.

--
Oscar

On Sat, 14 Dec 2019 at 15:26, Francesco Bonazzi  wrote:
>
> Great new!
>
> Are we going to drop Python 2.7 and 3.4 support?
>
> There are two nice things to have:
>
> support for type annotations with enforcement in testing.
> integration of MatchPy into SymPy (unfortunately this step requires to drop 
> Python 3.5 support as well, as MatchPy is Python 3.6+ only).
>
>
> On Saturday, 14 December 2019 02:38:23 UTC+1, Oscar wrote:
>>
>> On Fri, 13 Dec 2019 at 21:41, Oscar Benjamin  wrote:
>> >
>> > Hi all,
>> >
>> > It is my pleasure to announce the release of SymPy 1.5 today. I have
>> > uploaded the release files to for this release to PyPI so you should
>> > be able to install or upgrade with
>> >
>> > $ pip install -U sympy
>>
>> I just realised I didn't give the hashes for the release files which are
>>
>> 8ae4a95378304ed4081921767fe46f0adf5921bf471c9f5df425abf2c655d751
>> sympy-1.5-py2.py3-none-any.whl
>> 31567dc010bff0967ef7a87210acf3f938c6ab24481581fc143536fb103e9ce8
>> sympy-1.5.tar.gz
>> b880a0819efac35661e59ec4341e3df7667e51f952033b12a91361f792458639
>> sympy-docs-html-1.5.zip
>> 2f366888c0efc86bf031e1db4dd988463c26583a8582e33b4bc85eb6b14d4ea1
>> sympy-docs-pdf-1.5.pdf
>>
>> I'm interested to know: does anyone check these?
>>
>> --
>> Oscar
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sympy+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sympy/b17bed68-2653-4bb9-8b54-fa19eaeb18e3%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAHVvXxTr0NMn5w2ZKbbCTRdtZHp0Fq4H18vrHCFr8%2BK5KbO%2BbA%40mail.gmail.com.