Hi,
My name is Daniel Pyrathon. I am currently a third year BSc student in Computer Science at the University of Plymouth.
I love programming and I have always been active in the Open Source community (especially Python). In the past years I have written lots of Python, Javascript, Ruby, Java, and I am currently using C++ for many university projects. I have attended the last 3 EuroPython conferences and I have been a staff member of the conference for the last 2 years.
I am currently looking for a way to contribute to Django. Working on Django would increase my knowledge of the framework as well as let me share my own experience.
Reading the ideas list I found 2 of them that are very interesting for me, and so the reason behind this post is not only to present myself but also to discuss their feasibility.
Formalizing the Meta object
This task is very challenging because it digs in the internals of Django. I feel that I could learn a lot from it because I am very committed to refactoring and write most of my code in TDD. I have also experience with backwards compatibility.
Do you have any resources (code) I should read to get up to date and to understand better how it is currently implemented?
Improved error reporting
The idea of making people’s lives better by improving error messages is fundamental. There would be a lot to discuss: what type of imports would we want to mask? I have read BetterErrorMessages and would be happy to get started soon. My idea behind this task would be to expand on this ticket: what would be great is to add a web console with live REPL support, similar to what Werkzeug debugger does. This could be a great starting point and would lead to a better use of Django.
Said this, I have to be very honest. I have never contributed to Django up till now and I want to hear your feedback on which proposal would suit me best. However I learn a lot through experience and I am attracted by new and challenging tasks.
Also, it would be nice if I could have some suggestions on what to read and if there are some specific parts of the code I should be directed to.Hi,
My name is Daniel Pyrathon. I am currently a third year BSc student in Computer Science at the University of Plymouth.
I love programming and I have always been active in the Open Source community (especially Python). In the past years I have written lots of Python, Javascript, Ruby, Java, and I am currently using C++ for many university projects. I have attended the last 3 EuroPython conferences and I have been a staff member of the conference for the last 2 years.
I am currently looking for a way to contribute to Django. Working on Django would increase my knowledge of the framework as well as let me share my own experience.
Reading the ideas list I found 2 of them that are very interesting for me, and so the reason behind this post is not only to present myself but also to discuss their feasibility.
Formalizing the Meta object
This task is very challenging because it digs in the internals of Django. I feel that I could learn a lot from it because I am very committed to refactoring and write most of my code in TDD. I have also experience with backwards compatibility.
Do you have any resources (code) I should read to get up to date and to understand better how it is currently implemented?
Improved error reporting
The idea of making people’s lives better by improving error messages is fundamental. There would be a lot to discuss: what type of imports would we want to mask? I have read BetterErrorMessages and would be happy to get started soon. My idea behind this task would be to expand on this ticket: what would be great is to add a web console with live REPL support, similar to what Werkzeug debugger does. This could be a great starting point and would lead to a better use of Django.
Said this, I have to be very honest. I have never contributed to Django up till now and I want to hear your feedback on which proposal would suit me best. However I learn a lot through experience and I am attracted by new and challenging tasks.
Also, it would be nice if I could have some suggestions on what to read and if there are some specific parts of the code I should be directed to.
Formalizing Meta
Enabling users to build custom stores that work well with Django
2) Security implications. Unfortunately, more than one site has been launched with debug=True accidentally left on; all you need to do then is stimulate a server error, and you have REPL shell access to the server. This strikes me as a remarkably effective foot-gun :-) Before you get too involved in the implementation, I'd want to know the security issues have been locked down.
--To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ad5d6016-2c6a-45b4-91c8-0e4500befc74%40googlegroups.com.