Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #94083 > unrolled thread

Re: Should non-security 2.7 bugs be fixed?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Should non-security 2.7 bugs be fixed? Devin Jeanpierre <jeanpierreda@gmail.com> - 2015-07-18 19:33 -0700
    Re: Should non-security 2.7 bugs be fixed? Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-18 19:49 -0700
    Re: Should non-security 2.7 bugs be fixed? Rustom Mody <rustompmody@gmail.com> - 2015-07-18 20:52 -0700
      Re: Should non-security 2.7 bugs be fixed? Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-18 21:18 -0700
      Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Steven D'Aprano <steve@pearwood.info> - 2015-07-19 14:45 +1000
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-19 15:06 +1000
          Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-19 10:16 +0300
            Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-19 00:32 -0700
              Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-19 10:44 +0300
              Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Terry Reedy <tjreedy@udel.edu> - 2015-07-19 19:13 -0400
                Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-19 19:02 -0700
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Anuradha Laxminarayan <lanuradha@gmail.com> - 2015-07-18 23:25 -0700
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Terry Reedy <tjreedy@udel.edu> - 2015-07-19 04:26 -0400
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Tim Chase <python.list@tim.thechases.com> - 2015-07-19 07:56 -0500
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-20 04:07 +1000
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Tim Chase <python.list@tim.thechases.com> - 2015-07-19 14:55 -0500
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-20 07:16 +1000
          Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] wxjmfauth@gmail.com - 2015-07-20 00:43 -0700
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] MRAB <python@mrabarnett.plus.com> - 2015-07-19 23:13 +0100
        Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-20 20:30 -0700
          Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-21 13:43 +1000
            Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-20 23:11 -0700
          Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Laura Creighton <lac@openend.se> - 2015-07-21 10:10 +0200
            Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-21 12:10 +0300
              Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-21 19:18 +1000
                Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-21 13:13 +0300
              Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-21 11:34 +0100
              Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-07-21 20:39 +1000
                Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-21 13:54 +0300
                  Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-08-09 00:27 +0300
                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-08-09 09:29 -0700
                Re:  Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-22 06:34 -0700
                  OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Steven D'Aprano <steve@pearwood.info> - 2015-07-23 02:58 +1000
                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Laura Creighton <lac@openend.se> - 2015-07-22 19:17 +0200
                      Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-22 10:49 -0700
                        Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Laura Creighton <lac@openend.se> - 2015-07-22 20:14 +0200
                        Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-22 21:59 +0100
                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Steven D'Aprano <steve@pearwood.info> - 2015-07-23 03:21 +1000
                      Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-07-22 21:44 -0400
                      Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-23 12:00 +1000
                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Paul Rubin <no.email@nospam.invalid> - 2015-07-22 10:48 -0700
                      Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-22 10:51 -0700
                      Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-07-23 15:14 +1000
                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-22 11:09 -0700
                      Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-07-23 15:41 +1000
                        Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-23 23:59 +0300
                          Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-24 07:03 +1000
                            Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-24 00:29 +0300
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-23 22:50 +0100
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Laura Creighton <lac@openend.se> - 2015-07-23 23:52 +0200
                                Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-24 00:59 +0300
                                  Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-24 08:02 +1000
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Chris Angelico <rosuav@gmail.com> - 2015-07-24 08:00 +1000
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] MRAB <python@mrabarnett.plus.com> - 2015-07-23 23:01 +0100
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Laura Creighton <lac@openend.se> - 2015-07-24 00:19 +0200
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-23 23:56 +0100
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Grant Edwards <invalid@invalid.invalid> - 2015-07-24 00:07 +0000
                                Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-23 18:40 -0700
                                Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Paul Rubin <no.email@nospam.invalid> - 2015-07-23 19:03 -0700
                                  Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-23 20:16 -0700
                                  Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Grant Edwards <invalid@invalid.invalid> - 2015-07-24 14:13 +0000
                                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Paul Rubin <no.email@nospam.invalid> - 2015-07-24 08:45 -0700
                                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-24 16:58 +0100
                              Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-23 22:15 -0700
                      Re: OT Re: Math-embarrassment results in CS [was: Should non-security   2.7 bugs be fixed?] Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2015-07-23 18:57 +1200
                        Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-23 02:12 -0700
                        Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Rustom Mody <rustompmody@gmail.com> - 2015-07-23 05:52 -0700
                    Re: OT Re: Math-embarrassment results in CS [was: Should non-security 2.7 bugs be fixed?] Marko Rauhamaa <marko@pacujo.net> - 2015-07-23 11:24 +0300
          Re: Devanagari int literals [was Re: Should non-security 2.7 bugs be fixed?] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-07-21 18:57 +1000
      Re: Should non-security 2.7 bugs be fixed? Terry Reedy <tjreedy@udel.edu> - 2015-07-19 02:44 -0400
      Re: Should non-security 2.7 bugs be fixed? Terry Reedy <tjreedy@udel.edu> - 2015-07-19 05:11 -0400
        Re: Should non-security 2.7 bugs be fixed? Rustom Mody <rustompmody@gmail.com> - 2015-07-19 07:30 -0700
      Re: Should non-security 2.7 bugs be fixed? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-19 15:00 +0100
    Re: Should non-security 2.7 bugs be fixed? Steven D'Aprano <steve@pearwood.info> - 2015-07-19 14:45 +1000
      Re: Should non-security 2.7 bugs be fixed? Devin Jeanpierre <jeanpierreda@gmail.com> - 2015-07-19 18:20 -0700
        Re: Should non-security 2.7 bugs be fixed? Steven D'Aprano <steve@pearwood.info> - 2015-07-20 13:05 +1000
          Re: Should non-security 2.7 bugs be fixed? Devin Jeanpierre <jeanpierreda@gmail.com> - 2015-07-19 20:41 -0700
      Re: Should non-security 2.7 bugs be fixed? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-20 02:46 +0100
        Re: Should non-security 2.7 bugs be fixed? Rustom Mody <rustompmody@gmail.com> - 2015-07-19 19:16 -0700
          Re: Should non-security 2.7 bugs be fixed? Chris Angelico <rosuav@gmail.com> - 2015-07-20 12:59 +1000
          Re: Should non-security 2.7 bugs be fixed? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-20 11:59 +0100
          Re: Should non-security 2.7 bugs be fixed? Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-20 20:04 -0700
            Re: Should non-security 2.7 bugs be fixed? Rustom Mody <rustompmody@gmail.com> - 2015-07-20 20:15 -0700
              Re: Should non-security 2.7 bugs be fixed? Chris Angelico <rosuav@gmail.com> - 2015-07-21 13:33 +1000
              Re: Should non-security 2.7 bugs be fixed? Terry Reedy <tjreedy@udel.edu> - 2015-07-21 00:45 -0400
            Re: Should non-security 2.7 bugs be fixed? breamoreboy@gmail.com - 2015-07-21 14:22 -0700
              Re: Should non-security 2.7 bugs be fixed? Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-21 19:07 -0700
                Re: Should non-security 2.7 bugs be fixed? Terry Reedy <tjreedy@udel.edu> - 2015-07-22 02:51 -0400
                  Re: Should non-security 2.7 bugs be fixed? Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-22 16:37 -0700
      Re: Should non-security 2.7 bugs be fixed? Terry Reedy <tjreedy@udel.edu> - 2015-07-20 02:25 -0400
      Re: Should non-security 2.7 bugs be fixed? dieter <dieter@handshake.de> - 2015-07-20 08:58 +0200
      Re: Should non-security 2.7 bugs be fixed? Devin Jeanpierre <jeanpierreda@gmail.com> - 2015-07-20 00:13 -0700

