Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Daniel Pyrathon
Hi Colin, Thanks for getting back On Monday, August 18, 2014 4:58:20 PM UTC+2, Collin Anderson wrote: > > The goal is to have "API methods that let you introspect the fields and > relations that exist on a model", right? Why go though the trouble of > finding the one specific type for each fiel

Re: Proposal: Password Validity Layer

2014-08-18 Thread Florian Apolloner
Validation errors are only caught inside form validation. Forms set the password usually in save, not in clean, so I don't think that patch covers it (or at least the relevant forms have to call validate_password in clean too) On Monday, August 18, 2014 5:31:05 PM UTC+2, Keith Hackbarth wrote:

Re: help with ZINNIA

2014-08-18 Thread James Bennett
Two things: 1. This is django-developers, the list for discussing the development of Django itself. For questions about using Django or Django-based applications, please use the django-users mailing list. 2. You've just shared your SECRET_KEY setting publicly with thousands of people who received

help with ZINNIA

2014-08-18 Thread antonio vangi
Hallo, sorry could someone help me fi installation of zinnia. My pip freeze: BeautifulSoup==3.2.1 Django==1.4.5 PIL==1.1.7 Pillow==2.5.2 South==1.0 argparse==1.2.1 beautifulsoup4==4.3.2 django-blog-zinnia==0.11.1 django-contrib-comments==1.5 django-mptt==0.5.5 django-tagging==0.3.2 django-xmlrpc=

Re: Proposal: Password Validity Layer

2014-08-18 Thread Collin Anderson
Wow. That's simple. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to dja

Re: Proposal: Password Validity Layer

2014-08-18 Thread Keith Hackbarth
Tim, et al., I've coded up a proof of concept here. I'd be very interested in your feedback. https://github.com/keithhackbarth/django/commit/c0897dd4b3d49e39246d1e74d636e32862881451 Thank you, Keith On Thursday, August 7, 2014 7:04:40 PM UTC-6, charettes wrote: > > We could override `AbstractB

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Collin Anderson
Also, I think we should avoid discriminating between "virtual" and non-virtual (as with local vs parent). Why should it matter how a field is stored in the database? I think the distinction will make it harder to use non-relational databases. It maybe helpful to recognize if a field has a "pare

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Collin Anderson
The goal is to have "API methods that let you introspect the fields and relations that exist on a model", right? Why go though the trouble of finding the one specific type for each field (that we'll never be able to change later)? Why have a get_fields() method with an ever-growing number of kw

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Daniel Pyrathon
Hi Shai, Thanks for getting back, so.. On Monday, August 18, 2014 1:44:49 PM UTC+2, Shai Berger wrote: > > Hi again, > > Below, ">D" are quotations from Daniel's message I'm replying to, and > ">R" are from Russell's message that opened this thread. > > >D *Regarding FileField* > > It took m

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Daniel Pyrathon
Hi Anssi With regards to Michal Petrucha's changes, I have the feeling you are correct. A solution to this could be to provide a cached property called **foreign_keys** that will disguise the actual identity of a ForeignKey. Once the Michael's changes are introduced, we could start deprecating

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Shai Berger
Hi again, Below, ">D" are quotations from Daniel's message I'm replying to, and ">R" are from Russell's message that opened this thread. >D *Regarding FileField* It took me some time to clear for myself why FileField is a data field, and not like FK: The point is not where the data is stored

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Ivan Kharlamov
On 08/18/2014 02:03 PM, Anssi Kääriäinen wrote: > As for changing ForeignKey to virtual field plus concrete field > representation - I just realized this will be backwards incompatible no > matter what we do regarding categorization. An all-fields including > get_fields() call will return separate

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Anssi Kääriäinen
On Monday, August 18, 2014 7:45:17 AM UTC+3, Russell Keith-Magee wrote: > > I understand what you're driving at here, and I've had similar thoughts > over the course of the SoC. The catch is that this makes the API for > get_fields() fairly complicated. > > If every field fits into one specific t

Re: GSoC Meta refactor: Bikeshedding time!!

2014-08-18 Thread Daniel Pyrathon
Hi All, First of all, thanks Russell for bringing this discussion up. *Regarding get_fields complication* Throughout the development of this project, I have realised that 90% of the API usage inside and outside of Django can rely entirely on 4 or 5 cached properties. The most used API calls are