Throwing away virtualenv is actually best way to get problems (unless you're working with solutions like docker or vagrant).
Virtualenv makes easy to check that you really do have only certain packages, certain versions and they won't generate any sudden surprises.
On Thu, 13 Aug 2015 04:27:02 -0700 (PDT)
durir...@gmail.com wrote:
> I use no virtualenv, to throw away solutions in that direction.. (didn't
> wanna to go hard first time).
> *pip* is only installed in 3.2, so that wasn't the problem. I've solved the
> problem right now, but after an hour of trial and error, I think the only
> think was to do *--upgrade wheel*. Is was just the problem of that package.
> >> Searching about the error, it looks like I just have to install *wheel*.
> >> However, when I run the command *sudo pip install wheel* (*pip* is
> >> installed under *Python3*):
> >> Requirement already satisfied (use --upgrade to upgrade): wheel in
> >> /usr/local/lib/python3.2/dist-packages
> >>
> >> So, seeing that I can just going, I retry the package install and... get
> >> the same error: "*invalid command 'bdist_wheel'"*. Anyone could tell me
> >> what is going on? Is my first time doing a reusable app.
> >>
> >>
>
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
django-users...@googlegroups.com.
> To post to this group, send email to
django...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/django-users.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/cff1f3fe-c0e0-4b0a-a135-ef87f70e0113%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
--
Jani Tiainen