Page 5 of 5 — ← Prev page 1 2 3 4 [5]

#94227

On 20/07/2015 03:16, Rustom Mody wrote:
> On Monday, July 20, 2015 at 7:16:50 AM UTC+5:30, Mark Lawrence wrote:
>> On 20/07/2015 02:20, Devin Jeanpierre wrote:
>>
>>>
>>> I don't like how this is being redirected to "surely you
>>> misunderstood" or "I don't believe you". The fact that some core devs
>>> are hostile to 2.x development is really bleedingly obvious, you
>>> shouldn't need quotes or context thrown at you. The rhetoric almost
>>> always shies _just_ short of ceasing bugfixes (until 2020, when that
>>> abruptly becomes a cracking good idea). e.g. in "2.7 is here until
>>> 2020, please don't call it a waste".
>>>
>>
>> A couple of things.
>>
>> First "some core devs are hostile", actually some have stated that
>> they're simply not interested in 2.7 and will not work on it.
>>
>> Second how has the thread got here, as it was originally asking about
>> back porting bug fixes from 3.x to 2.7?  Further it said:-
>>
>> <quote>
>> If the vast majority of Python programmers are focused on 2.7, why are
>> volunteers to help fix 2.7 bugs so scarce?
>> </quote>
>>
>> So I most humbly suggest, as I may have hinted at once or twice earlier
>> in this thread, that people either put up or shut up.
>
> I just ran the following command
> $ hg log --template "{author|person}\n" | sort | uniq -c | sort -nr
>
> as giving all the committers to python in sorted order.
> I get the list below.
> Dont see any Mark Lawrence there
> Of course I dont know hg at all well... Just picked up the above command from
> http://stackoverflow.com/questions/6126678/how-to-list-commiters-sorted-by-number-of-commits-commit-count
>
> So... May I humbly ask where are your precious commits??
>

