I'd like to help with this Python 2 -> 3 migration if possible. We're nearly
halfway through 2020 now -- is there currently anything stopping us from doing
this migration at the moment? Is this the right time to do so?
On 2019/10/05 02:11:24, Valentyn Tymofieiev wrote:
> On Fri, Oct 4, 2019
On Fri, Oct 4, 2019 at 11:02 AM Robert Bradshaw wrote:
> Thanks for holding this vote. Note that this is a pledge to remove
> support sometime in 2020, but no promises as to whether that will be
> January or December (though I hope sooner rather than later)
Right.
>
Valentyn, did you want to
Thanks for holding this vote. Note that this is a pledge to remove
support sometime in 2020, but no promises as to whether that will be
January or December (though I hope sooner rather than later).
Valentyn, did you want to go ahead and make a PR adding Apache Beam to
the python3statement page?
As suggested and enthusiastically supported by several folks in this
thread, I will send a vote to sign a pledge on http://python3statement.org
on behalf of Apache Beam to discontinue Python 2 support in or before 2020.
The motivation for signing the pledge is:
- to provide another signal to Beam
Re feedback collection, we already print a message:
"You are using Apache Beam with Python 2. New releases of Apache Beam will
soon support Python 3 only."
When users run Python 2 pipelines. This might be a good place to provide
additional info along with a place to send feedback (probably user@).
Thanks a lot for sharing your thoughts, I completely agree that we need to
minimize the burden on our users as much as possible. Especially in this
case when we are offering a robust python 3 solution just now. However I do
share the same concerns related to dependencies and tool chains, It will
Granted that we just have finalized the Python 3 support, we should
allow time for it to mature and for users to make the switch.
Oh, and one more thing, I think it'd make sense for Apache Beam to
sign https://python3statement.org/. The promise is that we'd
discontinue Python 2 support *in*
Oh, and one more thing, I think it'd make sense for Apache Beam to
sign https://python3statement.org/. The promise is that we'd
discontinue Python 2 support *in* 2020, which is not committing us to
January if we're not ready. Worth a vote?
On Thu, Sep 19, 2019 at 3:58 PM Robert Bradshaw wrote:
Exactly how long we support Python 2 depends on our users. Other than
those that speak up (such as yourself, thanks!), it's hard to get a
handle on how many need Python 2 and for how long. (Should we send out
a survey? Maybe after some experience with 2.16?)
On the one hand, the whole ecosystem
Hi all,
I had a read through this thread in the archives. It occurred before I
joined the mailing list, so I hope that this email connects up with the
thread properly for everyone.
I'd like to respond to the following points:
I believe we are referring to two separate things with support:
> -
On Sat, Jun 22, 2019 at 1:09 AM Valentyn Tymofieiev wrote:
>
> On Tue, Jun 18, 2019 at 2:01 PM Ahmet Altay wrote:
>>
>> Thank you for the update, very helpful. It might be worthwhile to share a
>> version of this with user mailing list after 2.14.
>
>
> I think so too, we can send an update to
On Tue, Jun 18, 2019 at 2:01 PM Ahmet Altay wrote:
> Thank you for the update, very helpful. It might be worthwhile to share a
> version of this with user mailing list after 2.14.
>
I think so too, we can send an update to user list when 2.14.0 is
released.
> Remaining question for me is:
Thank you for the update, very helpful. It might be worthwhile to share a
version of this with user mailing list after 2.14.
Remaining question for me is: There is no plan for an LTS release
currently. Would it make sense for us to target one after known remaining
issues are mostly fixed. What
To give a better understanding where we are w.r.t. Python 3, I'd like to
give a quick overview of the recent work that has been happening in Beam
community to support Python 3, and to summarize the current status of this
effort.
Current status:
1.
Beam 2.11.0 was the first release that
I like the update Ismaël referenced [1], I think we should prepare a
similar update for Beam users. I would propose the following:
- Designate last LTS release that we will have in 2019 to be the last LTS
release with Python 2 support.
- Add a Beam-specific deprecation warning on Python 2 starting
Sounds good.
On Fri, Jun 7, 2019 at 8:28 PM Ahmet Altay wrote:
> I agree with you. A more recent LTS release with python 2 support will be
> good. Cost of maintaining python 2 support is also fairly low (maybe zero
> actually besides keeping some pre-existing compatibility code).
>
> I believe
I agree with you. A more recent LTS release with python 2 support will be
good. Cost of maintaining python 2 support is also fairly low (maybe zero
actually besides keeping some pre-existing compatibility code).
I believe we are referring to two separate things with support:
- Supporting existing
I don't think the second release with robust/recommended Python 3
support should be the last release with Python 2 support--that is
simply not enough time for people to migrate. (Look at how long it
took us...) It does make a lot of sense to at least have one LTS
release with support for both.
I agree with the sentiment on this thread. Our priority needs to be
offering good python 3 support that we can comfortably recommend users to
switch. Progress on that so far has been promising and I do anticipate that
we will reach there in the near future.
My proposal would be, once we reach to
We can support Python 2 for some time in 2020, but, we should target a date
no later than 2020 to drop support.
If we do plan to drop support for Python 2 in 2020, we should sign the
Python 3 statement[1], declaring that we will "drop support for Python 2.7
no later than 2020".
In addition to the
Until Python 3 support for Beam is officially out of beta and
recommended, I don't think we can tell people to stop using Python 2.
Given that 2020 is just over 6 months away, that seems a short
transition time, so I would guess we'll have to continue supporting
Python 2 sometime into 2020.
A
Python 2 won't be maintained after 2020 [1]. I was wondering what will
be our (Beam) plan for this. Other projects [2] have started to alert
users that support will be removed so maybe we should decide or policy
for this too.
[1] https://pythonclock.org/
[2]
22 matches
Mail list logo
