'rc' version (like 1.0a1 or 1.0rc4), then pip won't install it by default ...
it will only install 'released' versions (like 1.0 or 1.0.1).
Adding the --pre option tells pip you actually do want the pre-release version.
So:
pip install --pre directory-caching
>
[snip]
>
> - Benjamin
--
Dave Hein
--
https://mail.python.org/mailman/listinfo/python-list
On Sunday, April 5, 2015 at 8:01:22 PM UTC-5, Steven D'Aprano wrote:
> On Mon, 6 Apr 2015 06:38 am, Dave Hein wrote:
>
> > I would like to distribute a python package with different code for
> > Python 2.* than for Python 3.*. (Mostly this is because of different
>
On Monday, April 6, 2015 at 12:47:05 AM UTC-5, Stefan Behnel wrote:
> Dave Hein schrieb am 05.04.2015 um 22:38:
> > I would like to distribute a python package with different code for
> > Python 2.* than for Python 3.*. (Mostly this is because of different
> > un
On Sunday, April 5, 2015 at 10:28:55 PM UTC-5, Mark Lawrence wrote:
> On 05/04/2015 21:38, Dave Hein wrote:
> > I would like to distribute a python package with different code for
> > Python 2.* than for Python 3.*. (Mostly this is because of different
> > unicode string han
location.
Is that at all possible? Is there some install time hook that lets me
supply custom installation code?
--
Dave Hein
--
https://mail.python.org/mailman/listinfo/python-list
