I'm sorry if I was misunderstood, I just wanted to know if a ticket exist for this problem (I didn't find it myself). I will create one. Did you have more details to put in the ticket for the reviewer? Just for clarification, I'm not part of the logilab team, so I will not comment on your remarks. Just want to thank again you for your participation.
2012/8/15 George Sakkis <george.sak...@gmail.com> > I'm sorry but I've already spent more time and effort than 99% of > casual contributors are expected to spend in 2012, namely: > > - Looked for a "submit new ticket" link or button on the tracker page, > didn't find one, figured it doesn't allow anonymous tickets. > - Signed up for yet another site account I'll probably won't have to > visit again. > - Emailed to python-proje...@logilab.org 10 days ago, got an > auto-reply that my email is being held until the list moderator can > review it for approval, reason being "Post by non-member to a > members-only list". WTF was the signup for if I am still not a member? > - Somehow found the Mailman page and registered for yet another > useless (to me) mailing list, powered by ugly antiquated software. > - Posted the email that actually appeared on the list, including a > clean patch with updated passing tests. > - Was asked to jump through one more hoop to create a ticket on the > tracker for whatever policy/bookkeeping reasons. > - I tried to login to logilab.org for creating the ticket and was > welcomed by an an invalid SSL certificate. > - After adding a temporary certificate exception, I got authentication > failure. Not very likely given that I use LastPass for auto generating > and entering passwords. > - Oh what the hell, let's pretend I forgot my password and enter my > email and captcha for recovery. > - Password recovery email arrives but it's broken too: > """ > If you requested this password change, please set a new password by > following the link below: > > None > """ > - That's it, screw it; I'm out. > > Bottom line, if your site is not hacked (which wouldn't surprise me at > all after all these red flags), it's horribly broken. Apologies for > the rant but It's ridiculous to have to go through all this BS in > 2012, when for most other projects I would have forked them, pushed my > patch and made a pull request in less time than it took me to figure > out how am I supposed to contribute to pylint. > > George > > > On Tue, Aug 14, 2012 at 8:31 PM, Boris FELD <lothiral...@gmail.com> wrote: > > First thanks for your patch. I can confirm the problem but I can't find a > > corresponding ticket on pylint ticket tracker. If there is no ticket, > could > > you please create one? > > I can confirm the problem and your test has caught it. > > Your patch work for me, I will push it in review as soon as I get a > ticket > > number. > > > > Thank you for participating on pylint. > > FELD Boris, > > GSOCer on pylint > > > > 2012/8/12 George Sakkis <george.sak...@gmail.com> > >> > >> Hi, > >> > >> the attached patch fixes the false positive W0231 warning in case the > >> base __init__ is inherited from object. > >> > >> George > >> > >> _______________________________________________ > >> Python-Projects mailing list > >> Python-Projects@lists.logilab.org > >> http://lists.logilab.org/mailman/listinfo/python-projects > > > > > _______________________________________________ > Python-Projects mailing list > Python-Projects@lists.logilab.org > http://lists.logilab.org/mailman/listinfo/python-projects >
_______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
