Re: [Python-Dev] Introducing Electronic Contributor Agreements

On 3/4/2013 7:51 PM, Mark Lawrence wrote: Who's talking source code, you're previously mentioned *ALL* patches needing a CLA. Does this mean you have to sign a CLA for a one line documentation patch? It it is a one char typo, I would not bother downloading the patch, or adding a person to AC

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On Mon, 4 Mar 2013 15:47:37 -0800 Eli Bendersky wrote: > On Mon, Mar 4, 2013 at 1:28 PM, Antoine Pitrou wrote: > > > On Mon, 4 Mar 2013 13:26:57 -0800 > > Eli Bendersky wrote: > > > [Splitting into a separate thread] > > > > > > Do we really need to overthink something that requires a trivial a

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On 5 March 2013 20:02, Lennart Regebro wrote: > On Tue, Mar 5, 2013 at 1:41 AM, Robert Collins > 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 p

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On Tuesday, March 5, 2013 at 2:02 AM, Lennart Regebro wrote: > On Tue, Mar 5, 2013 at 1:41 AM, Robert Collins > 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 suites can be run by > >

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On Tue, Mar 5, 2013 at 1:41 AM, Robert Collins 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 subset cannot]. But c

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 4:39 PM, Michael Foord wrote: > > On 1 Mar 2013, at 18:38, Antoine Pitrou wrote: > >> On Fri, 1 Mar 2013 09:32:23 -0500 >> Barry Warsaw wrote: >>> On the other hand in some ways Jython is sort of like Python on a weird virtual OS that lets the real OS bleed throu

Re: [Python-Dev] Introducing Electronic Contributor Agreements

Mark Lawrence writes: > People already use the bug tracker as an excuse not to contribute, > wouldn't this requirement make the situation worse? A failure to sign the CLA is already a decision not to contribute to the distribution, no matter how noisy they are on the tracker and list. I think

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

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

Re: [Python-Dev] running tests; mebs

>> As a community, we know how important tests are, so I think our tools should >> reflect that and make it easy for those tests to be expressed. As a selfish >> side-effect, I want to reduce the amount of guesswork I need to perform in >> order to know how to run a package's test when I `$vcs clo

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 4 Mar 2013, at 20:00, Robert Collins wrote: > On 5 March 2013 05:34, Brett Cannon wrote: >> >> >> >> On Mon, Mar 4, 2013 at 11:29 AM, Barry Warsaw wrote: >>> >>> On Mar 04, 2013, at 07:26 PM, Robert Collins wrote: >>> It is of course possible for subunit and related tools to run t

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 4 Mar 2013, at 22:24, Barry Warsaw wrote: > On Mar 04, 2013, at 05:04 PM, Brett Cannon wrote: > >> Sure, but that has nothing to do with programmatic package discovery. >> That's something you will have to do as a person in making a qualitative >> decision along the same lines as API design.

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 5 March 2013 13:50, Michael Foord wrote: >> Right - all I wanted was to flag that you and I and any other >> interested parties should discuss this at the summit :). > > I've added a testing topic to the agenda. At the very least you could outline > your streaming test result proposal, or kic

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 5 Mar 2013, at 00:23, Robert Collins wrote: > On 5 March 2013 13:21, Michael Foord wrote: >> > >> We can certainly talk about it - although as Guido says, something specific >> may be easier to have a useful discussion about. >> >> Reading through your blog articles it seemed like a whol

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On 04/03/2013 22:08, Brett Cannon wrote: On Mon, Mar 4, 2013 at 4:33 PM, Mark Lawrence mailto:breamore...@yahoo.co.uk>> wrote: On 04/03/2013 20:46, Terry Reedy wrote: On 3/4/2013 11:36 AM, Brett Cannon wrote: On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On 5 March 2013 13:35, Eli Bendersky 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 > discussed, and my

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 1 Mar 2013, at 18:38, Antoine Pitrou wrote: > On Fri, 1 Mar 2013 09:32:23 -0500 > Barry Warsaw wrote: >> >>> On the other hand in some ways Jython is sort of like Python on a >>> weird virtual OS that lets the real OS bleed through some. This may >>> still need to be checked in that way (th

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On Mon, Mar 4, 2013 at 4:09 PM, Robert Collins wrote: > On 5 March 2013 12:49, Eli Bendersky wrote: > > > > On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw wrote: > >> > >> On Mar 05, 2013, at 11:01 AM, Robert Collins wrote: > >> > >> >The big thing is automated tools, not developers. > >> > >> Exa

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 4 Mar 2013, at 20:02, Daniel Holth wrote: > On Mon, Mar 4, 2013 at 2:26 PM, Berker Peksağ wrote: >> On Mon, Mar 4, 2013 at 9:14 PM, Barry Warsaw wrote: >>> On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote: >>> > $ python -m unittest discover > $ python setup.py test > $ pytho

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 28 Feb 2013, at 13:49, Brett Cannon wrote: > > > > On Thu, Feb 28, 2013 at 6:34 AM, Michael Foord > wrote: > > On 28 Feb 2013, at 07:36, Georg Brandl wrote: > > > Am 27.02.2013 17:51, schrieb Michael Foord: > >> Hello all, > >> > >> PyCon, and the Python Language Summit, is nearly upo

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 5 March 2013 13:21, Michael Foord wrote: > > We can certainly talk about it - although as Guido says, something specific > may be easier to have a useful discussion about. > > Reading through your blog articles it seemed like a whole lot of subunit > context was required to understand the sp

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 4 Mar 2013, at 19:26, Berker Peksağ wrote: > On Mon, Mar 4, 2013 at 9:14 PM, Barry Warsaw wrote: >> On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote: >> $ python -m unittest discover $ python setup.py test $ python setup.py nosetests $ python -m nose test $ nosete

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 4 Mar 2013, at 06:26, Robert Collins wrote: > On 4 March 2013 18:54, Guido van Rossum wrote: >> On Sun, Mar 3, 2013 at 9:24 PM, Robert Collins >> wrote: >>> I'd like to talk about overhauling - not tweaking, overhauling - the >>> standard library testing facilities. >> >> That seems like t

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 5 Mar 2013 05:21, "Barry Warsaw" wrote: > > On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote: > > >> $ python -m unittest discover > >> $ python setup.py test > >> $ python setup.py nosetests > >> $ python -m nose test > >> $ nosetests-X.Y > >> > >> Besides having a multitude of choices, ther

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 3/4/2013 5:24 PM, Barry Warsaw wrote: What I'm looking for is something that automated tools can use to easily discover how to run a package's tests. I want it to be dead simple for developers of a package to declare how their tests are to be run, and what I am writing a package that has t

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 3 Mar 2013, at 01:29, Trent Nelson wrote: > On Wed, Feb 27, 2013 at 08:51:16AM -0800, Michael Foord wrote: >> If you have other items you'd like to discuss please let me know and I >> can add them to the agenda. > >Hmm, seems like this might be a good forum to introduce the >parallel

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On 5 March 2013 12:49, Eli Bendersky wrote: > > On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw 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 t

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On Mon, Mar 4, 2013 at 2:14 PM, Barry Warsaw 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 more po

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On Mon, Mar 4, 2013 at 1:28 PM, Antoine Pitrou wrote: > On Mon, 4 Mar 2013 13:26:57 -0800 > Eli Bendersky 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

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On 3/4/2013 3:46 PM, Antoine Pitrou wrote: On Mon, 04 Mar 2013 15:46:48 -0500 Terry Reedy wrote: On 3/4/2013 11:36 AM, Brett Cannon wrote: With this in place I would like to propose that all patches submitted to bugs.python.org must come from someone who has signed t

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mar 04, 2013, at 05:04 PM, Brett Cannon wrote: >Sure, but that has nothing to do with programmatic package discovery. >That's something you will have to do as a person in making a qualitative >decision along the same lines as API design. Flipping a bit in a config >file saying "I have tests" do

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

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: http://mail.python

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On Mon, Mar 4, 2013 at 4:33 PM, Mark Lawrence wrote: > On 04/03/2013 20:46, Terry Reedy wrote: > >> On 3/4/2013 11:36 AM, Brett Cannon wrote: >> >>> >>> >>> >>> On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin >> > wrote: >>> >>> The full announcement is at >>> >>> http:/

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 3:45 PM, Barry Warsaw wrote: > On Mar 04, 2013, at 03:40 PM, Daniel Holth wrote: > > >On Mon, Mar 4, 2013 at 3:14 PM, Barry Warsaw wrote: > >> On Mar 04, 2013, at 03:02 PM, Daniel Holth wrote: > >> > >>>setup.py's setup(test_suite="x")... not sure if this is a distutils or

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On 5 March 2013 10:26, Eli Bendersky 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 packages the

Re: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

On Mon, 4 Mar 2013 13:26:57 -0800 Eli Bendersky 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. > What's wro

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On 04/03/2013 20:46, Terry Reedy wrote: On 3/4/2013 11:36 AM, Brett Cannon wrote: On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin mailto:br...@python.org>> wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows.

[Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)

[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 runpyte

Re: [Python-Dev] Planning on removing cache invalidation for file finders

On Sun, Mar 3, 2013 at 12:31 PM, Brett Cannon wrote: > But how about this as a compromise over introducing write_module(): > invalidate_caches() can take a path for something to specifically > invalidate. The path can then be passed to the invalidate_caches() on > sys.meta_path. In the case of Pat

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On Mon, 04 Mar 2013 15:46:48 -0500 Terry Reedy wrote: > On 3/4/2013 11:36 AM, Brett Cannon wrote: > > > > > > > > On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin > > wrote: > > > > The full announcement is at > > http://blog.python.org/2013/03/introducing-electronic

Re: [Python-Dev] Disabling string interning for null and single-char causes segfaults

Hi, 2013/3/4 Amaury Forgeot d'Arc : > The example above is obviously from python2.7; there is a similar example > with python3.2: x = b'\xe9\xe9'.decode('ascii', 'ignore') x == '', x is '' > (True, False) > > ...but this bug has been fixed in 3.3: PyUnicode_Resize() always returns the >

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On 3/4/2013 11:36 AM, Brett Cannon wrote: On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin mailto:br...@python.org>> wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows. We've now moved to an electronic

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mar 04, 2013, at 03:40 PM, Daniel Holth wrote: >On Mon, Mar 4, 2013 at 3:14 PM, Barry Warsaw wrote: >> On Mar 04, 2013, at 03:02 PM, Daniel Holth wrote: >> >>>setup.py's setup(test_suite="x")... not sure if this is a distutils or >>>setuptools feature. PEP 426 has an extension mechanism that c

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 3:14 PM, Barry Warsaw wrote: > On Mar 04, 2013, at 03:02 PM, Daniel Holth wrote: > >>setup.py's setup(test_suite="x")... not sure if this is a distutils or >>setuptools feature. PEP 426 has an extension mechanism that could do >>the job. > > Shouldn't "testing" be a first or

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mar 04, 2013, at 03:02 PM, Daniel Holth wrote: >setup.py's setup(test_suite="x")... not sure if this is a distutils or >setuptools feature. PEP 426 has an extension mechanism that could do >the job. Shouldn't "testing" be a first order feature? -Barry signature.asc Description: PGP signatur

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 5 March 2013 05:51, Barry Warsaw wrote: > I should have added "from the command line". E.g. is it: > > $ python -m unittest discover > $ python setup.py test > $ python setup.py nosetests > $ python -m nose test > $ nosetests-X.Y $ testr run :) > Besides having a multitude of choices, there

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 2:26 PM, Berker Peksağ wrote: > On Mon, Mar 4, 2013 at 9:14 PM, Barry Warsaw wrote: >> On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote: >> $ python -m unittest discover $ python setup.py test $ python setup.py nosetests $ python -m nose test $ no

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On 5 March 2013 05:34, Brett Cannon wrote: > > > > On Mon, Mar 4, 2013 at 11:29 AM, Barry Warsaw wrote: >> >> On Mar 04, 2013, at 07:26 PM, Robert Collins wrote: >> >> >It is of course possible for subunit and related tools to run their >> >own implementation, but it seems ideal to me to have a c

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On Tue, Mar 5, 2013 at 3:30 AM, Brian Curtin wrote: > The full announcement is at > http://blog.python.org/2013/03/introducing-electronic-contributor.html, > but a summary follows. > > We've now moved to an electronic Contributor License Agreement form at > http://www.python.org/psf/contrib/contr

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 9:14 PM, Barry Warsaw wrote: > On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote: > >>> $ python -m unittest discover >>> $ python setup.py test >>> $ python setup.py nosetests >>> $ python -m nose test >>> $ nosetests-X.Y >>> >>> Besides having a multitude of choices, ther

Re: [Python-Dev] Disabling string interning for null and single-char causes segfaults

2013/3/4 Guido van Rossum > x = u'\xe9'.encode('ascii', 'ignore') > x == '', x is '' > > (True, False) > > Code that relies on this is incorrect (the language doesn't guarantee > interning) but nevertheless given the intention of the implementation, > that behavior of encode() is also a

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote: >> $ python -m unittest discover >> $ python setup.py test >> $ python setup.py nosetests >> $ python -m nose test >> $ nosetests-X.Y >> >> Besides having a multitude of choices, there's almost no way to >> automatically discover (e.g. by metada

Re: [Python-Dev] Disabling string interning for null and single-char causes segfaults

On Mon, Mar 4, 2013 at 11:06 AM, Amaury Forgeot d'Arc wrote: > > > 2013/3/4 Serhiy Storchaka >> >> On 01.03.13 17:24, Stefan Bucur wrote: >>> >>> Before digging deeper into the issue, I wanted to ask here if there are >>> any implicit assumptions about string identity and interning throughout >>>

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 8:41 PM, Antoine Pitrou wrote: > On Mon, 4 Mar 2013 11:51:04 -0500 > Barry Warsaw wrote: >> On Mar 04, 2013, at 11:34 AM, Brett Cannon wrote: >> >> >> And One True Way of invoking and/or discovering how to invoke, a package's >> >> test suite. >> > >> >How does unittest's t

Re: [Python-Dev] Disabling string interning for null and single-char causes segfaults

2013/3/4 Serhiy Storchaka > On 01.03.13 17:24, Stefan Bucur wrote: > >> Before digging deeper into the issue, I wanted to ask here if there are >> any implicit assumptions about string identity and interning throughout >> the interpreter implementation. For instance, are two single-char >> string

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, 4 Mar 2013 11:51:04 -0500 Barry Warsaw wrote: > On Mar 04, 2013, at 11:34 AM, Brett Cannon wrote: > > >> And One True Way of invoking and/or discovering how to invoke, a package's > >> test suite. > > > >How does unittest's test discovery not solve that? > > I should have added "from the

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On Mon, Mar 4, 2013 at 11:02 AM, Skip Montanaro wrote: > > > On Mon, Mar 4, 2013 at 10:30 AM, Brian Curtin wrote: >> >> The full announcement is at >> http://blog.python.org/2013/03/introducing-electronic-contributor.html, >> but a summary follows. >> ... > > > Brian, > > Do you want old-timers l

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On Mon, Mar 4, 2013 at 10:30 AM, Brian Curtin wrote: > The full announcement is at > http://blog.python.org/2013/03/introducing-electronic-contributor.html, > but a summary follows. > ... Brian, Do you want old-timers like me who have a wet-signed fax gathering dust in a box at PSF World Head

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mar 04, 2013, at 11:34 AM, Brett Cannon wrote: >> And One True Way of invoking and/or discovering how to invoke, a package's >> test suite. > >How does unittest's test discovery not solve that? I should have added "from the command line". E.g. is it: $ python -m unittest discover $ python se

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 11:44 AM, David Cournapeau wrote: > On Mon, Mar 4, 2013 at 4:34 PM, Brett Cannon wrote: > > > > > > > > On Mon, Mar 4, 2013 at 11:29 AM, Barry Warsaw wrote: > >> > >> On Mar 04, 2013, at 07:26 PM, Robert Collins wrote: > >> > >> >It is of course possible for subunit and re

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 4:34 PM, Brett Cannon wrote: > > > > On Mon, Mar 4, 2013 at 11:29 AM, Barry Warsaw wrote: >> >> On Mar 04, 2013, at 07:26 PM, Robert Collins wrote: >> >> >It is of course possible for subunit and related tools to run their >> >own implementation, but it seems ideal to me to

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mon, Mar 4, 2013 at 11:29 AM, Barry Warsaw wrote: > On Mar 04, 2013, at 07:26 PM, Robert Collins wrote: > > >It is of course possible for subunit and related tools to run their > >own implementation, but it seems ideal to me to have a common API > >which regular unittest, nose, py.test and oth

Re: [Python-Dev] Introducing Electronic Contributor Agreements

On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin wrote: > The full announcement is at > http://blog.python.org/2013/03/introducing-electronic-contributor.html, > but a summary follows. > > We've now moved to an electronic Contributor License Agreement form at > http://www.python.org/psf/contrib/cont

[Python-Dev] Introducing Electronic Contributor Agreements

The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows. We've now moved to an electronic Contributor License Agreement form at http://www.python.org/psf/contrib/contrib-form/ which will hopefully ease the signing and sending of for

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

On Mar 04, 2013, at 07:26 PM, Robert Collins wrote: >It is of course possible for subunit and related tools to run their >own implementation, but it seems ideal to me to have a common API >which regular unittest, nose, py.test and others can all agree on and >use : better reuse for pretty printers

Re: [Python-Dev] Disabling string interning for null and single-char causes segfaults

On 01.03.13 17:24, Stefan Bucur wrote: Before digging deeper into the issue, I wanted to ask here if there are any implicit assumptions about string identity and interning throughout the interpreter implementation. For instance, are two single-char strings having the same content supposed to be i

Re: [Python-Dev] Disabling string interning for null and single-char causes segfaults

On 02.03.13 22:32, Terry Reedy wrote: I am just curious: does 3.3 still intern (some) unicode chars? Did the 256 interned bytes of 2.x carry over to 3.x? Yes, Python 3 interns an empty string and first 256 Unicode characters. ___ Python-Dev mailing

Re: [Python-Dev] Python Language Summit at PyCon: Agenda

Le Mon, 4 Mar 2013 19:46:07 +1300, Robert Collins a écrit : > On 4 March 2013 19:40, Nick Coghlan wrote: > > > Your feedback on http://bugs.python.org/issue16997 would be greatly > > appreciated. > > Done directly to Antoine on IRC the other day in a conversation with > him and Michael about th