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

_______________________________________________
yt-dev mailing list -- yt-dev@python.org
To unsubscribe send an email to yt-dev-leave@python.org