yt-4.0 branch and python 3-only features
Hi folks, Is it now safe to use Py3-only features? If so, are we setting Python 3.6 to be the minimum version? YTEP-0033 doesn't note specifically. The specific thing I want to use (using native metaclasses instead of @add_metaclass) isn't Python 3.6 only, but I thought it was as good a time as any to ask. -Matt
It looks like we're still running python2.7 tests on the yt-4.0 branch, at least on travis: https://github.com/yt-project/yt/blob/yt-4.0/.travis.yml. I'd accept a PR that removed the python2.7 and python3.4 tests (I think next time we merge with master the 3.4 tests will go away, they're already gone on master). I don't think we've decided the minimum python3 version for the yt 4.0 release. For what it's worth, Python3.5 won't go EOL until five years after its release, which means September 2020, so I'd at least want to have a discussion before dropping support for it out of hand, as users might still be on Python3.5 on LTS distros when we release yt 4.0. -Nathan On Tue, Jul 17, 2018 at 10:50 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Is it now safe to use Py3-only features? If so, are we setting Python 3.6 to be the minimum version? YTEP-0033 doesn't note specifically.
The specific thing I want to use (using native metaclasses instead of @add_metaclass) isn't Python 3.6 only, but I thought it was as good a time as any to ask.
-Matt
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
a perhaps naive question, but for someone like me who has never used metaclasses python, can you give an example of why it is useful? (in general, and in yt) Mike On Tue, Jul 17, 2018 at 11:51 AM Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Is it now safe to use Py3-only features? If so, are we setting Python 3.6 to be the minimum version? YTEP-0033 doesn't note specifically.
The specific thing I want to use (using native metaclasses instead of @add_metaclass) isn't Python 3.6 only, but I thought it was as good a time as any to ask.
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
-- Michael Zingale Associate Professor Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
Hi Mike and Nathan, Awesome, thanks Nathan! I will issue a PR once I figure out what other steps to take. Mike, the main thing I want to do is get rid of our usage of six.add_metaclass. We use metaclasses mostly to "autoregister" things, so that if something is defined it sticks itself into a dictionary we can call. But, the metaclass syntax changed with Python 3, so we've had to use the compatibility layer, which is a bit ugly and kind of messes with any kind of static analysis. Getting rid of it will make things a bit cleaner. -Matt On Tue, Jul 17, 2018 at 11:07 AM Michael Zingale < michael.zingale@stonybrook.edu> wrote:
a perhaps naive question, but for someone like me who has never used metaclasses python, can you give an example of why it is useful? (in general, and in yt)
Mike
On Tue, Jul 17, 2018 at 11:51 AM Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Is it now safe to use Py3-only features? If so, are we setting Python 3.6 to be the minimum version? YTEP-0033 doesn't note specifically.
The specific thing I want to use (using native metaclasses instead of @add_metaclass) isn't Python 3.6 only, but I thought it was as good a time as any to ask.
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
Hi, just to clarify, I meant I would issue a PR that might include Py3-only functionality, but I won't do Py3.6-only functionality. Apologies for the confusion! On Tue, Jul 17, 2018 at 11:12 AM Matthew Turk <matthewturk@gmail.com> wrote:
Hi Mike and Nathan,
Awesome, thanks Nathan! I will issue a PR once I figure out what other steps to take.
Mike, the main thing I want to do is get rid of our usage of six.add_metaclass. We use metaclasses mostly to "autoregister" things, so that if something is defined it sticks itself into a dictionary we can call. But, the metaclass syntax changed with Python 3, so we've had to use the compatibility layer, which is a bit ugly and kind of messes with any kind of static analysis. Getting rid of it will make things a bit cleaner.
-Matt
On Tue, Jul 17, 2018 at 11:07 AM Michael Zingale < michael.zingale@stonybrook.edu> wrote:
a perhaps naive question, but for someone like me who has never used metaclasses python, can you give an example of why it is useful? (in general, and in yt)
Mike
On Tue, Jul 17, 2018 at 11:51 AM Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Is it now safe to use Py3-only features? If so, are we setting Python 3.6 to be the minimum version? YTEP-0033 doesn't note specifically.
The specific thing I want to use (using native metaclasses instead of @add_metaclass) isn't Python 3.6 only, but I thought it was as good a time as any to ask.
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale github: http://github.com/zingale
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
participants (3)
-
Matthew Turk -
Michael Zingale -
Nathan Goldbaum