11–20 of 27 posts
Are 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
Earlier quoted context omitted.
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.
It's not only the compatibility that is ugly. It's also that python 2 code has a couple of ugly warts, such as the forced arguments for super(). The only way I'm supporting python 2 with my libraries is by running 3to2 and pasteurize (future package) over the python 3 source code. 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…
Why did you point us to unofficial clone of the Subversion repository ?
And due to the fact that shlomif is doing his best to improve PysolFC in that "unofficial clone of the Subversion repository".
Earlier quoted context omitted.
It's not only the compatibility that is ugly. It's also that python 2 code has a couple of ugly warts, such as the forced arguments for super(). The only way I'm supporting python 2 with my libraries is by running 3to2 and pasteurize (future package) over the python 3 source code. 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…
I've been using 3.6 for some personal work and man are f-strings and ordered dicts wonderful. I don't want to go back.
Are 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'd expect backporting from 3 to 2 to be more of a pain than porting from 2 to 3.
You might have experience with both, but if not, this seems worth bearing in mind.
PySolFC (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…
Why did you point us to unofficial clone of the Subversion repository ?
Because there is really not much going on in the official repo? See for yourself: https://sourceforge.net/p/pysolfc/code/commit_browser And due to the fact that shlomif is doing his best to improve PysolFC in that "unofficial clone of the Subversion repository".
Earlier quoted context omitted.
It's not only the compatibility that is ugly. It's also that python 2 code has a couple of ugly warts, such as the forced arguments for super(). The only way I'm supporting python 2 with my libraries is by running 3to2 and pasteurize (future package) over the python 3 source code. 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…
I've been using 3.6 for some personal work and man are f-strings and ordered dicts wonderful. I don't want to go back.
Earlier quoted context omitted.
Because there is really not much going on in the official repo? See for yourself: https://sourceforge.net/p/pysolfc/code/commit_browser And due to the fact that shlomif is doing his best to improve PysolFC in that "unofficial clone of the Subversion repository".
Just to be clear, this is a fork (takeover?) of http://pysolfc.sourceforge.net , which is an approved fork of http://www.pysol.org/ .
There was not much activity regarding PySol and PySolFC in recent years. Shlomif is trying to change this.