Re: Epydoc failed to generate documentation for Django 1.5

Take a look at the generic views auto-generated docs from Epydoc(link in my post), it's definitely breathtaking. Especially seeing how all the classes come together in a nice UML graph. It really provides some prospective on how hard the core Django developer work and think over a process

Re: Epydoc failed to generate documentation for Django 1.5

On Wed, Apr 3, 2013 at 10:19 PM, Kevin Veroneau wrote: > Is this Epydoc error related to Epydoc or something that Django shouldn't > have done in it's source code? It looks perhaps like something you'd need to fix -- the message about settings.configure() indicates that

Epydoc failed to generate documentation for Django 1.5

Hello Django team, I was attempting to build documentation for Django 1.5, and it seems that Epydoc doesn't like something in the GIS contrib in the tests.py module. Here is the beginning of the error, see the attached text file for the full stacktrace: | In

Re: URLField should allow scheme to be empty

After poking around a bit[1], it appears that URLFields are used almost exclusively for canonical links to webpages, and are not typically used as, say, the target of internal redirects, or resources that are loaded on a page. In addition, it looks like the code from ticket 5331 that automatically

Re: Remove download_url from setup.py

On Wed, Apr 3, 2013 at 7:46 PM, Russell Keith-Magee wrote: > > On Wed, Apr 3, 2013 at 5:29 PM, Donald Stufft wrote: >> >> Just an idea. >> >> I think it might make sense to remove the download_url from setup.py. It >> has caused problems in the past >>

Re: Remove download_url from setup.py

On Wed, Apr 3, 2013 at 5:29 PM, Donald Stufft wrote: > Just an idea. > > I think it might make sense to remove the download_url from setup.py. It > has caused problems in the past ( > http://www.djangoproject.com/m/bad-installer.txt) and I don't think > leaving it there adds

Re: Kickstarter for Django Admin?

On Sunday, March 31, 2013 9:46:59 AM UTC-7, Serge G. Spaolonzi wrote: > > > On Sat, Mar 30, 2013 at 7:20 PM, Victor Hooi > wrote: > >> >> From the existing projects, we can draw two clear requirements that >> people want: >> >>- Changing the look and feel - I'm not

Re: URLField should allow scheme to be empty

As per RFC 3986 (see section 4, in particular 4.2) all of the following are valid: Absolute URI http://www.example.com/images/xyz.png Network path reference //www.example.com/images/xyz.png Suffix reference (frowned upon but valid?) www.example.com/images/xyz.png Absolute path reference

Re: Django Core mentorship list

Ahem: [1] https://groups.google.com/forum/?fromgroups#!forum/django-core-mentorship :) On Wed, Apr 3, 2013 at 11:44 AM, Jeremy Dunck wrote: > Hey all, > I've just created django-core-mentorship[1] with founding members > including Carl Meyer, Jacob Kaplan-Moss, Simon

Re: URLField should allow scheme to be empty

Don't add an option, it's not needed. URLs with blank schemas are valid, it's just a bug that Django adds 'http://' in that case. So make a ticket, +1 from me. Best, Alex Ogier On Wed, Apr 3, 2013 at 4:24 PM, Juan Pablo Martínez wrote: > I love it. > If URLField has an option

Re: URLField should allow scheme to be empty

I love it. If URLField has an option like "scheme_required=False" or something like that. No behaviour is the "correct", append or not append scheme. The option to our needs seems to be more correct. Regards, On Wed, Apr 3, 2013 at 5:14 PM, SteveB wrote: > How to avoid

URLField should allow scheme to be empty

How to avoid those browser warnings about mixing secure and insecure content on a web page? Wouldn't it be great to be able to specify a URL for a resource (be it a script, image, iframe etc.) such that if the current page is insecure (using a http:// scheme) the content would be fetched using

Django Core mentorship list

Hey all, I've just created django-core-mentorship[1] with founding members including Carl Meyer, Jacob Kaplan-Moss, Simon Charette, and Russell Keith-Magee. Modeled after pythonmentors.com, the intention is to help more people make the leap from using django to contributing to it. It is a

Re: Django 1.5.1 released

On Tue, Apr 2, 2013 at 11:02 PM, Russell Keith-Magee wrote: > In short, no - Twitter isn't a particularly reliable source for updates. > Someone in the core team will usually tweet about the release, but since > it's hard to share logins to a single Twitter account, and

Re: Django 1.5.1 released

That makes sense, thanks for the explanation and the pointers to the best sources of information. I never realized the Django announce mailing list existed, it will serve my purposes perfectly as I'm sure it's intended to! Regards, Josh On Apr 2, 9:02 pm, Russell Keith-Magee

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

Re: URL dispatcher fallthrough?

I think it's esoteric enough that mentioning it in the docs doesn't seem like it's worth the distraction. But the wiki's, um, a wiki... so feel free to edit! Jacob On Wed, Apr 3, 2013 at 9:07 AM, Felipe Prenholato wrote: > Jacob, I know that Django don't refer to third

Re: Kickstarter for Django Admin?

I have a point about kickstarter powered projects. Anyone can send one, but in my opinion only projects extensively discussed here with a complete roadmap can have success. Actually I think that it also should have mentors, like GSOC, while aproved by community via money. Also, Andrew proposal is

Re: URL dispatcher fallthrough?

Jacob, I know that Django don't refer to third party packages in docs, but is possible to have something in doc or wiki (and doc linking to wiki) about this url helper (and possible others)? I ask because I see functionality proposed by this thread and by your app good enough to be cited in some

Re: Django 1.5 using a cached HttpResponse with WSGI has an empty body

I created a ticket for this problem: https://code.djangoproject.com/ticket/20187 -- 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

Re: Django 1.5 using a cached HttpResponse with WSGI has an empty body

Hi Aymeric, Thanks for your reply. Actually I'm just using a memory cache for the response, so I'm not pickling it. My thoughts are: 1. The __iter__ method of a HttpResponse should create an instance of a separate iterator class to iterate over the container. It should not return

Remove download_url from setup.py

Just an idea. I think it might make sense to remove the download_url from setup.py. It has caused problems in the past (http://www.djangoproject.com/m/bad-installer.txt) and I don't think leaving it there adds much value. It does however add yet another place that a package releaser needs to