It was written that run
{{{
pip install -r py3.txt
}}}
i am running same on my mac OS but it always show problems in installing
`pylibmc` and `libmemcached ` to fix that i ran
{{{
brew install libmemcached
pip3 install -r py3.txt
}}}
because there was some python3 dependencies in it
so think that should be mentioned in docs that if its not installed by
`pip` then try using `pip3`
--
Ticket URL: <https://code.djangoproject.com/ticket/27876>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => invalid
Comment:
It looks like your virtualenv wasn't activated when you ran `pip install
...`.
--
Ticket URL: <https://code.djangoproject.com/ticket/27876#comment:1>
* status: closed => new
* resolution: invalid =>
Comment:
I've run into this bug as well, and I definitely am in my py3 virtualenv.
{{{
(django) SensitiveDependence:django phildini$ which python3
/Users/phildini/.virtualenvs/django/bin/python3
}}}
I was coming here to see if I should file a bug and found this one. I note
that we already call out windows in the `requirements/py3.txt` file, so it
feels like there's precedent for special-casing OS's.
Is the correct approach here to update the docs, or skip these tests on
mac, or do nothing?
--
Ticket URL: <https://code.djangoproject.com/ticket/27876#comment:2>
* cc: Tim, graham (removed)
Comment:
I'm not a mac OS user so I can't say for sure what the issue is here. What
does "it always show problems in installing pylibmc and libmemcached"
mean? My guess is that the equivalent of `libmemcached-dev` (Debian
package) isn't installed. ([https://stackoverflow.com/questions/9070218
/error-when-trying-to-install-pylibmc-on-mac-osx-lion related
StackOverflow]). I think it's not Django's job to document the
requirements of third-party packages. I'd rather enhance
[http://sendapatch.se/projects/pylibmc/install.html pylibmc's install
instructions] if needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/27876#comment:3>
* status: new => closed
* resolution: => invalid
Comment:
Feel free to propose some patch for Django's docs if my analysis isn't
correct.
--
Ticket URL: <https://code.djangoproject.com/ticket/27876#comment:4>