Re: FYI: Scheduled downtime on djangoproject.com Thursday night

2013-01-29 Thread Jacob Kaplan-Moss 
On Tue, Jan 29, 2013 at 6:27 PM, Russell Keith-Magee
 wrote:
> Of course, this is Mongolian Standard Time, correct?

Naturally :)

Bleh. PST. Sorry 'bout that!

Jacob

-- 
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: FYI: Scheduled downtime on djangoproject.com Thursday night

2013-01-29 Thread Russell Keith-Magee 
On Wed, Jan 30, 2013 at 1:11 AM, Jacob Kaplan-Moss wrote:

> Hey folks --
>
> MediaTemple, our hosting provider for djangoproject.com, is going to
> be taking our server offline Thursday night while they give us more
> RAM.
>
> The window for downtime is some time between 9PM and 4AM, though the
> actual downtime itself should be less than an hour.
>

Of course, this is Mongolian Standard Time, correct?

:-)

Russ %-)

-- 
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

2013-01-29 Thread Russell Keith-Magee 
On Tue, Jan 29, 2013 at 3:39 PM, nimesh ghelani wrote:

> Hi,
> I am also interested in Django as organization for GSoC. I did few basic
> projects using Django and now as a final test, i am putting my all in for
> my hardcode 13 submission. After that, i believe i will have a month and a
> half before GSoC is announced. Can you guide me on how to make the most of
> that time? As of now my approach will be as suggested in the website, going
> through tickets, observing the patches and trying to contribute in any way
> i can.
>

Two ways you can prepare:

 * Get involved in the community. Triage bugs, provide feedback on Trac,
participate in django-developer discussions. Then, when you submit your
proposal, you won't just be a name on an application -- you'll be someone
we know, because we've been working with you.

 * Start working on your project proposal. You won't be able to submit it
for a couple of months, but that doesn't mean you can't start working on it
now. Post it to django-developers and ask for feedback. If you start now,
you have an advantage -- you have an extra couple of months to get reviews,
and you won't be competing with other students for the attention of
reviewers.

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: Writing class-based contrib.admin actions

2013-01-29 Thread Luke Plant 
On 29/01/13 12:53, Timmy O'Mahony wrote:
> At the moment, writing custom admin actions
> 
> requires an old style view function that returns a Response object. The
> signature for this is similar to a old function-based view (except with
> modeladmin before request): 
> 
> func(modeladmin, request, queryset):
> ...
> return HttpResponse()
> 
> I wanted to write an action with an intermediate page
> ,
> but using class based views (for uniformity across my app). This doesn't
> seem to be doable without writing a custom base View object

Changing the signature would be backwards incompatible (or very hacky).

You can always do:

  def my_admin_action(modeladmin, request, queryset):
  return MyView.as_view(request, modeladmin, queryset)

And then take it to the next step:

  my_admin_action = cbv_to_admin_action(MyView)


Luke


-- 
"I am going to let you move around more, just to break up the
mahogany." (True Quotes From Induhviduals, Scott Adams)

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: Simplify the default project template

2013-01-29 Thread Aymeric Augustin 
Hello,

I took into account the feedback received here and on IRC (thanks everyone!) 
and I now have a branch ready for review:

https://github.com/aaugustin/django/compare/simplify-project-template

The commit messages give some hints about the reasoning behind each change. 
I'll be glad to provide more detailed explanations if necessary.

Like Jacob said, everyone here would certainly do this a bit differently. Let's 
avoid bikeshedding — if you can't resist, tell me in private — and look for 
problems such as:
- I got the priorities wrong: forgot something important / included 
something useless,
- I missed some best practices,
- I did something that's likely to trip up beginners,
- etc.

I plan to commit this next week. Let me know if you'd like more time to review.

Thank you,

-- 
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.

FYI: Scheduled downtime on djangoproject.com Thursday night

2013-01-29 Thread Jacob Kaplan-Moss 
Hey folks --

MediaTemple, our hosting provider for djangoproject.com, is going to
be taking our server offline Thursday night while they give us more
RAM.

The window for downtime is some time between 9PM and 4AM, though the
actual downtime itself should be less than an hour.

Since most people use the site for documentation, I'll remind you that
you can always find a mirror of Django's documentation on Read the
Docs: http://django.readthedocs.org/.

Thanks!

Jacob

-- 
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: Writing class-based contrib.admin actions

2013-01-29 Thread Timmy O'Mahony 
Thinking about this more, this might be better suited to a third party 
module that helps write admin actions - similar to django-crispy-forms etc. 

On Tuesday, 29 January 2013 13:53:19 UTC+1, Timmy O'Mahony wrote:
>
> At the moment, writing custom admin 
> actionsrequires
>  an old style view function that returns a Response object. The 
> signature for this is similar to a old function-based view (except with 
> modeladmin before request): 
>
> func(modeladmin, request, queryset):
> ...
> return HttpResponse()
>
> I wanted to write an action with an intermediate 
> page,
>  
> but using class based views (for uniformity across my app). This doesn't 
> seem to be doable without writing a custom base View object 
> that
>  interprets the 
> view args in a different order. By switching the function signature for 
> actions and putting the request first, wouldn't this it very easy to plugin 
> class based views when writing actions. 
>
> Does this make sense and is it worth a feature request (or a bit more 
> research)? 
>
> Timmy
>

-- 
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.

Writing class-based contrib.admin actions

2013-01-29 Thread Timmy O'Mahony 
At the moment, writing custom admin 
actionsrequires
 an old style view function that returns a Response object. The 
signature for this is similar to a old function-based view (except with 
modeladmin before request): 

func(modeladmin, request, queryset):
...
return HttpResponse()

I wanted to write an action with an intermediate 
page,
 
but using class based views (for uniformity across my app). This doesn't 
seem to be doable without writing a custom base View object 
that
 interprets the 
view args in a different order. By switching the function signature for 
actions and putting the request first, wouldn't this it very easy to plugin 
class based views when writing actions. 

Does this make sense and is it worth a feature request (or a bit more 
research)? 

Timmy

-- 
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

2013-01-29 Thread nimesh ghelani 
Hi,
I am also interested in Django as organization for GSoC. I did few basic 
projects using Django and now as a final test, i am putting my all in for 
my hardcode 13 submission. After that, i believe i will have a month and a 
half before GSoC is announced. Can you guide me on how to make the most of 
that time? As of now my approach will be as suggested in the website, going 
through tickets, observing the patches and trying to contribute in any way 
i can.

On Tuesday, January 29, 2013 7:13:39 AM 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.