Hi all,
I won't be able to make it to the summit and probably not the
conference. I have a raging 104F fever (40C for many of you =)
The doctor says I have influenza and am highly contagious, so I
shouldn't be going anywhere near conference full of people for five
days - looks like I'm missing th
On Tue, Mar 5, 2013 at 8:55 AM, fwierzbi...@gmail.com
wrote:
> I've been thinking that this is a bit of a historical mistake on our
> part. I'm strongly considering setting os.name properly in Jython3.
In fairness to Jython implementers past - it wasn't a mistake but a
deliberate design choice at
On Mon, Mar 4, 2013 at 9:39 PM, Jeff Hardy wrote:
> I think you misremembered - there's lots of code that uses
> `sys.platform == 'win32'` to detect Windows, but sys.platform is 'cli'
> for IronPython. I'm pretty sure `os.name has always been 'nt' (when
> running on Windows), and if not, it defini
On 5 Mar 2013, at 05:39, Jeff Hardy wrote:
> 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 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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
On Mon, Mar 4, 2013 at 4:46 PM, Robert Collins
wrote:
> 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 the compata
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 the compatability impact of subtests. Happy to
do a full code review if that
On Mon, Mar 4, 2013 at 4:26 PM, 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 li
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 too big a topic and too vague a description to discuss
> use
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 too big a topic and too vague a description to discuss
usefully. Perhaps you have a specific proposal? Or at least ju
On 28 February 2013 05:51, Michael Foord wrote:
> Hello all,
>
> PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
>
> The agenda of topics f
On Mar 2, 2013, at 11:41 AM, Nick Coghlan wrote:
> On Fri, Mar 1, 2013 at 9:39 AM, Doug Hellmann wrote:
>>
>> On Feb 27, 2013, at 11:51 AM, Michael Foord wrote:
>>
>>> Hello all,
>>>
>>> PyCon, and the Python Language Summit, is nearly upon us. We have a good
>>> number of people confirmed
Stefan Krah, 02.03.2013 21:01:
> Stefan Behnel wrote:
I'm not so happy with the argument clinic, but that's certainly also
because I'm biased. I've written the argument unpacking code for Cython
some years ago, so it's not surprising that I'm quite happy with that and
fail to se
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/async stuff I've been working on the past few months.
On Thu, 28 Feb 2013 11:39:52 +
Michael Foord wrote:
> >
> > Perhaps someone wants to discuss
> > http://www.python.org/dev/peps/pep-0428/, but I won't be there and the
> > PEP isn't terribly up-to-date either :-)
>
> If you can find someone familiar with pathlib to champion the discussion it
Stefan Behnel wrote:
> >> I'm not so happy with the argument clinic, but that's certainly also
> >> because I'm biased. I've written the argument unpacking code for Cython
> >> some years ago, so it's not surprising that I'm quite happy with that and
> >> fail to see the need for a totally new DSL
Hi Nick,
thanks for the feedback.
Nick Coghlan, 02.03.2013 17:58:
> On Fri, Mar 1, 2013 at 7:41 PM, Stefan Behnel wrote:
>> Michael Foord, 27.02.2013 17:51:
>> It's also true that many of the topics above aren't really interesting for
>> us, because we just inherit them with CPython, e.g. stdlib
>> And I'd really like to see a CPython summit
>> happen at some point. There's so much interesting stuff going on in that
>> area that it's worth getting some people together to move these things
>> forward.
>
> Yes, a CPython runtime summit some year would be interesting.
>
> Cheers,
> Nick.
I
On Fri, Mar 1, 2013 at 7:41 PM, Stefan Behnel wrote:
> Michael Foord, 27.02.2013 17:51:
> It's also true that many of the topics above aren't really interesting for
> us, because we just inherit them with CPython, e.g. stdlib changes.
> Packaging is only relevant as far as it impacts the distribut
On Sat, Mar 2, 2013 at 6:01 PM, Gregory P. Smith wrote:
> It'd mean smaller code objects and less bloat from constants (docstrings for
> one implementation vs another, etc) being in memory. Taken further, this
> could even be extended beyond implementations to platforms as we have some
> standard
On Fri, Mar 1, 2013 at 9:39 AM, Doug Hellmann wrote:
>
> On Feb 27, 2013, at 11:51 AM, Michael Foord wrote:
>
>> Hello all,
>>
>> PyCon, and the Python Language Summit, is nearly upon us. We have a good
>> number of people confirmed to attend. If you are intending to come to the
>> language summ
On Thu, Feb 28, 2013 at 1:15 AM, Nick Coghlan wrote:
> On Thu, Feb 28, 2013 at 1:37 PM, Barry Warsaw wrote:
> > On Feb 27, 2013, at 11:33 AM, fwierzbi...@gmail.com wrote:
> >>The easy part for Jython is pushing some of our "if is_jython:" stuff
> >>into the appropriate spots in CPython's Lib/.
>
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 (there's are still checks of >os.name == 'nt'> right?)
>
>
On Fri, Mar 1, 2013 at 4:41 AM, Stefan Behnel wrote:
> Michael Foord, 27.02.2013 17:51:
> > PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
On Feb 28, 2013, at 08:44 AM, fwierzbi...@gmail.com wrote:
>Sorry I meant "is_jython" as a sort of shorthand for a case by case
>check. It would be cool if we had a nice set of checks somewhere like
>"is_refcounted", etc. Would the sys.implementation area be a good
>place for such things?
Yep. U
Michael Foord, 27.02.2013 17:51:
> PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
>
> The agenda of topics for discussion so far includes
On Feb 27, 2013, at 11:51 AM, Michael Foord wrote:
> Hello all,
>
> PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
>
> The agenda of to
On Thu, Feb 28, 2013 at 1:30 AM, Antoine Pitrou wrote:
> Le Wed, 27 Feb 2013 11:33:30 -0800,
> "fwierzbi...@gmail.com" a écrit :
>>
>> There are a couple of spots that might be more controversial. For
>> example, Jython has a file Lib/zlib.py that implements zlib in terms
>> of the existing Java
On Thu, Feb 28, 2013 at 1:15 AM, Nick Coghlan wrote:
> On Thu, Feb 28, 2013 at 1:37 PM, Barry Warsaw wrote:
>> On Feb 27, 2013, at 11:33 AM, fwierzbi...@gmail.com wrote:
>>>The easy part for Jython is pushing some of our "if is_jython:" stuff
>>>into the appropriate spots in CPython's Lib/.
>>
>>
On Wed, Feb 27, 2013 at 7:37 PM, Barry Warsaw wrote:
> On Feb 27, 2013, at 11:33 AM, fwierzbi...@gmail.com wrote:
>
>>I am suggesting that we push forward on the "shared library" approach to the
>>files in the Lib/* directory, so that would certainly include IronPython and
>>PyPy as well I hope.
>
On Thursday, February 28, 2013 at 9:49 AM, Stefan Krah wrote:
> Jesse Noller mailto:jnol...@gmail.com)> wrote:
> > > Why would it help to resolve such an issue (if it is an issue at all!)
> > > for a single person on a private mailing list?
> >
> >
> >
> >
> > See: http://mail.python.org/pip
Jesse Noller wrote:
> > Why would it help to resolve such an issue (if it is an issue at all!)
> > for a single person on a private mailing list?
>
>
> See: http://mail.python.org/pipermail/python-dev/2013-February/124463.html
That was quick. Thanks!
Stefan Krah
__
Steven D'Aprano wrote:
> The question of whether or not the PSF is violating the Apache license in
> some way is not one that is helped by having arbitrary people give their
> uninformed opinions.
No one will be preventing lawyers from giving their opinions on python-legal.
In fact, at least one
On Thursday, February 28, 2013 at 7:26 AM, Stefan Krah wrote:
> Jesse Noller mailto:jnol...@gmail.com)> wrote:
> > > > We have one: p...@python.org (mailto:p...@python.org)
> > >
> > >
> > >
> > > That's not exactly a public mailing-list.
> >
> > Nope. But it's also where lawyers flock and t
On Thu, Feb 28, 2013 at 8:53 AM, Benjamin Peterson wrote:
> 2013/2/28 Brett Cannon :
> >
> >
> >
> > On Thu, Feb 28, 2013 at 6:34 AM, Michael Foord <
> fuzzy...@voidspace.org.uk>
> > wrote:
> >>
> >>
> >> On 28 Feb 2013, at 07:36, Georg Brandl wrote:
> >>
> >> > Am 27.02.2013 17:51, schrieb Micha
2013/2/28 Brett Cannon :
>
>
>
> 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 upon us. We have a
>> >
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 upon us. We have a
> good number of people confirmed to attend. If y
Le Fri, 01 Mar 2013 00:21:48 +1100,
Steven D'Aprano a écrit :
>
> The question of whether or not the PSF is violating the Apache
> license in some way is not one that is helped by having arbitrary
> people give their uninformed opinions. I sympathize with curious
> people wanting to see what's go
On 28/02/13 23:26, Stefan Krah wrote:
Jesse Noller wrote:
We have one: p...@python.org
That's not exactly a public mailing-list.
Nope. But it's also where lawyers flock and these issues can rapidly be
resolved.
If the list isn't publicly archived, the same questions will arise over
and o
On Feb 28, 2013, at 8:03 AM, "Stephen J. Turnbull" wrote:
> Stefan Krah writes:
>
>> Why would [the PSF list] help to resolve such an issue (if it is an
>> issue at all!)
>
> Precisely.
>
> If there *is* a compliance problem, there's nothing to be done before
> talking to the lawyers. Altho
Stefan Krah writes:
> Why would [the PSF list] help to resolve such an issue (if it is an
> issue at all!)
Precisely.
If there *is* a compliance problem, there's nothing to be done before
talking to the lawyers. Although license *choice* is primarily a
political issue, *compliance* is technic
On Feb 28, 2013, at 7:31 AM, Jesse Noller wrote:
>
>
> On Feb 28, 2013, at 7:23 AM, Antoine Pitrou wrote:
>
>> Le Thu, 28 Feb 2013 06:57:36 -0500,
>> Jesse Noller a écrit :
>>>
>>> On Feb 28, 2013, at 6:55 AM, Antoine Pitrou
>>> wrote:
>>>
Le Thu, 28 Feb 2013 06:48:24 -0500,
J
On Feb 28, 2013, at 7:23 AM, Antoine Pitrou wrote:
> Le Thu, 28 Feb 2013 06:57:36 -0500,
> Jesse Noller a écrit :
>>
>> On Feb 28, 2013, at 6:55 AM, Antoine Pitrou
>> wrote:
>>
>>> Le Thu, 28 Feb 2013 06:48:24 -0500,
>>> Jesse Noller a écrit :
>
> Perhaps it's an idea to have a py
Jesse Noller wrote:
> >> We have one: p...@python.org
> >
> > That's not exactly a public mailing-list.
>
> Nope. But it's also where lawyers flock and these issues can rapidly be
> resolved.
If the list isn't publicly archived, the same questions will arise over
and over again (probably on py
Le Thu, 28 Feb 2013 06:57:36 -0500,
Jesse Noller a écrit :
>
> On Feb 28, 2013, at 6:55 AM, Antoine Pitrou
> wrote:
>
> > Le Thu, 28 Feb 2013 06:48:24 -0500,
> > Jesse Noller a écrit :
> >>>
> >>> Perhaps it's an idea to have a python-legal mailing list for these
> >>> topics?
> >>>
> >>> I
On Feb 28, 2013, at 6:55 AM, Antoine Pitrou wrote:
> Le Thu, 28 Feb 2013 06:48:24 -0500,
> Jesse Noller a écrit :
>>>
>>> Perhaps it's an idea to have a python-legal mailing list for these
>>> topics?
>>>
>>> I don't think it's fundamentally wrong to scrutinize licenses,
>>> provided that th
Le Thu, 28 Feb 2013 06:48:24 -0500,
Jesse Noller a écrit :
> >
> > Perhaps it's an idea to have a python-legal mailing list for these
> > topics?
> >
> > I don't think it's fundamentally wrong to scrutinize licenses,
> > provided that the discussion stays civil and factual.
> >
> > IIRC Debian
On Feb 28, 2013, at 6:42 AM, Stefan Krah wrote:
> Jesse Noller wrote:
>> http://www.python.org/psf/contrib/contrib-form/ + http://opensource.org/
>>licenses/apache2.0.php
>> and why PSF doesn't comply the 4. Redistribution clause from Apache 2.0
>>license
>>
>>
>>
>> I'm
On 28 Feb 2013, at 03:42, Barry Warsaw wrote:
> On Feb 27, 2013, at 04:51 PM, 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.
>
> I'd like to have some discussions around promotion of Python 3, how we can
> acceler
On 27 Feb 2013, at 19:01, fwierzbi...@gmail.com wrote:
> On Wed, Feb 27, 2013 at 8:51 AM, 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.
>
> I'd like to discuss merging Jython's standard Lib (the *.py files). We
Jesse Noller wrote:
> http://www.python.org/psf/contrib/contrib-form/ + http://opensource.org/
> licenses/apache2.0.php
>and why PSF doesn't comply the 4. Redistribution clause from Apache 2.0
> license
>
>
>
> I'm not even touching your security through obscurity trollbai
On 27 Feb 2013, at 18:50, Antoine Pitrou wrote:
> On Wed, 27 Feb 2013 16:51:16 +
> Michael Foord wrote:
>
>> Hello all,
>>
>> PyCon, and the Python Language Summit, is nearly upon us. We have a good
>> number of people confirmed to attend. If you are intending to come to the
>> language
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 upon us. We have a good
>> number of people confirmed to attend. If you are intending to come to the
>> language summit but haven't
On Feb 27, 2013, at 3:20 PM, anatoly techtonik wrote:
>
> * security by obscurity in legal position of PSF towards contributors
> https://code.google.com/legal/individual-cla-v1.0.html
>vs
> http://www.python.org/psf/contrib/contrib-form/ +
> http://www.samurajdata.se/opensource/mirro
On 28/02/13 07:20, anatoly techtonik wrote:
* as an exercise - try to build a scroller for a running Python script
* it is impossible for Python 2 and probably for Python 3 as well
What do you mean by "a scroller"?
[...]
and why PSF doesn't comply the 4. Redistribution clause fr
Le Wed, 27 Feb 2013 11:33:30 -0800,
"fwierzbi...@gmail.com" a écrit :
>
> There are a couple of spots that might be more controversial. For
> example, Jython has a file Lib/zlib.py that implements zlib in terms
> of the existing Java support for zlib. I do wonder if such a file is
> acceptable in
On Thu, Feb 28, 2013 at 1:37 PM, Barry Warsaw wrote:
> On Feb 27, 2013, at 11:33 AM, fwierzbi...@gmail.com wrote:
>>The easy part for Jython is pushing some of our "if is_jython:" stuff
>>into the appropriate spots in CPython's Lib/.
>
> I wonder if there isn't a better way to do this than sprinkl
Am 27.02.2013 17:51, schrieb Michael Foord:
> Hello all,
>
> PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
>
> The agenda of topics for
On Feb 27, 2013, at 04:51 PM, 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.
I'd like to have some discussions around promotion of Python 3, how we can
accelerate its adoption, availability of supporting packages, what cri
On Feb 27, 2013, at 11:33 AM, fwierzbi...@gmail.com wrote:
>I am suggesting that we push forward on the "shared library" approach to the
>files in the Lib/* directory, so that would certainly include IronPython and
>PyPy as well I hope.
+1
>The easy part for Jython is pushing some of our "if is_
On Wed, Feb 27, 2013 at 12:33 PM, fwierzbi...@gmail.com
wrote:
> There are a couple of spots that might be more controversial. For
> example, Jython has a file Lib/zlib.py that implements zlib in terms
> of the existing Java support for zlib. I do wonder if such a file is
> acceptable in CPython's
On Wed, Feb 27, 2013 at 7:51 PM, Michael Foord wrote:
> Hello all,
>
> PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
>
> The agenda of topi
On Wed, Feb 27, 2013 at 11:21 AM, Brett Cannon wrote:
> Do you mean more generally getting more pure Python implementations of
> modules in the stdlib? If so then as a reference there is
> http://bugs.python.org/issue16651 which lists the modules in the stdlib w/
> only extension module implementa
On Wed, Feb 27, 2013 at 2:01 PM, fwierzbi...@gmail.com <
fwierzbi...@gmail.com> wrote:
> On Wed, Feb 27, 2013 at 8:51 AM, 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.
>
> I'd like to discuss merging Jython's standa
On Wed, Feb 27, 2013 at 8:51 AM, 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.
I'd like to discuss merging Jython's standard Lib (the *.py files). We
have in the past had agreement that this would be a good idea - I ju
On Wed, 27 Feb 2013 16:51:16 +
Michael Foord wrote:
> Hello all,
>
> PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
>
> The agenda
On Wed, Feb 27, 2013 at 10:51 AM, Michael Foord
wrote:
> Hello all,
>
> PyCon, and the Python Language Summit, is nearly upon us. We have a good
> number of people confirmed to attend. If you are intending to come to the
> language summit but haven't let me know please do so.
>
> The agenda of t
Hello all,
PyCon, and the Python Language Summit, is nearly upon us. We have a good number
of people confirmed to attend. If you are intending to come to the language
summit but haven't let me know please do so.
The agenda of topics for discussion so far includes the following:
* A report on p
99 matches
Mail list logo
