Re: Python 3 support

Fokko, as far as workflow goes I’m just asking if it’s ok to start merging PRs that only support 3.5+ after 1.9 “final” goes out. That would have two consequences: 1. avro-python3-1.9 would work with python3.4 as well as it ever has. 2. Maintenance releases of 1.9 would need to be cut from a 1.9-

Re: Python 3 support

Michael, after some careful thoughts I think it is too late to remove 3.4 support in Avro 1.9 since we're passed RC3. I've updated the tickets to target this for 1.10. Cheers, Fokko Op ma 6 mei 2019 om 10:32 schreef Driesprong, Fokko : > +1 from my side > > Thanks Michael for reviving this threa

Re: Python 3 support

+1 from my side Thanks Michael for reviving this thread again. Since 3.4 isn't officially supported anymore, I think it is save to drop support for Avro 1.9 as well to speed up the deprecation process. In practice it will still work against 3.4 until we start using breaking features such as type a

Re: Python 3 support

+1 On Sat, May 4, 2019, 2:37 PM sajuukk wrote: > +1 > > W dniu 04.05.2019 o 16:10, Michael A. Smith pisze: > > Hi, Avro devs, it's time to wake this thread up for a checkpoint. > > > > I glanced at pypi stats today and it looks like 3.4 downloads are usually > > below 1000. More importantly, Pyt

Re: Python 3 support

+1 W dniu 04.05.2019 o 16:10, Michael A. Smith pisze: Hi, Avro devs, it's time to wake this thread up for a checkpoint. I glanced at pypi stats today and it looks like 3.4 downloads are usually below 1000. More importantly, Python has already EOL'ed python 3.4. Do we want to consider python 3.4

Re: Python 3 support

Hi, Avro devs, it's time to wake this thread up for a checkpoint. I glanced at pypi stats today and it looks like 3.4 downloads are usually below 1000. More importantly, Python has already EOL'ed python 3.4. Do we want to consider python 3.4 support officially dropped as of the 1.9 release? That

Re: Python 3 support

Hi Michael, Ok, I think it's good idea to drop the Python 3.4 support after the last release of 3.4. We can show deprecation warnings before. By the way, this will also be a good opportunity for some refactoring. As for the Avro on Python 2.7, my approach would be just leave it as it is now and do

Re: Python 3 support

Hi, Piotr, Thanks for posting this for discussion. In my work projects we use Python 3.6, 3.7, and (cough) 2.7. So it won’t hurt me directly if Avro doesn’t support Python 3.4 anymore. However, avro-py3 is a library, so wide version support is appropriate in my opinion. Python still supports 3.4

Re: Python 3 support

Hi Michael and Fokko, I posted some notes today morning, but it was too late I guess. Isn't the decision to use Python 3.4 too conservative? 3.4 was released on 2014 and I strongly believe that we should be as up-to-date as possible. 3.4 is used by around 13% of users as shown by Scott Belden and

Re: Python 3 support

Hi Michael, Thanks for pointing out the Python versions. I'm fine with the suggestion of supporting 3.4 up to 3.7. I would also consider supporting from 3.5 onwards. Right now I've done some tests against 3.4 and that seems to run fine. I'm fine with adding the classifiers. Cheers, Fokko Op wo 3

Python 3 support

In comments to https://github.com/apache/avro/pull/347 it was suggested that we hold a vote to discuss which versions of Python 3 we consider officially supported. I assume we follow the Apache Voting Process for code modifications