PySolFC – A collection of Solitaire games for Python
1–10 of 27 posts
Re: PySolFC – A collection of Solitaire games for Python
#2Unfortunately, PySolFC is getting old. To bring it up to date and make PySolFC compatible with modern operating systems, it has to be ported to Python 3 first — so we desperately need Python programmers.
JOIN PORTING EFFORTS AT: https://github.com/shlomif/PySolFC
You can also help by spreading the word. After we finish porting PySolFC to Python 3, new features will be added, we also aim to refresh the app’s look.
Re: PySolFC – A collection of Solitaire games for Python
#3PySolFC (previously known as PySol) is a multi-platform collection of over 1000 solitaire card (and not only) games with a rich feature set that can rival commercial solitaire packages. Unfortunately, PySolFC is getting old. To bring it up to date and make PySolFC compatible with modern operating systems, it has to be ported to Python 3 first — so we desperately need Python programmers. JOIN PORTING EFFORTS AT: https…
Re: PySolFC – A collection of Solitaire games for Python
#4edit: Current title seems good.
Re: PySolFC – A collection of Solitaire games for Python
#5PySolFC (previously known as PySol) is a multi-platform collection of over 1000 solitaire card (and not only) games with a rich feature set that can rival commercial solitaire packages. Unfortunately, PySolFC is getting old. To bring it up to date and make PySolFC compatible with modern operating systems, it has to be ported to Python 3 first — so we desperately need Python programmers. JOIN PORTING EFFORTS AT: https…
Sweet! I'd love to contribute. There doesn't seem to be a contribution guide or timeline in the repo. I'd suggest adding a list of modules which require refactoring.
Re: PySolFC – A collection of Solitaire games for Python
#6Python six is a library that might help with targeting both
Re: PySolFC – A collection of Solitaire games for Python
#7Are you actually planning to lose Python 2 compatibility is porting to 3? It might make more sense to keep both if you can, if only because if you give up Python 2, there'll be an intermediate period where the code won't run anywhere. Python six is a library that might help with targeting both
I think your advice might be well intended, but if followed will end up with an overloaded dev. and no new progress being made (and all that for the five guys who still don't have py3 installed)
Sorry to sound harsh, but I wish someone had told me that advice when I accepted to backport a py3 package to py2
Re: PySolFC – A collection of Solitaire games for Python
#8Are you actually planning to lose Python 2 compatibility is porting to 3? It might make more sense to keep both if you can, if only because if you give up Python 2, there'll be an intermediate period where the code won't run anywhere. Python six is a library that might help with targeting both
Code that supports both py2 and py3 is often ugly and a pain to work with. I think your advice might be well intended, but if followed will end up with an overloaded dev. and no new progress being made (and all that for the five guys who still don't have py3 installed) Sorry to sound harsh, but I wish someone had told me that advice when I accepted to backport a py3 package to py2
I don't believe 2-3 compatibility must be ugly (though it certainly can be), but I'm glad you believe what you said. If that makes sense.
Re: PySolFC – A collection of Solitaire games for Python
#9Re: PySolFC – A collection of Solitaire games for Python
#10Earlier quoted context omitted.
Code that supports both py2 and py3 is often ugly and a pain to work with. I think your advice might be well intended, but if followed will end up with an overloaded dev. and no new progress being made (and all that for the five guys who still don't have py3 installed) Sorry to sound harsh, but I wish someone had told me that advice when I accepted to backport a py3 package to py2
Wow! The community has turned a corner! :-) I don't believe 2-3 compatibility must be ugly (though it certainly can be), but I'm glad you believe what you said. If that makes sense.
I really don't want to actually have source code that works on both, it's a pain to maintain. Although the future library should make it a lot nicer, but you still need a lot of ugly from __future__ imports as well.