Re: GSOC 2015 project ideas suggestion

It still doesn't interest me enough to provide any additional feedback. On Thursday, March 26, 2015 at 1:20:42 AM UTC-4, Asif Saifuddin wrote: > > Hi, > > I have been updating my proposal and as the deadline is friday Your > feedback will help me to make it better in technical point of view > >

Re: Pre-DEP: community support of unmaintained versions of Django

Hi Carl, James, Sorry for the late reply on this. I've been unavailable the past week. I know you guys are still sorting out how you want to run this, but I wanted to let you know that, given our current dependence on Python 2.6, I'm willing to do what's needed to maintain security backports

Re: GSoC 2015: Improved URL Pattern Matching (Draft)

Hi Alexander, I won’t repeat what Russell said, just add a few things. A few months ago I had a use case for internationalization that looked pretty simple but turned out to be tricky to implement: https://github.com/oscaro/django-o18n . Resolving is

Re: GSoC 2015: Improved URL Pattern Matching (Draft)

Russ - Thanks a ton for the feedback. I really appreciate you taking the time to look over my proposal. On Wednesday, March 25, 2015 at 11:11:02 PM UTC-4, Russell Keith-Magee wrote: > > Hi Alex, > > On Thu, Mar 26, 2015 at 7:03 AM, Alexander Patel < > alexand...@college.harvard.edu > wrote:

Re: Help needed with Oracle GIS backend

Hi Jani. On Wednesday 25 March 2015 09:58:00 Jani Tiainen wrote: > > We're still running Oracle and GIS. Though we do have built custom > backend based on Django GIS backend - mainly to have support for > Oracle XE, 3D functionality and in general to make it faster. > > It's currently closed

Re: Help needed with Oracle GIS backend

Before the fellowship started, I worked a bit on Oracle GIS to fix it up and get its tests passing, but I'm unsure if I should continue to try to do so as part of my duties in the absence of anyone else stepping up. Clearly if no one uses this backend, it's wasted effort. Should we try

Re: Two phase cleaning of models/forms

In particular it is worth noting the addition of form.add_error[1] in Django 1.7 which makes long clean methods much nicer to handle. [1] https://docs.djangoproject.com/en/1.7/ref/forms/api/#django.forms.Form.add_error On 25 March 2015 at 16:11, Carl Meyer wrote: > Hi Thomas,

Re: Extending the URL Dispatcher (GSoC 2015 proposal)

I've updated my proposal with a few more changes. Specifically, I've added a small part about reversing namespaced urls without specifying the namespace. In some circumstances this can provide looser coupling between third-party apps and arbitrary, reversible objects. It can also ease the

Re: improving debug logging in development

Hi All, A little off topic, but here's what I do to generate "yellow" html tracebacks in production behind the scenes: from django.views import debug html = debug.ExceptionReporter(request, is_email=False, *sys.exc_info()). get_traceback_html() Though, I do that within the

Re: improving debug logging in development

What about the yellow 500 error-page when in debug-mode? I'd like to have a copy of the complete thing *somewhere* now that what's sent by email is sanitized. Cloning a running system, turning DEBUG on and attempting to trigger the same error isn't always easy. Is the 500-data loggable at all? On