Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install futures only in python2 #9

Closed
jorrete opened this issue Oct 29, 2016 · 2 comments
Closed

Install futures only in python2 #9

jorrete opened this issue Oct 29, 2016 · 2 comments

Comments

@jorrete
Copy link

jorrete commented Oct 29, 2016

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.

@beaugunderson
Copy link
Owner

good catch! i'll implement that :)


Sent from my phone.

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.

@beaugunderson
Copy link
Owner

hey @jorrete--sorry this took two years but this is fixed in 4.0.1!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants