Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Plyara name and link to list #210

Merged
merged 2 commits into from
May 4, 2019

Conversation

CAM-Gerlach
Copy link
Contributor

@CAM-Gerlach CAM-Gerlach commented May 3, 2019

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.

@utkonos
Copy link

utkonos commented May 4, 2019

No problem. We dropped 2 and release a 3-only version 2.0.0 on Feb 1, 2019.

@CAM-Gerlach
Copy link
Contributor Author

@takluyver Opinion on adding another entry to the schedule?

@hugovk
Copy link
Contributor

hugovk commented May 4, 2019

@CAM-Gerlach
Copy link
Contributor Author

CAM-Gerlach commented May 4, 2019

@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.

@takluyver
Copy link
Member

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. ;-)

@takluyver takluyver merged commit 81cdf04 into python3statement:master May 4, 2019
@takluyver
Copy link
Member

Thanks

@CAM-Gerlach
Copy link
Contributor Author

CAM-Gerlach commented May 4, 2019

@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

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.

@takluyver
Copy link
Member

Sorry, I'm trigger happy on the merge button today. Feel free to make another PR if it needs changing.

@CAM-Gerlach
Copy link
Contributor Author

Np. @utkonos , just lmk if it needs any changes and I'll make them in a new PR. Thanks.

@utkonos
Copy link

utkonos commented May 4, 2019 via email

@CAM-Gerlach
Copy link
Contributor Author

CAM-Gerlach commented May 4, 2019

version 2.0.0 that we released on February 1 was a rewrite of the project in python 3

Ah, that's what I was looking for; thanks @utkonos . I'll just nix the Python 2 and 3 support component entirely, then. Sorry for the confusion.

@CAM-Gerlach CAM-Gerlach deleted the add-plyara branch May 7, 2019 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add plyara
4 participants