On 20/03/12 07:18, Sachin Gupta wrote:
Could you guide me what number of error fixes would be good work for GSOC proposal. Also if there are any class of Django errors that are of greater concern (like django.db)
There's no clearly defined "number" that would be good - we'll be looking at your schedule that's on the proposal, instead, to make sure that you've scheduled the fixes with the right amount of time and that you've got enough work.
As for which ones are of greater concern, that's a difficult question to answer - everyone has their own "favourite" (my particular nemesis is the Postgres transaction-is-aborted one). I'd suggest looking through django-users, StackOverflow, etc., to get an idea of what's tripping people up the most.
For the error message OperationalError: Unable to close due to unfinalised statements The context is not correct. I tried using a file that does not have write permission for sqlite3, but the error that came up is not what is listed above. The error message was quite appropriate in this case django.db.utils.DatabaseError: attempt to write a readonly database So is there something which I am not getting correctly?
I'm not sure - I've never had that one myself. It might have only been with a previous version of the sqlite library or Python binding - have a look through the history on the wiki page to see when it was put in there, and by whom.
Andrew -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