Thank you for showing your complete ignorance as to how Python works.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

[toc] | [prev] | [next] | [standalone]

#94256

On Sunday, July 19, 2015 at 9:17:11 PM UTC-5, Rustom Mody wrote:


> List of python committers:
> -------------------------
>  11081 Guido van Rossum
> [snip: long list]

Thanks for posting this list of names. I had put in a pyFOIA
request for this data a few years ago, but to my surprise, was
flat out denied. I'm not sure how exhaustive this list may be,
but publicly displaying the "commit hierarchy" within the Python
community is very import for those who may want to get involved.

[Talking to Mark Lawrence, Rustom said:]
> So... May I humbly ask where are your precious commits??

Thanks for putting Mark in his place. He has been brow
beating folks on this list (myself included) for years, and
i'll bet he now feels as tiny as D'Aprano did -- when GvR
scolded him for disrespecting a Noob on Python-ideas.

  Yeah, i was watching! 

  I'M *ALWAYS* WATCHING!

  ಠ_ಠ

Now that Mark's lack of "commit cred" has been exposed, we can
safely ignore his hollow and hypocritical bullying. And now
that he has been de-fanged, he will be forced to seek employment
elsewhere. Hmm, my suggestion is that he market himself as an
on-call "peanut butter removal service". A venture that will
no doubt be successful, seeing that he has two "heads up" on
his competition! 

[toc] | [prev] | [next] | [standalone]

#94257

On Tuesday, July 21, 2015 at 8:34:30 AM UTC+5:30, Rick Johnson wrote:
> On Sunday, July 19, 2015 at 9:17:11 PM UTC-5, Rustom Mody wrote:
> 
> 
> > List of python committers:
> > -------------------------
> >  11081 Guido van Rossum
> > [snip: long list]
> 
> Thanks for posting this list of names. I had put in a pyFOIA
> request for this data a few years ago, but to my surprise, was
> flat out denied. I'm not sure how exhaustive this list may be,
> but publicly displaying the "commit hierarchy" within the Python
> community is very import for those who may want to get involved.
> 
> [Talking to Mark Lawrence, Rustom said:]
> > So... May I humbly ask where are your precious commits??
> 
> Thanks for putting Mark in his place. He has been brow
> beating folks on this list (myself included) for years, and
> i'll bet he now feels as tiny as D'Aprano did -- when GvR
> scolded him for disrespecting a Noob on Python-ideas.
> 
>   Yeah, i was watching! 
> 
>   I'M *ALWAYS* WATCHING!
> 
>   ಠ_ಠ
> 
> Now that Mark's lack of "commit cred" has been exposed, we can
> safely ignore his hollow and hypocritical bullying. And now
> that he has been de-fanged, he will be forced to seek employment
> elsewhere. Hmm, my suggestion is that he market himself as an
> on-call "peanut butter removal service". A venture that will
> no doubt be successful, seeing that he has two "heads up" on
> his competition!

Hey Rick!
Lets have a useful discussion
And cut the rhetoric
Please

[Chris already showed that this list is inaccurate -- probably related 
to hg not having sighoff distinct from commit like git]

[toc] | [prev] | [next] | [standalone]

#94261

On Tue, Jul 21, 2015 at 1:15 PM, Rustom Mody <rustompmody@gmail.com> wrote:
> [Chris already showed that this list is inaccurate -- probably related
> to hg not having sighoff distinct from commit like git]

It's also the manner of workflow. If you want to accept patches and
have them acknowledged to their original authors, the patches need to
carry metadata identifying the authors. I went to the tracker and hit
"Random Issue" and got one with an attached file as the first hit:

http://bugs.python.org/issue12982
http://bugs.python.org/file26008/issue12982.diff

Repeated the exercise and won again:

http://bugs.python.org/issue4733
http://bugs.python.org/file12437/urlopen_text.diff

Notice how the patch files start straight in with content. There's no
authorship information retained.

By comparison, a patch created with 'git format-patch' and applied
with 'git am' starts with RFC 822 headers, provides a commit message,
and generally is intended as a way of transmitting a *commit*, rather
than simply some changes. I'm not overly familiar with Mercurial
workflows, but I think 'hg export' and 'hg import' give the same sort
of information; I tried on CPython and got this:

# HG changeset patch
# User Robert Collins <rbtcollins@hp.com>
# Date 1436838700 -43200
#      Tue Jul 14 13:51:40 2015 +1200
# Branch 3.5
# Node ID 7021d46c490e8d9d3422737c69980dc1602f90db
# Parent  0127b0cad5ecb83c39ce58a4be27bf6d43a78d91
Issue #23661: unittest.mock side_effects can now be exceptions again.

This was a regression vs Python 3.4. Patch from Ignacio Rossi

diff -r 0127b0cad5ec -r 7021d46c490e Lib/unittest/mock.py
--- a/Lib/unittest/mock.py      Sat Jul 11 16:33:39 2015 -0700
+++ b/Lib/unittest/mock.py      Tue Jul 14 13:51:40 2015 +1200
@@ -506,7 +506,8 @@
         if delegated is None:

(chomp actual details)

Whether it's possible to have authorship retained or not, though, a
lot of patches can logically be credited to multiple people. Whose
name goes on it? With the CPython workflow, it's always the core
committer who applied it, nobody else. (That's consistent, at least.)
So the names in the log are of the people who have write access to the
repo, and nobody else.

ChrisA

[toc] | [prev] | [next] | [standalone]

#94268

On 7/20/2015 11:33 PM, Chris Angelico wrote:

> It's also the manner of workflow. If you want to accept patches and
> have them acknowledged to their original authors, the patches need to
> carry metadata identifying the authors. Notice how the patch files start straight in with content. There's no
> authorship information retained.
>
> By comparison, a patch created with 'git format-patch' and applied
> with 'git am' starts with RFC 822 headers, provides a commit message,
> and generally is intended as a way of transmitting a *commit*, rather
> than simply some changes. I'm not overly familiar with Mercurial
> workflows, but I think 'hg export' and 'hg import' give the same sort
> of information; I tried on CPython and got this:

hg has an option to produce git-format patches.  However, they do not 
work with the Rietveld code review tool, and so are discouraged.  I do 
not know if the extra information would survive an hg commit.

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#94318

On Tuesday, July 21, 2015 at 4:04:30 AM UTC+1, Rick Johnson wrote:
> On Sunday, July 19, 2015 at 9:17:11 PM UTC-5, Rustom Mody wrote:
> 
> 
> > List of python committers:
> > -------------------------
> >  11081 Guido van Rossum
> > [snip: long list]
> 
> Thanks for posting this list of names. I had put in a pyFOIA
> request for this data a few years ago, but to my surprise, was
> flat out denied. I'm not sure how exhaustive this list may be,
> but publicly displaying the "commit hierarchy" within the Python
> community is very import for those who may want to get involved.
> 
> [Talking to Mark Lawrence, Rustom said:]
> > So... May I humbly ask where are your precious commits??
> 
> Thanks for putting Mark in his place. He has been brow
> beating folks on this list (myself included) for years, and
> i'll bet he now feels as tiny as D'Aprano did -- when GvR
> scolded him for disrespecting a Noob on Python-ideas.
> 

Read on, oh great stupid one.

>   Yeah, i was watching! 
> 
>   I'M *ALWAYS* WATCHING!
> 
>   ಠ_ಠ
> 
> Now that Mark's lack of "commit cred" has been exposed, we can
> safely ignore his hollow and hypocritical bullying. And now
> that he has been de-fanged, he will be forced to seek employment
> elsewhere. Hmm, my suggestion is that he market himself as an
> on-call "peanut butter removal service". A venture that will
> no doubt be successful, seeing that he has two "heads up" on
> his competition!

Ever heard the saying "engage brain before putting mouth into gear"?  It was actually Rustom who posted inaccurate data as only core-devs have commit rights.  It would appear that your knowledge of the current development process is as good as your knowledge of European geography.  I would say enjoy your future in the "peanut butter removal service" but it is quite clear that you haven't the skills needed to make it happen.  In the mean time I'll quite happily carry on contributing to the Python community as best I can.

Oh, and while I think about it, you'd better put that shovel down, or the hole will only get deeper.

Have a nice day :)

[toc] | [prev] | [next] | [standalone]

#94339

On Tuesday, July 21, 2015 at 4:22:50 PM UTC-5, bream...@gmail.com wrote:

> It was actually Rustom who posted inaccurate data as only
> core-devs have commit rights.

Well-well. We now find ourselves before the royal court of
logic: If we are to take your statement as fact, then only
two possibilities exist:

  (a) Mark is a core dev who has committed patches and is a
  bully.
  
  (b) Mark is not a core dev, and therefor can not commit
  anything, therefor he's a bully *AND* a hypocrite!

Which is it?

> It would appear that your knowledge of the current
> development process is as good as your knowledge of
> European geography.

So you've been lurking in that thread also? As with this
thread, folks have mis-interpreted my words. When i get a
chance to respond over there, you shall become enlightened
and humbled.

[toc] | [prev] | [next] | [standalone]

#94347

On 7/21/2015 10:07 PM, Rick Johnson wrote:

> two possibilities exist:
>
>    (a) Mark is a core dev who has committed patches and is a
>    bully.
>
>    (b) Mark is not a core dev, and therefor can not commit
>    anything, therefor he's a bully *AND* a hypocrite!
>
> Which is it?

Mark is not a core dev, cannot commit, and as far as I know, has never 
claimed such.  However, he has participated on the tracker, has reviewed 
patches, and has submitted patches, at least one of which has been 
committed.  His user name is BreamoreBoy and his tracker email is the 
same breamore@ address that recently upset you.  'BreamoreBoy' has been 
nosy on at least 1483 issues, over half as many as me.

You, as 'RantingRick' have opened 1 issue, quickly closed, but not 
posted under than name on any others.
https://bugs.python.org/issue8970
You sent one patch to me which I applied.
Maybe there is some other activity that I missed.

I would prefer it if you both stopped snipping and sniping at each other.

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#94411

On Wednesday, July 22, 2015 at 1:51:57 AM UTC-5, Terry Reedy wrote:
> > Which is it?
> 
> Mark is not a core dev [...] However His user name is
> BreamoreBoy and his tracker email is the same breamore@
> address that recently upset you.

Thank you for confirming my suspicion. You have always been
honest, and that is why i carry a great respect for you. It
seems that D'Aprano's attempt at "gas lighting" me will not
only fail, but also expose him as one of the cohorts. It's
no surprise though, Steven & Chris & Mark have been bullying
me for years.

> I would prefer it if you both stopped snipping and sniping
> at each other.

I agree. But you don't need to convince me. Tell Mark, Chris
and Steven. The few times i did try to contribute i was
toyed with. (except for the one time i provided you with a
patch, of course). Why would i subject myself to those
childish games again? Until people start treating me like a
respected member, i'm going to be a thorn in the gluteus
maximus of this group. I can be either a friend or a foe --
their choice!

PS: One thing i have noticed, in my many years here, is
that: When the truth starts to support my argument, the
thread "mysteriously" forks on some OT subject, and usually
a subject that involves heavy emotional or philosophical
debate. Such as is the case now. I think the mainstream
media could learn a thing or two about diversionary tactics
simply from watching this group.

[toc] | [prev] | [next] | [standalone]

#94212

On 7/19/2015 9:20 PM, Devin Jeanpierre wrote:

> Search your logs for https://bugs.python.org/issue17094
> http://bugs.python.org/issue5315
>
> I was most frustrated by the first case --
 > the patch was (informally) rejected

