|
⇤ ← Revision 1 as of 2011-03-10 13:19:12
Size: 839
Comment:
|
← Revision 2 as of 2011-03-10 16:54:57 ⇥
Size: 1816
Comment: base description
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| metaclasses, __new__, 2.6 properties, etc... | This project would consist in enhancing pylint underlying library (astng) to understand things it doesn't yet, such as metaclasses, __new__, 2.6 properties, etc... Expected skills: good knowledge of python language, including meta-object protocol, ability to grasp hairy code |
| Line 15: | Line 17: |
| Provide static descriptions of some classes, ease control of inference for dynamic classes there are in web frameworks for instance | The aim of this project would be to define and implement a way to provide static descriptions of some classes, and also to allow control of inference for dynamic classes (such as found in web frameworks for instance), making pylint (more) usable in case where it's not yet. That would implies working on underlying astng library as well. |
| Line 17: | Line 19: |
| Expected skills: good knowledge of python language, ability to grasp hairy code | |
| Line 20: | Line 23: |
| to be developped | Python3 brings type annotation to the language. This project would be to enhance pylint current type inference by using this information, Expected skills: good knowledge of python language, ability to grasp hairy code |
| Line 25: | Line 30: |
| to be developped | This project consist in thinking and implementing a new way to use pylint for new-comers, where it would help them in learning the langage (and sometime general programmation). Expected skills: knowledge of python language, ability to sketch a new-comer application |
PyLint Ideas for GSoC 2011
The best way to get started is to join our XMPP room at public@conference.jabber.logilab.org and/or mailing list at python-projects@lists.logilab.org.
Remember that applicants are required to commit code to be eligible for acceptance, though this may be after their application is submitted. The contributed code need not be in the same area as their proposal would have them working in.
improve understanding of code
This project would consist in enhancing pylint underlying library (astng) to understand things it doesn't yet, such as metaclasses, new, 2.6 properties, etc...
Expected skills: good knowledge of python language, including meta-object protocol, ability to grasp hairy code
make inference customisable
The aim of this project would be to define and implement a way to provide static descriptions of some classes, and also to allow control of inference for dynamic classes (such as found in web frameworks for instance), making pylint (more) usable in case where it's not yet. That would implies working on underlying astng library as well.
Expected skills: good knowledge of python language, ability to grasp hairy code
benefit from python3 annotations
Python3 brings type annotation to the language. This project would be to enhance pylint current type inference by using this information,
Expected skills: good knowledge of python language, ability to grasp hairy code
pylint as an interactive tool to help learning python
This project consist in thinking and implementing a new way to use pylint for new-comers, where it would help them in learning the langage (and sometime general programmation).
Expected skills: knowledge of python language, ability to sketch a new-comer application