Paul Moore wrote:
FWIW, it looks like file:myserver/share/WINDOWS/clock.avi is how
you'd refer to \\myserver\share\WINDOWS\clock.avi.
Where did you get that from? According to this it's wrong:
http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx
It should be
file://
On 9 August 2014 18:50, Donald Stufft wrote:
> Does: file:///c:/WINDOWS/clock.avi work?
Never mind, it's my mistake. Reading the docs more closely, "Convert
the path component path from a percent-encoded URL to the local syntax
for a path. This does not accept a complete URL." (Note that second
s
> On Aug 9, 2014, at 1:41 PM, Paul Moore wrote:
>
> On 9 August 2014 17:02, Donald Stufft wrote:
>> To be clear, the direct reference is mostly for use in the install_requires.
>> On the CLI pip can still just take a path to a file or whatever. This feature
>> is intended to replace dependency_
On 9 August 2014 17:02, Donald Stufft wrote:
> To be clear, the direct reference is mostly for use in the install_requires.
> On the CLI pip can still just take a path to a file or whatever. This feature
> is intended to replace dependency_links in a way that people can use
> them for private pack
> On Aug 9, 2014, at 4:26 AM, Paul Moore wrote:
>
> On 8 August 2014 22:53, Donald Stufft wrote:
>> Direct references
>> =
>>
>> Some automated tools may permit the use of a direct reference as an
>> alternative to a normal version specifier. A direct reference consists of
>> t
On 8 August 2014 22:53, Donald Stufft wrote:
> Direct references
> =
>
> Some automated tools may permit the use of a direct reference as an
> alternative to a normal version specifier. A direct reference consists of
> the specifier ``@`` and an explicit URL.
>
> Whether or not dir
