bennr01

@drallensmith regarding the QuantifiedCode issues in #97: *Avoid using "non-Pythonic" variable names* in `distributed.py`: I think we can remove `saw_EOFError` completely. If i recall correctly, it is no longer required...

@drallensmith HyperNEAT looks interesting. I just read trough a paper and the [HyperNEAT user page](http://eplex.cs.ucf.edu/hyperNEATpage/HyperNEAT.html) and i think i now understand the concept. The problem is integrating it into neat-python....

We could also add the ability to dump a network into a dictionary which only contains strings and number and write a function to create a network from this dictionary....

Hi, I am the guy who wrote `neat.distributed` a couple of years ago. The old version tried to utilize `multiprocessing`'s distributed functionality, but (as you can see) it has some...

> In fact I'm trying to optimize a function that takes a few minutes to complete, so running this distributed would really speed this up a lot so I don't...

OK, i just tested it with `3.6` (via *run with Python 3.6*) and was not able to replicate it. After switching back to `2.7` the bug was **still observed**. So...

> 54 daze left. It will always live on in my heart as the one true version of python. Though i suppose I should start porting to py3 soon... Also,...

@d0pa If you have any questions, just ask. I wont bite you, but i may trap you in a 4-dimensional space 😄 @drallensmith I opened the issues tab for my...

@drallensmith yes, exactly.

**Small suggestion:** dropping py2 support is technically a backwards incompatible api change. When following [semantic versioning](https://semver.org/), this should be indicated by a major version bump. `pyfilesystem2` currently has the major...