Built-in router link generator in Django

Folks, I am wondering if Django would benefit from the inclusion of this package or something like it? https://github.com/un33k/django-menuware A utility module to auto generate links from configuration. Thanks, Val -- You received this message because you are subscribed to the Google Grou

rotate_token via test client in 1.7a2

Just wondering if CSRF token should be also rotated when accessed via unittest client. Middleware is in place and rotation happens via a browser. Bug or intended behaviour, or perhaps a misuse ? # Example self.client = Client(enforce_csrf_checks=True) resp = self.client.g

Re: APPEND_SLASH skip per URL or per base_uri

Hi Aymeric, Localized solution is fine, but when I saw the number posts from people who were trying to find a solution to this, I thought, perhaps it would be a nice little enhancement to the APPEND_SLASH functionality. Thanks, Val On Thursday, 13 March 2014 17:12:51 UTC-4, Val Neekman

Re: APPEND_SLASH skip per URL or per base_uri

t; url(r'^profile$', views.profile, name='profile', append_slash=False), > > (with a dollar sign at the end of the regex pattern). > > > On Thu, Mar 13, 2014 at 4:19 PM, Ryan Hiebert wrote: > >> In your example, APPEND_SLASH >> >> >> On Th

APPEND_SLASH skip per URL or per base_uri

Some JavaScript frameworks(e.g. AngularJS) remove the ending slash before making a request. If APPEND_SLASH = True, then the API would not be consumable by AngurlarJS. Would it be a good idea to add options to disable the APPEND_SLASH behaviour per *url()*, or per a *base_uri*? *Example 1:* *se

Re: #20824 - Email-based auth contrib module; some help required

The following may be a viable solution for the case-insensitive fields. (email, username, alias ... etc.) Look at lines: 23, 66 and 159. https://gist.github.com/un33k/9273782 Val On Fri, Feb 28, 2014 at 5:05 AM, Tilman Koschnick wrote: > On Thu, 2014-02-27 at 08:43 +0800, Russell Keith-Mag

Re: Testing 1.7a2 -- pre_migrate and post_migrate (py2.7)

Yeah, I do remember times where I had to put the signal handlers in the urls.py in order to lazyfy them, hence, avoiding the circle-dance. Of course, they would not fire via the management commands. Ok, good to have the AppConfig.ready() for that. Thanks, Alight, Perhaps, I should create a ticke

Re: Testing 1.7a2 -- pre_migrate and post_migrate (py2.7)

Is the following statement still valid? "Any handlers that listen to this signal need to be *written* in a particular place: a management module in one of your INSTALLED_APPS. If handlers are *registered* anywhere else

Re: Why SlugField overrides get_internal_type()?

Oh, I see. Thanks Carl. Val On Fri, Feb 7, 2014 at 6:14 PM, Carl Meyer wrote: > Hi Val, > > On 02/07/2014 04:07 PM, Val Neekman wrote: > > None of the other subclasses of CharField override get_internal_type() > > but the SlugField and I am wondering why? > > &g

Why SlugField overrides get_internal_type()?

None of the other subclasses of CharField override get_internal_type() but the SlugField and I am wondering why? Class SlugField(CharField): def get_internal_type(self): return "SlugField" Thx, Val -- You received this message because you are subscribed to the Google Groups "Djan

Re: Django 1.7 - Named migration directory

that to a different place if they want to ship the app > like that, achieving exactly the result you want without an extra setting > per app :) > > Andrew > > > On Mon, Dec 23, 2013 at 11:57 PM, Val Neekman wrote: > >> I am wondering if it would be a good idea for a dja

Django 1.7 - Named migration directory

I am wondering if it would be a good idea for a django app to name its migration directory and if nothing is provided then the name would default to 'migrations'. The case: (let's call it a GEO app) GEO app looks at the setting.py file for a flag called "GEO_USING_GEO_DJANGO". # in models.py if

Re: Getting user's real IP address in Django

. Val On Sun, Dec 22, 2013 at 7:30 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > > On Mon, Dec 23, 2013 at 7:27 AM, Val Neekman wrote: > >> Majority of the sites/apps built on Django *may* require user's real IP >> address for tracking, p

Re: Getting user's real IP address in Django

*correction*: It should read: "*may I propose*" instead of "may I purpose". Thanks, Val On Sun, Dec 22, 2013 at 6:27 PM, Val Neekman wrote: > Majority of the sites/apps built on Django *may* require user's real IP > address for tracking, prevention, veri

Getting user's real IP address in Django

Majority of the sites/apps built on Django *may* require user's real IP address for tracking, prevention, verification and many other reasons. To get (guess) user's real IP address, one must check few META fields in a particular order to peel off the proxies. This is what lot of Django developers

Re: South data-migration and custom save() method

hod does). > > Andrew > > > On Fri, Dec 20, 2013 at 4:15 PM, Val Neekman wrote: > >> South (latest) has a limitation where it ignores a custom save() method >> in the model class. >> >> I am wondering if that is going to be true for the new South in the

South data-migration and custom save() method

South (latest) has a limitation where it ignores a custom save() method in the model class. I am wondering if that is going to be true for the new South in the core in Django 1.7? Thanks, Val -- You received this message because you are subscribed to the Google Groups "Django developers" grou

Custom Users + Signals (reusable app)

Folks, I am to release an app as a reusable app. However, the app makes the use of post_save signals raised by the User model and there is a problem. With the limitation of a Custom User + Signals in mind, I cannot really call it a "true" reusable app, if it doesn't work for setups that have roll

Ability to save 4xx messages to database

I am wondering if it would be a good idea to save a copy of *404s* in database instead of sending the email out to the ADMIN. The reason is, while I see a notification of some sort beneficial, with sites that items are added and deleted on a regular basis, all those 404 messages (emails) can be co

Re: Ticket 20147 - deprecate and replace request.META

+1 for leaving META alone. On Apr 8, 2013, at 7:45 PM, Russell Keith-Magee wrote: > > On Tue, Apr 9, 2013 at 5:13 AM, Carl Meyer wrote: >> Hi Luke, >> >> On 04/08/2013 02:02 PM, Luke Plant wrote: >> > This is already the subject of a ticket, but I didn't get a response >> > yet. Basically,

Re: Kickstarter for Django Admin?

The beauty of kickstarter is that people speak with their wallets. If a project doesn't have a merit, then no one would pitch in and that would be the end of the project. Django admin is a great tool. In my projects I use it for quick view and edits so I don't have to fallback to command line or S

Re: URL dispatcher fallthrough?

+1 here! It might also be a great feature to run the 404 through before sending that email out. A replacement and/or complement to IGNORABLE_404_URLS Val On Tue, Mar 26, 2013 at 1:25 PM, Loic Bistuer wrote: > +1 for me. > > Having a catchall view under a single URL pattern is a tightly coupled

Re: New additions to django.contrib?

Awesome news indeed. Thx On Fri, Mar 22, 2013 at 12:58 PM, Mateusz Harasymczuk wrote: > About your topic on adding South to Django core. > Andrew is working on that: > https://www.djangoproject.com/weblog/2013/mar/22/kickstarting-schema-migrations-django/ > > -- > You received this message becaus

Re: Goodbye, Malcolm

Met him for the first time in DjangoCon 2012. What a down to earth guy. He'll be missed. Val Sent from my mobile device. On 2013-03-19, at 3:25 PM, Leon Matthews wrote: > On 20 March 2013 06:01, Jacob Kaplan-Moss wrote: >> We have difficult news: Malcolm Tredinnick has passed away. > > Wh

GeoDjango International Date Line (IDL) handling

My previous email got messed up (ended up in a different thread), so I am sending again. -- If you build a geom with a bounding box that contains IDL (International Date Line) and run a point__within query on it, then the result is unpredictable and incorrect.

Re: GeoDjango and __within query when IDL is involved

I must have hit reply on my iPhone instead of new email. Not meant to be a response to your email. Sorry about the confusion. Sent from my iPad On Mar 18, 2013, at 5:40 AM, Omer Katz wrote: > Sorry, how is this related? > > בתאריך יום ראשון, 17 במרץ 2013 19:34:53 UTC+3, מאת Va

GeoDjango and __within query when IDL is involved

If you build a geom with a bounding box that contains IDL (International Date Line) and run a point__within query on it, then the result is unpredictable and incorrect. Does anyone know of a native GeoDjango solution to this? If not, would there be a lot of resistance against a patch that inco

Re: Changes to django's settings module

d today for me, so maybe I will try writing up some of the > practices that make managing settings easier for me later tonight. > > Best, > Alex Ogier > > > On Thu, Mar 14, 2013 at 9:16 AM, Val Neekman wrote: >> >> Yeah, split by role is what I have done. >>

Re: Changes to django's settings module

Yeah, split by role is what I have done. settings/default.py (absolute necessities) settings/deploy.py (inherits default.py & adds production specifics) settings/debug.py (inherits deploy.py & overwrites debug stuff) settings/test.py (inherits deploy.py & overwrites test specific) settings/externa

Re: Proposal: deprecate and remove django.contrib.comments

Yep. +1 Val Sent from my mobile device. On 2013-03-07, at 11:48 AM, Jacob Kaplan-Moss wrote: > Hi folks -- > > This one's simple: I'd like to deprecate `django.contrib.comments`, > scheduling it to be removed in a couple of releases. > > My rationale is this: if you don't really care much a

Re: Why is GeoDjango in core ?

Yeah, it's amazing that we have GeoDjango included as I'm using it right now. However I can fall back to geopy and still getaway with rough acceptable estimates with limited scope and capability which I'm fine with. (In my use case) If I had to choose between GeoDjango and South as a core pack

Re: Custom user models in 1.5, not flexible/dry enough?

is definitely going in the right direction. Val On Tuesday, 20 November 2012 16:37:17 UTC-5, Val Neekman wrote: > > I have used Django extensively on few "big" projects, yet I consider > myself a newbie when it comes to Django (core). > > As soon as the Class-B

Re: Custom user models in 1.5, not flexible/dry enough?

I have used Django extensively on few "big" projects, yet I consider myself a newbie when it comes to Django (core). As soon as the Class-Based views were released, I read the docs and tried to port my "then" ongoing project to the new Classy views. I have to say that I *agree with Russell* on t