On 02 avril 11:41, Claudiu Popa wrote:
> Yes, I'll have a look. I have two pull requests which could get into 1.2:
> 
> https://bitbucket.org/logilab/pylint/pull-request/95/add-new-warning-eval-used
> and 
> https://bitbucket.org/logilab/pylint/pull-request/98/add-new-checks-for-class-slots.

Ok, so you merged the first one. I've added some comments to the second one.
I've also integrated patches provided by Torsten/Google.

On my side, here is the before-release-todo-list:

* progress on
  
https://bitbucket.org/logilab/pylint-brain/pull-request/13/infer-builtin-exceptions-at-build-time-and
  would be nice, but not required. This is not in the shape I would like to see
  it, though my idea seems potentially problematic due to the bootstrap issue
  mentioned by Claudiu

* 
https://bitbucket.org/logilab/astroid/issue/13/python-3-pylint-cant-check-package-source
  would be nice also, though I probably won't have the time to work on this

* pylint pull request triage: merge the ready-and-not-controversial ones,
  provide/ask feedback for others

* pylint issues triage: close the resolved, open the acknowledged new ones, ask
  feedback when necessary, and see if there are some show-stopper (probably not)

Any help, notably on the two last points, is very welcome.
-- 
Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
CubicWeb, the semantic web framework:    http://www.cubicweb.org
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects

Reply via email to