I recommend submitting a DNW (Does Not Work) rating for any games that don't support Python 3, if you feel that way. I think that when people see that supporting Python 3 will get them more players, it'll get the message across.
I propose we make this a formal rule, which means that you can vote to disqualify Python 2 entries from the first competition in 2020 (which would be Pyweek 29, by my reckoning).
Isn't Pyweek supposed to be a fun, supportive environment? Marking perfectly good entries with DNW just because they're in Python 2 seems like a dick move to me.
For what it's worth when I mark an entry as DNW it's not meant to be a criticism. I do it for other entries that don't have bugs, for instance if they use a library I spend 20 minutes trying to install and it still won't work. I have a limited amount of time to make each game work, so the truth is the more dependencies you have the more likely it won't happen for me, though I do always try. I'm fine with people using exotic libraries as long as they understand that fewer people will be able to play it. Letting them know I was in that category will help them make an informed decision. That's how I see it anyway.
I developed with python 2 for the last one and got a lot of comments that asked me to move to python 3. So this time I did. I'm hoping that's the same with most people
> I propose we make this a formal rule, which means that you can vote to
disqualify Python 2 entries from the first competition in 2020 (which
would be Pyweek 29, by my reckoning).
Buffalo974 on 2018/08/03 22:05
Cosmologicon on
2018/08/22 02:45:
I recommend submitting a DNW (Does Not Work) rating for any games that don't support Python 3, if you feel that way. I think that when people see that supporting Python 3 will get them more players, it'll get the message across.Of the survey responses it seems most respondents went with the versions of Python that are supported, which are currently 2.7 and 3.4 to 3.7.
I propose we make this a formal rule, which means that you can vote to disqualify Python 2 entries from the first competition in 2020 (which would be Pyweek 29, by my reckoning).
LeopardShark on
2018/10/19 16:30:
Yes, I like this idea!
AnthonyB on
2018/10/21 00:11:
Isn't Pyweek supposed to be a fun, supportive environment? Marking perfectly good entries with DNW just because they're in Python 2 seems like a dick move to me.DNW doesn't affect the scores, but I know what you mean - it's a bit ungenerous to those who have spent a week making a game for you.
It's a stronger case once Python 2 is officially unsupported, especially if we formally put it in the rules.
Cosmologicon on
2018/10/21 01:00:
For what it's worth when I mark an entry as DNW it's not meant to be a criticism. I do it for other entries that don't have bugs, for instance if they use a library I spend 20 minutes trying to install and it still won't work. I have a limited amount of time to make each game work, so the truth is the more dependencies you have the more likely it won't happen for me, though I do always try. I'm fine with people using exotic libraries as long as they understand that fewer people will be able to play it. Letting them know I was in that category will help them make an informed decision. That's how I see it anyway.
gummbum on
2018/10/21 02:24:
I support Python 2 and 3. It's not that hard.
gizmo_thunder on
2018/10/28 01:46:
I developed with python 2 for the last one and got a lot of comments that asked me to move to python 3. So this time I did. I'm hoping that's the same with most people
stOneskull on
2019/03/19 07:28:
it may as well be for 2020 if it happens.. but not this year
Buffalo974 on
2019/09/19 09:26:
up ?