Inconsistent humanize naturaltime (#18202)

[rikuthero...@gmail.com]

Hi folks,

I was about to start fixing ticket
#18202,
and I have a little doubt of how to focus that ticket. The workaround
proposed by "oradoe" seems good and works fine, but that will allow to show
only one level, like "10 minutes ago", "2 hours ago" or "4 months ago". As
it's propose on the ticket, maybe add some extra parameter to the filter to
allow that the user can specify how many deep levels he wants.

The problem there is that the filter uses
django.utils.timesince,
that actually only returns 2 levels as maximum. Should I change thoset
functions too? I think it won't be difficult to change it and maintain the
current behavior as the default one, but I would like to check it with you
before.

Cheers,

-- 
Pablo Recio Quijano

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[rikuthero...@gmail.com]

The one that Giovanni did is really nice, I like it!

2012/4/29 Juan Pablo Martínez 

> http://imgur.com/a/186fh
> nice :)
>
> On Sun, Apr 29, 2012 at 4:07 PM, Giovanni Collazo wrote:
>
>> I liked what Dana Woodman did, so I did a design based on that.
>>
>> Here: http://imgur.com/a/186fh
>>
>> --
>> @gcollazo
>> gcoll...@24veces.com
>>
>> On Sunday, April 29, 2012 1:32:13 PM UTC-4, Dana Woodman wrote:
>>>
>>> This is my take: 
>>> http://cl.ly/**0U2C1O20133i0U3d1s3X/o
>>>
>>> --
>>> Dana Woodman
>>> d...@danawoodman.com
>>> http://www.danawoodman.com
>>>
>>> On Sunday, April 29, 2012 at 9:23 AM, Alec Taylor wrote:
>>>
>>> Here is a design I just pulled up: http://i.imgur.com/wIkel.png
>>>
>>> Thoughts?
>>>
>>> On Mon, Apr 30, 2012 at 1:34 AM, Alec Taylor 
>>> wrote:
>>>
>>> Contact me for UX once you have forked the repo, I'll throw something
>>> up and place it on the wiki (or in an issue) of that new repo.
>>>
>>> Email: alectayl...@gmail.com
>>>
>>> On Sun, Apr 29, 2012 at 10:33 AM, Dana Woodman 
>>> wrote:
>>>
>>> Great info Russ, thanks!
>>>
>>> My thoughts at this point would be to focus on the main content sections,
>>> including the home page and documentation overview pages.
>>>
>>> For the home page I'd see something like this working well:
>>>
>>> -Logo and brief project description (fork on Github as well?) - Answers
>>> the
>>> "What is Django?" and "Why should I care?" questions. (for example,
>>> Twitter
>>> Bootstraps's home page: 
>>> http://cl.ly/**3R0d1X300S0S0f0A0j0S
>>> )
>>> Link to download and docs - Answers the "How can I start?" question
>>> "Who uses Django?" section - Answers, well... the "Who uses Django?"
>>> question. BTW, is there a reason that there isn't more of the larger
>>> users
>>> of Django on here?  Eg Disqus, Instagram, Pinterest, Google, Mahalo,
>>> addons.mozilla.org, etc... This alone would get people excited to use
>>> Django
>>> and would convince a lot of the business types that Django can scale and
>>> is
>>> worth the investment.
>>> A graphical site navigation area, eg: http://cl.ly/**
>>> 3B1N2h3E2x3x0f3V091K  -
>>> Give people a an easy way to get around to the core content on the site.
>>>
>>>
>>> Thinking a layout along the lines of Node.js (http://nodejs.org
>>> /) homepage
>>> would be effective. Node does a good job of keeping things minimal and
>>> easy
>>> to navigate.
>>>
>>> Some sort of "blogroll" type feature would satisfy the need to update the
>>> community of interesting or useful links. This could work in concert with
>>> the documentation as well. Not sure what the exact needs for this are,
>>> what
>>> would be an ideal process for this?
>>>
>>> How would the style guide be presented? Would it be a page on
>>> djangoproject.org, Github Wiki, a PDF, or...?
>>>
>>> I assume it would be fairly straightforward to give Spinx a new skin?
>>>
>>> Do you feel an incremental approach would be best or should it be a
>>> complete
>>> overhaul in one go?
>>>
>>> --
>>> Dana Woodman
>>> d...@danawoodman.com
>>> http://www.danawoodman.com
>>>
>>> On Saturday, April 28, 2012 at 4:49 PM, Russell Keith-Magee wrote:
>>>
>>> Hi Dana
>>>
>>>
>>> On Sunday, 29 April 2012 at 1:45 AM, Dana Woodman wrote:
>>>
>>> Very true Chris. I'd love to see the documents that were put together
>>> when
>>> this was discussed last time, if they're still around.
>>>
>>> I've included the design brief in my response to Ned. If you're looking
>>> for
>>> something else in particular, let me know and I'll see if I can find (or
>>> produce) something that is suitable.
>>>
>>>
>>> In regards to what needs improvement, there are some core issues as I see
>>> it.
>>>
>>> 1) the home page does a poor job of conveying what someone should do if
>>> they
>>> want to try out Django. It also could do a much better job of making
>>> Django
>>> a bit more "sexy".
>>> 2) the documentation itself, while thorough, is a bit difficult to
>>> navigate,
>>> especially for new users. I think this could be partially remedied by
>>> some
>>> modifications to headers and color choices.
>>> 3) the project could do a better job of selling itself, especially in
>>> regards to showcasing why it is so great: automatic admin, large active
>>> community and plugins, large sites and organizations using it, active
>>> development, lots of built in security, etc...
>>> 4) it just looks old and outdated, which is a problem in its own right.
>>>
>>> Should I just fork the project on Github and hack away or do I need to
>>> work
>>> on subversion?
>>>
>>> As of yesterday, we are a SVN-free organisation -- everything is on
>>> GitHub.
>>> However, djangoproject.com has been on GitHub for a while:
>>>
>>> https://github.com/django/**djangoproject.com
>>> If you want to work on code directly, that's the place to start.
>>>
>>>
>>> In regards to organization of the d

