Re: pypi2port and python supported versions

2017-04-25 Thread db
On 24 Apr 2017, at 19:10, Mojca Miklavec wrote: > In short: > - we probably need a bit more effort to bring all modules to 3.6 > - we probably need to review which entries may go from py-graveyard > and potentially change the others to default to 36 rather than 34 > - we certainly need to upgrade

Re: pypi2port and python supported versions

2017-04-24 Thread db
On 22 Apr 2017, at 23:17, Mojca Miklavec wrote: > 27 35 36 for sure. > 34 has not yet seen any active removal, so it's the bordercase, > probably not worth putting into new ports. These are the EoS dates: 3.3 2017-09 3.4 2019-03 I agree on 33, but 34? Why don't we also leave 35 out?

pypi2port and python supported versions

2017-04-22 Thread db
I used pypi2port to get the basic porfile for stem module, emended and submitted it in #54014. I was told to remove py34 and add py36. pypi2port usually writes 27 34 35 in python.versions, although 33 is still supported (now for a couple of months) and 36 is already released. What is the genera