You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It works well but I'm having some interaction-problems.
django-pipeline imports 'concurrent.future' and in some cases 'futures' raises a exception in python2 way that it is not supported in python3 (two exceptions without brackets).
django-gulp gave me no problem with python3 but the fact that 'futures' is also installed in python3 makes some packages use the installed 'futures' instead of the standard library.
On Oct 29, 2016, at 12:48, Jorge Rodríguez-Flores Esparza [email protected] wrote:
Hi,
I'm using django-gulp in python 3.
It works well but I'm having some interaction-problems.
django-pipeline imports 'concurrent.future' and in some cases 'futures' raises a exception in python2 way that it is not supported in python3 (two exceptions without brackets).
django-gulp gave me no problem with python3 but the fact that 'futures' is also installed in python3 makes some packages use the installed 'futures' instead of the standard library.
It would be nice to make the 'futures' installation depending on the python version.
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hi,
I'm using django-gulp in python 3.
It works well but I'm having some interaction-problems.
django-pipeline imports 'concurrent.future' and in some cases 'futures' raises a exception in python2 way that it is not supported in python3 (two exceptions without brackets).
django-gulp gave me no problem with python3 but the fact that 'futures' is also installed in python3 makes some packages use the installed 'futures' instead of the standard library.
It would be nice to make the 'futures' installation depending on the python version.
Thanks.
The text was updated successfully, but these errors were encountered: