Re: Combine localflavor apps again

On Sun, May 26, 2013 at 8:07 PM, Jannis Leidel wrote: > > On 24.05.2013, at 19:28, Trey Hunner wrote: > > > On Tuesday, May 21, 2013 5:51:11 AM UTC-7, Jannis Leidel wrote: > > So what I propose to fix this is simple: > > > > - combine the localflavor

Handling tests in django-localflavor-*

Hi :-) I'm currently looking through the test-integration of the localflavor packages and due to the structure used here it looks like (as Erik found out before me) it kind of lends itself to something like nose as testrunner. For this we both integrated test_settings module into the respective

Re: I'm interested in maintaining localflavor-at

Thank you :-) > Aymeric Augustin <mailto:aymeric.augus...@polytechnique.org> > May 21, 2013 5:10 PM > 2013/5/21 Horst Gutmann <ho...@zerokspot.com <mailto:ho...@zerokspot.com>> > > > If nobody else volunteers, I'd like to help by maintaining the >

I'm interested in maintaining localflavor-at

Hi :-) If nobody else volunteers, I'd like to help by maintaining the localflavor-at package. First working order should be to get it it somehow onto PyPI (depending on the outcome of Jannis' proposal). Username on IRC and Github: zerok Best wishes, Horst -- You received this message because

Re: facebook/twitter sharing, and testing

Hi :-) Please ask such questions on the django-users mailinglist. https://groups.google.com/forum/?fromgroups#!forum/django-users This here is for discussions about the development of django itself :-) Cheers, Horst On Wed, Apr 10, 2013 at 4:35 PM, sara ismail

Re: Django 1.5 with Python 3.2

This is documented here: https://docs.djangoproject.com/en/dev/topics/python3/#str-and-unicode-methods:-) Cheers, Horst On Mon, Apr 8, 2013 at 4:42 PM, L Radhakrishna Rao wrote: > I was following tutorials of django book, where python 2.7 version is used. > > I am

Re: Re-design "proposal" for djangoproject.com

On Sat, May 19, 2012 at 6:06 PM, Giovanni Collazo wrote: > Hi, > > So, I spend a few hours working on the re-design following Idan's > Guidelines. Any feedback and further direction from the core team would be > greatly appreciated. > > G. > Hi :-) Looks nice! A few points

Re: Localization on User model

On Thu, Sep 22, 2011 at 1:52 PM, Aymeric Augustin wrote: > 2011/9/22 lvella : >> What about changing this in future versions? Maybe simply a >> "true_name" field would do? Or maybe a way to customize the fields in >> the User model. > > Hi

Re: settings.py should have way to hide key/values even when debug set True

On Mon, Jan 31, 2011 at 5:02 PM, Matteius wrote: > I think it would be really useful to have a way (possibly a decorator > such as @hide_setting) such as to protect deployed sites when they > switch over to debug mode.  To me this would be a most useful setting > to have,

Re: Proposal for inclusion of two additional default template tags.

On Fri, Jan 7, 2011 at 5:41 PM, Jonathan S wrote: >> Regarding the macro-tag I think the idea is valid but I'd personally >> prefer a more flexible approach regarding variables being  provided >> for the macro block. Something like Jinja's macro comes to mind where >>

Re: Proposal for inclusion of two additional default template tags.

On Fri, Jan 7, 2011 at 5:18 PM, Dougal Matthews wrote: > On Friday, 7 January 2011 at 16:11, Jonathan S wrote: > > ** And a {% decorate %} template tag: > http://paste.pocoo.org/show/316593/ > > I think they are generic enough to be included. > {% decorate %} implements a

Re: parse xml

I so hope this response was the result of some translation gone wrong. If not, you shouldn't really expect anyone to answer your (highly off- topic) question with that attitude... On Oct 15, 7:56 pm, kostia wrote: > Give me the answer and do what you want. > > On Oct

Re: Regression problem on admin date format

> I have confirmed the bug with other non speaking people and I have >>>> sent an e-mail to django-i18n group to point out the problem. >>>> >>>> I have also contacted Marc and he has confirmed that the problem exists. >>>> >>>&

Re: Regression problem on admin date format

Did the patch that is attached to this issue work for you? It would really be nice to get some feedback on it :-) From what I've heard in other posts on this and the django-users list so far it seems to do the job. -- Horst P.S.: Sorry if this mail reaches you a second time. Somehow Google

Re: Class based generic views in 1.3?

On Sat, May 29, 2010 at 11:06 PM, Ben Firshman wrote: > Luke, you're absolutely right that changing the definition of a view is a bad > idea, it just seemed the best solution then. > > But don't worry, we've changed our minds again! If __call__() creates a copy > of self

Re: Date format localization problem (Django displays dates in format it doesn't accept)

Did you already try the patch I attached at http://code.djangoproject.com/ticket/13621 ? Perhaps this solves your problem too :-) On Fri, May 28, 2010 at 4:50 PM, Ludwik Trammer wrote: > Hi, > > There is quite a serious problem with Django 1.2's format localization > and

Re: Proposal for 1.2: built-in logging with django.core.log

Definitely a +1 from me. -- Horst On Thu, Sep 17, 2009 at 10:25 AM, Simon Willison wrote: > > I think we should add logging to Django in version 1.2, implemented as > a light-weight wrapper around the Python logging module > (django.core.log maybe?) plus code to write

Re: EuroPython Sprints

Same here. If I can make it to EuroPython I'll try really hard to be there for the sprints. -- Horst On Wed, May 20, 2009 at 11:59 AM, Robert Lofthouse wrote: > > I'm scheduled to give a talk there and if I can definitely make it > then I'll be going to the sprints as

Re: Dropping Python 2.3 compatibility for Django 1.1

Big +1 from me. Finally real decorators, generators and not to forget sets as built-in type :D -- Horst On Tue, Nov 25, 2008 at 7:04 PM, Brian Rosner <[EMAIL PROTECTED]> wrote: > > On Tue, Nov 25, 2008 at 10:08 AM, Jacob Kaplan-Moss > <[EMAIL PROTECTED]> wrote: >> >> Hi folks -- >> >> I'd like