On 31 October 2017 at 23:53, Nick Coghlan wrote:
> On 31 October 2017 at 22:49, Jeremy Stanley wrote:
>
>> On 2017-10-31 16:25:08 +1000 (+1000), Nick Coghlan wrote:
>> > Ideally we'd be recommending
>> >
On 31 October 2017 at 22:49, Jeremy Stanley wrote:
> On 2017-10-31 16:25:08 +1000 (+1000), Nick Coghlan wrote:
> > Ideally we'd be recommending
> > https://devpi.net/docs/devpi/devpi/stable/%2Bd/index.html to folks
> looking
> > to develop a robust pre-release artifact testing
On 2017-10-31 13:09:34 + (+), Thomas Kluyver wrote:
[...]
> If anyone wants to adapt the code to use in other tools, it's
> here:
>
> https://github.com/takluyver/flit/blob/ca08119/flit/inifile.py#L63-L108
[...]
Thanks for the pointer! That would make for a really great
stand-alone
On Tue, Oct 31, 2017, at 12:49 PM, Jeremy Stanley wrote:
> Do the two share enough common code for successful uploading to a
> devpi instance to be indicative of whether PyPI will accept or
> reject on the grounds of, e.g., invalid trove classifiers (this one
> in particular has been the most
On 2017-10-31 16:25:08 +1000 (+1000), Nick Coghlan wrote:
> Ideally we'd be recommending
> https://devpi.net/docs/devpi/devpi/stable/%2Bd/index.html to folks looking
> to develop a robust pre-release artifact testing workflow.
>
> While we mention it a couple of times on packaging.python.org
On 31 October 2017 at 03:41, Toshio Kuratomi wrote:
> When we locked down pypi to prevent uploading an sdist to overwrite a
> previous I remember that some people wanted a brief window to check
> for brown paper bag issues and be able to upload a new tarball in that
> window
> On Oct 30, 2017, at 1:41 PM, Toshio Kuratomi wrote:
>
> I figured that unless I
> asked, I would never know the answer :-)
>
TestPyPI has a couple of use cases, and it’s not very good at any of them.
One use case is to serve as a staging site for production PyPI to
TestPyPI can be useful for those who are not package maintainers, but want
to learn about Python Packaging and need a 'playground' to experiment with
it.
Mariatta Wijaya
On Mon, Oct 30, 2017 at 10:41 AM, Toshio Kuratomi
wrote:
> When we locked down pypi to prevent
When we locked down pypi to prevent uploading an sdist to overwrite a
previous I remember that some people wanted a brief window to check
for brown paper bag issues and be able to upload a new tarball in that
window if needed. IIRC, those people were told to use testpypi for
that sort of thing.