I've had a couple of conversations recently that suggest it's high
time I posted this particular idea publicly, so here's my suggestion
for dealing with (or, more accurately, avoiding) the binary dependency
management problem for upstream distribution in the near term.
= Defining the problem =
Th
I was working from (clearly hazy) memory. Sorry for the red herring.
On 1 December 2013 09:10, Donald Stufft wrote:
> Hiding a release doesn’t hide it from the simple index, so installers will
> still find it.
>
> On Nov 30, 2013, at 4:59 PM, Richard Jones wrote:
>
> There is no way to mark a
Hiding a release doesn’t hide it from the simple index, so installers will
still find it.
On Nov 30, 2013, at 4:59 PM, Richard Jones wrote:
> There is no way to mark a release as "pre-release" but you can hide it from
> view which would prevent an installer discovering any files related to the
There is no way to mark a release as "pre-release" but you can hide it from
view which would prevent an installer discovering any files related to the
release. Log into PyPI and use the "releases" page for the project.
On 30 November 2013 22:05, anatoly techtonik wrote:
> hi, please cc
>
> i w
On 30 November 2013 11:05, anatoly techtonik wrote:
> hi, please cc
>
> i want to release some versions to pypi, but hide them from installing
> by explicitly marking as pre-release. i want to preserve versions
> numbering as 0.1, 0.2 according to semver.org point 4. is that
> possible?
No, I don
hi, please cc
i want to release some versions to pypi, but hide them from installing
by explicitly marking as pre-release. i want to preserve versions
numbering as 0.1, 0.2 according to semver.org point 4. is that
possible?
--
anatoly t.
___
Distutils-SI