Re: 'ascii' codec can't encode characters in position 0-8: ordinal not in range(128)

[rikuthero...@gmail.com]

The problem is, I think, that you're trying to insert a non-ascii string,
inside an ascii string:

def __unicode__(self):
return 'name: {0}, url: {1}'.format(self.name, self.url)

Probably, self.name is an unicode string, and you're trying to put it on a
non-unicode string. Try this:

def __unicode__(self):
return u'name: {0}, url: {1}'.format(self.name, self.url)

It may work. If it doesn't look for "smart_unicode" and "force_unicode"
Django functions.

Regards

2011/2/22 Alexander Bolotnov 

> I fixed this by change the unicode to return self.name - but why was this
> failing anyway?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>



-- 
Pablo Recio Quijano

Desarrollador Django
Yaco Sistemas - http://www.yaco.es/

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

#16869 - BaseGenericInlineFormSet does not use form's save() method

[rikuthero...@gmail.com]

Hello,

As described on the ticket [1], I attach a patch that changes the behaviour
of "save_new" method in order to use the form's "save" method. Is the patch
correct, or there's something to improve?

Thanks in advance

[1] https://code.djangoproject.com/ticket/16869
[2]
https://code.djangoproject.com/attachment/ticket/16869/save_new_using_form_save.patch

-- 
Pablo Recio Quijano

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

#17028 - diveintopython.org links now dead

[rikuthero...@gmail.com]

Hello,

As described on the ticket [1], it seems that diveintopython.org is dead, so
I changed every occurence for  the mirror http://diveintopython.nfshost.com/,
that it seems to be the most updated. The changes are on the patch attached
in the ticket [2].

Best regards

[1] https://code.djangoproject.com/ticket/17028
[2]
https://code.djangoproject.com/attachment/ticket/17028/diveintopython_mirror_doc.patch

-- 
Pablo Recio Quijano

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #17028 - diveintopython.org links now dead

[rikuthero...@gmail.com]

Both have the content updated since 20 May 2004, so the content it's the
same, and I think is better to have a smaller URL, and it has no header
banner like the one from web.archive.org

But as I said, the content is really the same, so there should be no problem
changing it.

2011/10/12 Jeremy Dunck 

> How about:
> http://web.archive.org/web/20110726001211/http://diveintopython.org/
> ?
>
> On Wed, Oct 12, 2011 at 2:37 AM, rikuthero...@gmail.com
>  wrote:
> > Hello,
> >
> > As described on the ticket [1], it seems that diveintopython.org is
> dead, so
> > I changed every occurence for  the mirror
> > http://diveintopython.nfshost.com/, that it seems to be the most
> updated.
> > The changes are on the patch attached in the ticket [2].
> >
> > Best regards
> >
> > [1] https://code.djangoproject.com/ticket/17028
> > [2]
> >
> https://code.djangoproject.com/attachment/ticket/17028/diveintopython_mirror_doc.patch
> >
> > --
> > Pablo Recio Quijano
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django developers" group.
> > To post to this group, send email to django-developers@googlegroups.com.
> > To unsubscribe from this group, send email to
> > django-developers+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/django-developers?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Pablo Recio Quijano

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #17028 - diveintopython.org links now dead

[rikuthero...@gmail.com]

Those mirrors are from Dive into Python 3, is not the one linked from the
Django docs.

2011/10/12 Dougal Matthews 

>  Mirrors are appearing in a number of places for this and the html5
> version. Its hard to know which are more likely to stick around.
>
> http://diveintopython3.ep.io/
> https://github.com/diveintomark/diveintopython3
>
> Dougal
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Pablo Recio Quijano

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #17028 - diveintopython.org links now dead

[rikuthero...@gmail.com]

Hello,

Sorry, it seems that I miss that last point. I'll try to re-read the
contribution docs and work better in the proper way.

Thanks and sorry again.

2011/10/12 Russell Keith-Magee 

> On Wed, Oct 12, 2011 at 5:37 PM, rikuthero...@gmail.com
>  wrote:
> > Hello,
> >
> > As described on the ticket [1], it seems that diveintopython.org is
> dead, so
> > I changed every occurence for  the mirror
> > http://diveintopython.nfshost.com/, that it seems to be the most
> updated.
> > The changes are on the patch attached in the ticket [2].
> >
> > Best regards
> >
> > [1] https://code.djangoproject.com/ticket/17028
> > [2]
> >
> https://code.djangoproject.com/attachment/ticket/17028/diveintopython_mirror_doc.patch
> >
> > --
> > Pablo Recio Quijano
>
> Hi Pablo,
>
> Thanks for your recent work on patches for Django.
>
> However, as it notes in the last bullet point in the contribution
> guide about reporting bugs [1] -- you don't have to post to
> Django-developers just to tell us that you've added a patch. Anyone
> interested in watching for new patches can subscribe to django-updates
> and get automatically notified of *all* updates to Trac.
>
> The only reason to post to Django-dev is if you're looking for
> specific guidance on a patch -- for example, if you need confirmation
> that you''re taking the right approach in a fix, advice on where to
> put tests, and so on.
>
> Keep up the great contributions!
>
> [1]
> https://docs.djangoproject.com/en/1.3/internals/contributing/#reporting-bugs
>
> Yours,
> Russ Magee %-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Pablo Recio Quijano

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.