Re: please help
On Tue, Feb 5, 2013 at 1:47 AM, ABHINAV MISRA wrote: > Sir I am going through the book "Django 1.0 Web Site Development" as > suggested. But i need to ask how can i contribute to django. I thought that > proposal needs to be submitted during gsoc so I thought to intereact with > the organisation so it will help me in building strong proposal and knowing > the project. > I've already answered this question. Triage bugs, provide feedback on Trac, and participate in django-developer discussions. You can find a detailed list of instructions and suggestions in our documentation: https://docs.djangoproject.com/en/1.4/internals/contributing/ Nobody is going to give you a specific list of things to do. You need to look around, find something that interests you, and get involved. Yours, Russ Magee %-) -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: please help
Sir I am going through the book "Django 1.0 Web Site Development" as suggested. But i need to ask how can i contribute to django. I thought that proposal needs to be submitted during gsoc so I thought to intereact with the organisation so it will help me in building strong proposal and knowing the project. Thanking you regards Abhinav Misra On Tuesday, 29 January 2013 07:13:39 UTC+5:30, Russell Keith-Magee wrote: > > > > On Mon, Jan 28, 2013 at 9:17 PM, ABHINAV MISRA > > > wrote: > >> I am Abhinav Misra, an undergraduate. >> I was going through the project ideas of GSoC 2012 so as to find any >> project of which I am capable of. >> There i came up with the project named: " improved error reporting ". I >> want to take this project as my GSoC 2013 project. >> Till now GSoC 2013 is not announced but even if it is not happening I >> would like to take it as a project for my summers this year . >> I am not sure whether the project is completed till yet or not ? >> > > The error reporting project is something that is ongoing -- error messages > and reporting can always be improved, so there will always be work to be > done. > > >> I know python and C and I am currently learning java. I use eclipse and >> also netbeans as my IDE. I am well versed with git. >> Please guide me as to how can i approach this project and what should i >> do to successfully complete this project >> > > The first step is to come up with a detailed proposal. The details on the > GSoC 2012 website is a just a high level proposal; in order to be accepted > as a GSoC student, you'll need to propose a set of concrete proposals for > what you want to achieve, and how long you think it will take to achieve > those goals. > > We're not expecting the GSoC process to start for a couple of months, so > you've got plenty of time to get familiar with the code, and start honing > your proposal. > > Yours, > Russ Magee %-) > -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: ModelForms and the Rails input handling vulnerability
Le 4 févr. 2013 à 14:35, Luke Plant a écrit : > I like Alex Ogier's solution of a sentinel "__all__" flag. This would be > introduced for ModelForm and UpdateView using a deprecation process, so > that a form without one of 'fields' or 'exclude' will raise a > PendingDeprecation warning initially, and eventually be illegal. > > Both the '__all__' shortcut and the use of 'exclude' will be plastered > with warnings in the docs, and the docs will be re-written to assume > that you are going to provide 'fields' (at the moment the opposite is > assumed). > > How does that sound? Hi Luke, This sounds like a good compromise between security and usability. I've created a ticket to avoid losing track of this topic again: https://code.djangoproject.com/ticket/19733 -- Aymeric. -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: ModelForms and the Rails input handling vulnerability
This is an old thread, but we never came to a conclusion. I'll respond to Anssi below, and then add my own ideas. > I find the option of raising warnings or errors on missing data > elements the best option forward. There is one unfortunate downside, > that is we can't do this for checkboxes. So, it would be possible to > have a hidden-editable checkbox field. I don't think this is a great solution at this point. The hidden-editable checkbox field is going to be backwards incompatible in a serious way, because many forms are rendered manually in HTML, and they will break. I'm not convinced that warnings are ever a useful security mechanism, because they are so easily ignored. In production, they are invisible by default, and in development they are only visible if you look at the devserver output. Further, when a warning is correct, it shouldn't be a warning, it should be an error. When the warning is in fact incorrect, then it is a nuisance, and can easily lead to people ignoring or silencing all warnings, unless we also provide an easy and very fine grained way to deal with them. Warnings that are only sometimes correct always do the wrong thing. This contrasts with deprecation warnings, for example, which are always correct - because the functionality is indeed going to go away, and you do need to do something about it, but it isn't an error because the code is working OK now. The presence of the warning encourages you to do the right thing to get rid of it - migrate your code. My idea: I think, given the lack of consensus in this thread, that we have to opt for a conservative option. I like Alex Ogier's solution of a sentinel "__all__" flag. This would be introduced for ModelForm and UpdateView using a deprecation process, so that a form without one of 'fields' or 'exclude' will raise a PendingDeprecation warning initially, and eventually be illegal. Both the '__all__' shortcut and the use of 'exclude' will be plastered with warnings in the docs, and the docs will be re-written to assume that you are going to provide 'fields' (at the moment the opposite is assumed). How does that sound? Luke -- "If you're not part of the solution, you're part of the precipitate." (Steven Wright) Luke Plant || http://lukeplant.me.uk/ -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Ticket 19237
Hi, Trying out Django 1.5 with one of my projects, I ran out with a bug dealing with this ticket, so I reopened it: https://code.djangoproject.com/ticket/19237#comment:14 I think that bug should be blocker, because in a normal case can remove a lot of information when executing a strip_tags method. Cheers, On Saturday, 17 November 2012 09:01:33 UTC, Chris Khoo wrote: > > Hi > > I was wondering if one of the core developers could have a look at ticket > #19237 and progress it forward - > https://code.djangoproject.com/ticket/19237 > > It basically makes django.utils.html.strip_tags a little smarter. > > Thanks > > Chris > -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Internationalization not working
sure thanks :)
On Mon, Feb 4, 2013 at 1:32 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Please ask questions about using Django on django-users.
> The topic of this list is the development of Django itself.
>
> Thanks,
>
> --
> Aymeric.
>
>
>
> Le 4 févr. 2013 à 07:35, Satendra Tiwari a
> écrit :
>
> Hi all,
>
> Language translation is not working for me, I want translation of my
> website in anyother language currently I am using Dutch(for experiment)
>
> I have done the following things:
>
> *settings.py*
> LANGUAGES = (
> ('en', 'English'),
> ('nl', 'Dutch'),
> )
>
> LANGUAGE_CODE = 'nl'
> LOCALE_PATH = 'C:/py/django/django_bookmarks/locale/nl/LC_MESSAGES/'
>
> MIDDLEWARE_CLASSES = (
> 'django.middleware.common.CommonMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> 'django.middleware.locale.LocaleMiddleware',
> )
>
> *django.po*
> msgid ""
> msgstr ""
> "Project-Id-Version: PACKAGE VERSION\n"
> [.] //other META DATA information
> "Plural-Forms: nplurals=2; plural=(n != 1)\n"
>
> #: .\templates\main_page.html.py:3 .\templates\main_page.html.py:5
> msgid "Welcome to Django Bookmarks"
> msgstr "Welkom bij Django Bladwijzers"
>
> please let me know where am i going wrong.
>
>
> regards
> satendra
>
> --
> 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-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> 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-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
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-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Internationalization not working
Please ask questions about using Django on django-users.
The topic of this list is the development of Django itself.
Thanks,
--
Aymeric.
Le 4 févr. 2013 à 07:35, Satendra Tiwari a écrit :
> Hi all,
>
> Language translation is not working for me, I want translation of my website
> in anyother language currently I am using Dutch(for experiment)
>
> I have done the following things:
>
> settings.py
> LANGUAGES = (
> ('en', 'English'),
> ('nl', 'Dutch'),
> )
>
> LANGUAGE_CODE = 'nl'
> LOCALE_PATH = 'C:/py/django/django_bookmarks/locale/nl/LC_MESSAGES/'
>
> MIDDLEWARE_CLASSES = (
> 'django.middleware.common.CommonMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> 'django.middleware.locale.LocaleMiddleware',
> )
>
> django.po
> msgid ""
> msgstr ""
> "Project-Id-Version: PACKAGE VERSION\n"
> [.] //other META DATA information
> "Plural-Forms: nplurals=2; plural=(n != 1)\n"
>
> #: .\templates\main_page.html.py:3 .\templates\main_page.html.py:5
> msgid "Welcome to Django Bookmarks"
> msgstr "Welkom bij Django Bladwijzers"
>
> please let me know where am i going wrong.
>
>
> regards
> satendra
>
> --
> 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-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
--
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-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
