Python 3.7 requirement

[yarden]

I've noticed setup.py requires exactly Python version 3.7 (not higher or lower). Is that correct? It seems like too stringent a requirement. Many conda builds of Python framework for Mac OS X still ship Python 3.5. Is this more flexible than setup.py suggests? Thank you!

update:
I get this error:

  File "core/KappaSnapshot.py", line 20
    self._file_name: str
                   ^
SyntaxError: invalid syntax

with Python 3.5. I'm not familiar with the new typing features (which make Python look like OCaml). But is there really a typing syntax that is backwards incompatible between Py 3.5 and Py 3.7? It seems that there is (based on this: https://stackoverflow.com/questions/51789120/type-hints-syntax-error-on-python-3-5). If so, Python is officially the worst language on the planet since Python 3 was introduced...

In any case, all this typing stuff seems really excessive for KappaSnapshot.py. All the core part of the package is doing is parsingstrings with very simple regular expressions. I really doubt that typing buys anything in terms of speed but it makes the code way more complicated. Upgrading to 3.7 turns out to be a major pain because the default Python framework builds for Mac OS X (which are necessary to make matplotlib work - another way in which Python is broken) seem to be Python 3.5.

update 2: I managed to upgrade to Python 3.7 without breaking most of my packages and now it works. I hereby rename this issue "How I Learned to Stop Worrying and Love Python 3 Even Though It's Broken"

[hmedina]

Yes, the new typing system is the sole reason for the requirement of Python 3.7+ I don't know if there's much gained (e.g. the compiler behaves better?) from the user side, but from the development side, it made my life SO much easier. The base classes look simple enough, but the scrips can get pretty opaque (specially going into visualization where the codebase is larger...). I'm not planning on stripping out the typing system for backwards compatibility. In my Windows + WSL experience, compiling Python from source is not a significant burden. I'd rather post instructions and required packages under Ubuntu/WSL for that.

…

On Sat, May 11, 2019, 14:28 Yarden Katz ***@***.***> wrote: Reopened #2 <#2>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMD2SIJSRSIGK4W6JIKNH3PU4F5RANCNFSM4HMIWKBQ> . On Sat, May 11, 2019, 14:28 Yarden Katz ***@***.***> wrote: Reopened #2 <#2>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMD2SIJSRSIGK4W6JIKNH3PU4F5RANCNFSM4HMIWKBQ> .

[hmedina]

now it works

Ok, I'm closing the ticket then.

[hmedina]

On the note of Python... yeah... I remember the troubles of trying to get Numpy under Windows in the dark ages before the WSL, and then bam! It-just-works™️

[yarden]

Thanks Hector! Makes sense, I didn't appreciate the complexity of the rest of the code. Anyhow, the base functionality works great and saves me a great deal of time - thank you.