On 12/4/21 1:42 pm, John Rouillard wrote:
>>> Also I was able to use:
>>>
>>>       python3 setup.py sdist --repository test --sign
>>>
>>> successfully. I also did a pure sdist and tested the tarball. All
>>> tests passed.
>>>
>>> I also was able to:
>>>
>>>       python3 setup.py bdist_egg --repository test --sign
>>>       python3 setup.py bdist_wheel  --repository test --sign
>>>
>>> and it seems to work on test.pypi.org.
>>>
>>> Do you have a reference on how I can test these? Something similar to
>>> (your) step 11 in RELEASE.txt would be good. I don't want egg (ahem)
>>> on my face if I deploy these methods.
>>
>> I'm not sure I follow what you want to test. Are you able to elaborate?
> 
> Well when I have an sdist tarball, I unpack it somewhere in /tmp, run
> pytest against it. Then I run setup install --prefix (or --user) and
> check that expected files are where they should be in the resulting
> install.
> 
> What is the equivalent test mechanism for an egg or wheel to verify
> that they are properly built and will install correctly.
> E.G. a dummy example would be:
> 
>     python --wheel roundup.whl --entry roundup-admin
> 
> to verify that I can start roundup-admin from the wheel.
> 
> Roundup isn't just a module to be imported by an application. It is a
> set of cli applications, so maybe egg/wheel distribution doesn't make
> sense.
> 
> Thanks.

Would the following commands cover the use-cases for testing the 
installation from the various file formats:

     pip install dist/roundup-2.0.0.tar.gz
     pip install dist/roundup-2.0.0-py3-none-any.whl
     python -m easy_install dist/roundup-2.0.0-py3.9.egg

I'm not sure about how to invoke commands from a python archives 
directly. Are there any specific use-cases where this would be useful? I 
would assume to do anything useful with roundup it would need to be 
installed.