On Wed, Mar 6, 2013 at 4:45 PM, Lennart Regebro rege...@gmail.com wrote:
Perhaps we can solve this outside distutils-sig so that distutils-sig
can concentrate on the harder problems?
It's a distutils-sig problem because you need a way to publish any new
testing related metadata, and because
On Tue, Mar 5, 2013 at 5:02 PM, Lennart Regebro rege...@gmail.com wrote:
I don't care much what that mechanism is, but I think the easiest way
to get there is to tell people to extend distutils with a test command
(or use Distribute) and perhaps add such a command in 3.4 that will do
the
On Mar 4, 2013, at 11:13 PM, Robert Collins robe...@robertcollins.net wrote:
In principle maybe. Need to talk with the trial developers, nose
developers, py.test developers etc - to get consensus on a number of
internal API friction points.
Some of trial's lessons might be also useful for the
On Tue, Mar 5, 2013 at 10:02 AM, Glyph gl...@twistedmatrix.com wrote:
On Mar 4, 2013, at 11:13 PM, Robert Collins robe...@robertcollins.net
wrote:
In principle maybe. Need to talk with the trial developers, nose
developers, py.test developers etc - to get consensus on a number of
internal
On 5 Mar 2013, at 07:19, Antoine Pitrou solip...@pitrou.net wrote:
On Mon, 4 Mar 2013 15:47:37 -0800
Eli Bendersky eli...@gmail.com wrote:
On Mon, Mar 4, 2013 at 1:28 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Mon, 4 Mar 2013 13:26:57 -0800
Eli Bendersky eli...@gmail.com wrote:
On 5 Mar 2013, at 09:02, Glyph gl...@twistedmatrix.com wrote:
On Mar 4, 2013, at 11:13 PM, Robert Collins robe...@robertcollins.net wrote:
In principle maybe. Need to talk with the trial developers, nose
developers, py.test developers etc - to get consensus on a number of
internal API
On Mar 05, 2013, at 02:11 AM, Donald Stufft wrote:
Doesn't setuptools/distribute already have a setup.py test command? That
seems like the easiest way forward?
Yes, and in theory it can make `python setup.py test` work well. But there
are lots of little details (such as API differences for
On Tue, Mar 5, 2013 at 2:49 PM, Barry Warsaw ba...@python.org wrote:
On Mar 05, 2013, at 02:11 AM, Donald Stufft wrote:
Doesn't setuptools/distribute already have a setup.py test command? That
seems like the easiest way forward?
Yes, and in theory it can make `python setup.py test` work well.
On 6 Mar 2013 05:51, Barry Warsaw ba...@python.org wrote:
On Mar 05, 2013, at 02:11 AM, Donald Stufft wrote:
Doesn't setuptools/distribute already have a setup.py test command? That
seems like the easiest way forward?
Yes, and in theory it can make `python setup.py test` work well. But
On Tue, Mar 5, 2013 at 8:11 AM, Donald Stufft donald.stu...@gmail.com wrote:
I don't care much what that mechanism is, but I think the easiest way
to get there is to tell people to extend distutils with a test command
(or use Distribute) and perhaps add such a command in 3.4 that will do
the
On Tue, Mar 5, 2013 at 8:13 AM, Robert Collins
robe...@robertcollins.net wrote:
On 5 March 2013 20:02, Lennart Regebro rege...@gmail.com wrote:
What's needed here is not a tool that can run all unittests in
existence, but an official way for automated tools to run tests, with
the ability for
On Tue, Mar 5, 2013 at 9:25 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Tue, Mar 5, 2013 at 5:02 PM, Lennart Regebro rege...@gmail.com wrote:
I don't care much what that mechanism is, but I think the easiest way
to get there is to tell people to extend distutils with a test command
(or use
[Splitting into a separate thread]
Do we really need to overthink something that requires a trivial alias to
set up for one's own convenience?
Picking a Python version (as Barry mentions) is just one of the problems.
What's wrong with:
alias rupytests='python3 -m unittest discover
alias
On Mon, 4 Mar 2013 13:26:57 -0800
Eli Bendersky eli...@gmail.com wrote:
[Splitting into a separate thread]
Do we really need to overthink something that requires a trivial alias to
set up for one's own convenience?
Picking a Python version (as Barry mentions) is just one of the problems.
On 5 March 2013 10:26, Eli Bendersky eli...@gmail.com wrote:
[Splitting into a separate thread]
Do we really need to overthink something that requires a trivial alias to
set up for one's own convenience?
The big thing is automated tools, not developers.
When distributors want to redistribute
On Mar 05, 2013, at 11:01 AM, Robert Collins wrote:
The big thing is automated tools, not developers.
Exactly.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Mon, Mar 4, 2013 at 1:28 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Mon, 4 Mar 2013 13:26:57 -0800
Eli Bendersky eli...@gmail.com wrote:
[Splitting into a separate thread]
Do we really need to overthink something that requires a trivial alias to
set up for one's own
On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw ba...@python.org wrote:
On Mar 05, 2013, at 11:01 AM, Robert Collins wrote:
The big thing is automated tools, not developers.
Exactly.
I don't understand. Is python -m unittest discover too much typing for
automatic tools? If anything, it's much
On 5 March 2013 12:49, Eli Bendersky eli...@gmail.com wrote:
On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw ba...@python.org wrote:
On Mar 05, 2013, at 11:01 AM, Robert Collins wrote:
The big thing is automated tools, not developers.
Exactly.
I don't understand. Is python -m unittest
On Mon, Mar 4, 2013 at 4:09 PM, Robert Collins robe...@robertcollins.netwrote:
On 5 March 2013 12:49, Eli Bendersky eli...@gmail.com wrote:
On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw ba...@python.org wrote:
On Mar 05, 2013, at 11:01 AM, Robert Collins wrote:
The big thing is
On 5 March 2013 13:35, Eli Bendersky eli...@gmail.com wrote:
Perhaps :-)
I'm specifically referring to a new top-level script that will run all
unittests in discovery mode from the current directory, as a shortcut to
python -m unittest discover. ISTM this is at leas in part what was
On Mar 05, 2013, at 01:09 PM, Robert Collins wrote:
It isn't about length. It is about knowing that *that* is what to type
(and btw that exact command cannot run twisted's tests, among many
other projects tests).
Perhaps we are talking about different things. A top level script to
run tests is
On Tue, Mar 5, 2013 at 1:41 AM, Robert Collins
robe...@robertcollins.net wrote:
So that is interesting, but its not sufficient to meet the automation
need Barry is calling out, unless all test suites can be run by
'python -m unittest discover' with no additional parameters [and a
pretty large
On Tuesday, March 5, 2013 at 2:02 AM, Lennart Regebro wrote:
On Tue, Mar 5, 2013 at 1:41 AM, Robert Collins
robe...@robertcollins.net (mailto:robe...@robertcollins.net) wrote:
So that is interesting, but its not sufficient to meet the automation
need Barry is calling out, unless all test
On 5 March 2013 20:02, Lennart Regebro rege...@gmail.com wrote:
On Tue, Mar 5, 2013 at 1:41 AM, Robert Collins
robe...@robertcollins.net wrote:
So that is interesting, but its not sufficient to meet the automation
need Barry is calling out, unless all test suites can be run by
'python -m
On Mon, 4 Mar 2013 15:47:37 -0800
Eli Bendersky eli...@gmail.com wrote:
On Mon, Mar 4, 2013 at 1:28 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Mon, 4 Mar 2013 13:26:57 -0800
Eli Bendersky eli...@gmail.com wrote:
[Splitting into a separate thread]
Do we really need to
26 matches
Mail list logo
