Open nbro opened 3 years ago
unfortunately -e does not support 2to3.
@fmder So, what's your approach to developing Deap in Python 3?
I'm also having problems caused by 2to3.
I'm rewriting the whole thing in python3, but that take way more time than I have 😞
I am having exactly same problem. even I am using python 3.10
what should we do to get rid pf this problem?
I was having problem with installing deap 1.3.1 initially but it solved after demoting the setup tools version to 58.0.0
pip is 22.1.1 version
+1
I forked deap, cloned my fork and I tried to install the cloned version with
python setup.py install
inside a conda environment with Python 3.7. Then I try to run an example, even with just the importfrom deap import base
, and I get the errorThis is, of course, due to the fact that deap is not written for 3.7, as can be seen here, where that syntax is not supported in Python 3.7. As far as I understand, deap uses the option
use_2to3=True
to convert this code written in Python 2 to Python 3 during the installation, however, either if I install my cloned version withpython setup.py install
orpip install -e .
, this option is not applied, so I cannot run the code in editable mode.So, what's your approach to edit/develop deap in Python 3? I would like to change something in deap (i.e. add a feature), but I'm not sure what's the right approach here.
(By the way, you may consider not supporting Python 2 anymore, given it's officially not supported by Python developers anymore: apparently, you have already been discussing this: https://github.com/DEAP/deap/pull/408. Deap is mainly used for research and nobody in research is probably using Python 2 anymore. I would really suggest that a new version of Deap should be rewritten in Python 3 so that we can get rid of all this useless burden.)