On 9 October 2015 at 09:05, Thomas Güttler wrote:
> This is a follow up to the thread "Where should I put tests when packaging
> python modules?"
>
> I have never used tox up to now. But reading the mails of the thread, it seems
> that tox is the current state of
On 9 October 2015 at 20:11, Ionel Cristian Mărieș wrote:
>
> On Fri, Oct 9, 2015 at 12:43 PM, Paul Moore wrote:
>>
>>
>> The sample project is not intended for that purpose. It's a good
>> starting point for something like that, but that's not its
On Sat, Oct 10, 2015 at 5:11 PM, Nick Coghlan wrote:
> This unfortunately isn't a good idea, at least for folks aiming to
> publish their first project. While it's well-intentioned, the problem
> with it is that it can be *tremendously* demotivating for folks that
> aren't
On Oct 10, 2015 9:55 AM, "Ionel Cristian Mărieș" wrote:
>
>
> On Sat, Oct 10, 2015 at 5:11 PM, Nick Coghlan wrote:
>>
>> This unfortunately isn't a good idea, at least for folks aiming to
>> publish their first project. While it's well-intentioned, the
On Fri, Oct 9, 2015 at 12:43 PM, Paul Moore wrote:
>
> The sample project is not intended for that purpose. It's a good
> starting point for something like that, but that's not its purpose.
>
> Paul
>
> PS I sympathise with your wish for a "do this to set up your first
>
Am 08.10.2015 um 23:33 schrieb Antoine Pitrou:
On Thu, 8 Oct 2015 22:05:16 +0200
Thomas Güttler wrote:
This is a follow up to the thread "Where should I put tests when packaging python
modules?"
I have never used tox up to now. But reading the mails of the
Well, https://packaging.python.org/en/latest/distributing/ already says
"""
The section does not aim to cover best practices for Python project
development as a whole. For example, it does not provide guidance or
tool recommendations for version control, documentation, or testing
"""
It may be
On 9 October 2015 at 10:32, Thomas Güttler wrote:
> My question was: Any reasons not to use tox in the sample project?
1. Because the sample project is intended to explain how to *package*
a project, not how to test it, or document it, or any of a number of
other
On Thursday, October 8, 2015, Thomas Güttler
wrote:
> This is a follow up to the thread "Where should I put tests when packaging
> python modules?"
>
> I have never used tox up to now. But reading the mails of the thread, it
> seems
> that tox is the current state
On Thu, 8 Oct 2015 22:05:16 +0200
Thomas Güttler wrote:
> This is a follow up to the thread "Where should I put tests when packaging
> python modules?"
>
> I have never used tox up to now. But reading the mails of the thread, it seems
> that tox is the current
This is a follow up to the thread "Where should I put tests when packaging
python modules?"
I have never used tox up to now. But reading the mails of the thread, it seems
that tox is the current state of the art.
This leads me to the conclusion that the sample project should use tox.
Any
11 matches
Mail list logo