When and how should we remove lang/py3?

[Michael Smith <mi...@smith-li.com>]

 Previous emails on this list have discussed the "why" questions. But when
and how should we go about it? Could 1.10 be the last avro release to
include avro-python3? This would allow us to play a little less ticket
tennis with folks reporting bugs (can you reproduce this in "the other"
python library?) and focus all our effort into one python implementation.

What do you think?

Re: When and how should we remove lang/py3?

["Michael A. Smith" <mi...@smith-li.com>]

Bringing this back up: I think avro and avro-python3 are mostly compatible,
so we really just need to invent a way to make people switch automatically.
We could almost have py3 install avro as a dependency. The thing is, both
packages are under the root namespace `avro`, so you can't trivially have
them both installed. Maybe we can publish both packages from the same
codebase, but have the py3 one give a deprecation warning.

WDYT?

On Sun, May 3, 2020 at 03:45 Driesprong, Fokko <fo...@driesprong.frl> wrote:

> Hi Mchael,
>
> Thank you for bringing this up. I agree, but I'm not sure how we're going
> to migrate the users to the avro package.
>
> Rijprojectnum_downloads
> 1
> avro
> 885838
> 2
> avro-python3
> 147313
>
> A quick query on bigquery, that contains all the pypi downloads shows that
> the python3 package is more popular. Maybe we should add a deprecation
> warning in 1.10.0?
>
> Cheers,
> Fokko
>
> The query:
> SELECT file.project, COUNT(*) AS num_downloads
> FROM `the-psf.pypi.downloads*`
> WHERE file.project IN ('avro-python3', 'avro')
>   -- Only query the last 30 days of history
>   AND _TABLE_SUFFIX
>     BETWEEN FORMAT_DATE(
>       '%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY))
>     AND FORMAT_DATE('%Y%m%d', CURRENT_DATE())
> GROUP BY file.project
>
>
>
>
>
> Op do 30 apr. 2020 om 14:20 schreef Michael Smith <mi...@smith-li.com>:
>
> >  Previous emails on this list have discussed the "why" questions. But
> when
> > and how should we go about it? Could 1.10 be the last avro release to
> > include avro-python3? This would allow us to play a little less ticket
> > tennis with folks reporting bugs (can you reproduce this in "the other"
> > python library?) and focus all our effort into one python implementation.
> >
> > What do you think?
> >
>

Re: When and how should we remove lang/py3?

["Driesprong, Fokko" <fo...@driesprong.frl>]

Hi Mchael,

Thank you for bringing this up. I agree, but I'm not sure how we're going
to migrate the users to the avro package.

Rijprojectnum_downloads
1
avro
885838
2
avro-python3
147313

A quick query on bigquery, that contains all the pypi downloads shows that
the python3 package is more popular. Maybe we should add a deprecation
warning in 1.10.0?

Cheers,
Fokko

The query:
SELECT file.project, COUNT(*) AS num_downloads
FROM `the-psf.pypi.downloads*`
WHERE file.project IN ('avro-python3', 'avro')
  -- Only query the last 30 days of history
  AND _TABLE_SUFFIX
    BETWEEN FORMAT_DATE(
      '%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY))
    AND FORMAT_DATE('%Y%m%d', CURRENT_DATE())
GROUP BY file.project





Op do 30 apr. 2020 om 14:20 schreef Michael Smith <mi...@smith-li.com>:

>  Previous emails on this list have discussed the "why" questions. But when
> and how should we go about it? Could 1.10 be the last avro release to
> include avro-python3? This would allow us to play a little less ticket
> tennis with folks reporting bugs (can you reproduce this in "the other"
> python library?) and focus all our effort into one python implementation.
>
> What do you think?
>