By 'the patch', I presume you mean current-frames-cleanup.patch
by Stefan Ring, who said it "is certainly not the most complete 
solution, but it solves my problem.". It was reviewed a month later by a 
core dev, who said it had two defects.  Do you expect us to apply 
defective patches?

> in favor of the "right" fix,

"right" is your word. Natali simply uploaded an alternate patch that did 
not have the defects cited.  It went through 4 versions, two by Pitrou, 
before the commit and close 2 months later, with the comment "Hopefully 
there aren't any applications relying on the previous behaviour."

 >and the "right" fix was (informally) rejected because it changed behavior,

The bugfix was rejected *for both 2.7 and 3.3* in msg186011.  The 
rejection therefore does not indicate animus against 2.7 versus 3.x. The 
reason is that it did more than just fix the bug. When this is the case, 
we only apply to the upcoming release.  If we broke working code as a 
side-effect, as opposed to a direct effect, of a bugfix, many people 
would be frustrated. See some of the other comments in this thread.

Two years later, last May, you proposed and uploaded a patch with what 
looks to be a new and different approach.  It has been ignored.  In the 
absence of a core dev focused on 2.7, I expect that this will continue. 
Too bad you did not upload it in Feb 2013, before the review and fix 
started.

 > and http://bugs.python.org/issue5315

Another fairly obscure issue for most of us. Five years ago, this was 
turned into a doc issue, but no patch was ever submitted for either 2.x 
or 3.x.  Again, no particular prejudice against 2.x.

In May, you posted a bugfix which so far has been ignored.  Not too 
surprising.  I submitted a ping and updated the versions.  If anyone 
responds, you might be asked for a patch against 3.4 or 3.5.

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#94217

Mark Lawrence <breamoreboy@yahoo.co.uk> writes:
> ...
> So I most humbly suggest, as I may have hinted at once or twice
> earlier in this thread, that people either put up or shut up.

In another of your contributions to this thread, you spoke of another
alternative: "do a bit of begging". That is what some of us are doing.

[toc] | [prev] | [next] | [standalone]

#94219

I think you're missing the line where I said all the relevant
conversation happened in IRC, and that you should refer to logs.

On Sun, Jul 19, 2015 at 11:25 PM, Terry Reedy <tjreedy@udel.edu> wrote:
> On 7/19/2015 9:20 PM, Devin Jeanpierre wrote:
>
>> Search your logs for https://bugs.python.org/issue17094
>> http://bugs.python.org/issue5315
>>
>> I was most frustrated by the first case --
>
>> the patch was (informally) rejected
>
> By 'the patch', I presume you mean current-frames-cleanup.patch
> by Stefan Ring, who said it "is certainly not the most complete solution,
> but it solves my problem.". It was reviewed a month later by a core dev, who
> said it had two defects.  Do you expect us to apply defective patches?

No, I meant my patch. It was discussed in IRC, and I gave the search
term to grep for. (The issue URL.)

>> in favor of the "right" fix,
>
>
> "right" is your word. Natali simply uploaded an alternate patch that did not
> have the defects cited.  It went through 4 versions, two by Pitrou, before
> the commit and close 2 months later, with the comment "Hopefully there
> aren't any applications relying on the previous behaviour."

No, "right" is the word used by members of #python-dev, referrig to
Antoine's fix.

> Two years later, last May, you proposed and uploaded a patch with what looks
> to be a new and different approach.  It has been ignored.  In the absence of
> a core dev focused on 2.7, I expect that this will continue. Too bad you did
> not upload it in Feb 2013, before the review and fix started.

I'm not sure what you're implying here. It couldn't be helped.

>> and http://bugs.python.org/issue5315
>
> Another fairly obscure issue for most of us. Five years ago, this was turned
> into a doc issue, but no patch was ever submitted for either 2.x or 3.x.
> Again, no particular prejudice against 2.x.
>
> In May, you posted a bugfix which so far has been ignored.  Not too
> surprising.  I submitted a ping and updated the versions.  If anyone
> responds, you might be asked for a patch against 3.4 or 3.5.

Again, the prejudice was expressed in IRC. It was ignored because you
can just use asyncio in 3.x, and because the bug was old.

-- Devin

[toc] | [prev] | [standalone]

Page 5 of 5 — ← Prev page 1 2 3 4 [5]

Back to top | Article view | comp.lang.python

csiph-web