Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Add Plyara name and link to list #210
Conversation
|
No problem. We dropped 2 and release a 3-only version 2.0.0 on Feb 1, 2019. |
|
@takluyver Opinion on adding another entry to the schedule? |
|
@CAM-Gerlach Should be fine, see https://github.com/python3statement/python3statement.github.io#add-timeline-information for info. |
|
@hugovk Thanks, I do know how to do it :) (see #141 and #209 ) What I was asking was (as a followup to what I brought up with @takluyver previously) whether it was worthwhile to do for a project that doesn't really have the same order of magnitude of either direct users or other projects dependent on it as almost every other package listed in the schedule section, particularly given one minimal schedule line takes up nearly the space that 4-5 logos do on the list above, and at much higher density. |
|
I have some concern over how big the timeline is getting (#46), but we haven't figured out any neat solution yet, and I don't want to randomly stop adding projects that want to be listed on there. So I'm happy for it to keep growing until someone has a better idea. ;-) |
81cdf04
into
python3statement:master
|
Thanks |
|
@takluyver , @utkonos did not have the opportunity to double-check and approve the timeline, particularly since I hadn't yet been provided the full information I'd requested and had to make some assumptions. Again, @utkonos , what I've been asking is
As (what I thought was) a temporary stopgap, I put in the date of your 1.2.0 release, listed as the first one of the community maintained |
|
Sorry, I'm trigger happy on the merge button today. Feel free to make another PR if it needs changing. |
|
Np. @utkonos , just lmk if it needs any changes and I'll make them in a new PR. Thanks. |
|
I think I have answered this already. Here it is again: version 2.0.0 that
we released on February 1 was a rewrite of the project in python 3. We
decided to drop 2 support at that time.
…On Sat, May 4, 2019, 06:50 CAM Gerlach ***@***.***> wrote:
@utkonos <https://github.com/utkonos> did not check and approve the
timeline!
Again, @utkonos <https://github.com/utkonos> , what I've been asking you
is
how long have you supported Python 3 *before* you dropped Python 2
support, or with what approx release?
As (what I thought was) a temporary stopgap, I put in the date of your
1.2.0 release, listed as the first one of the community maintained plyara,
reasoning that was when a version was officially released fully supporting
Python 3. Is that correct? Also, in addition to my previous question, is
2020-01-01 fine as an end date for 2.x for now, or do you have something
more specific in mind? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#210 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVFVOYMMMX23YEWSCRETL3PTVTALANCNFSM4HKXOWQQ>
.
|
Ah, that's what I was looking for; thanks @utkonos . I'll just nix the |
Fixes #180 . @utkonos please review and confirm.
I could add you to the schedule, but I'll need to know more specifics and it seems its only used for larger projects with a large number of users or back-dependencies, since it takes up a lot of space on the page.