Re: Composite fields

On Mon, Mar 9, 2015 at 8:06 AM, Thomas Stephenson wrote: >> It doesn't result in good table design and adds restrictions/complication >> to the ORM/migrations. > > Well, honestly, making all subfields always nullable (whether it is or not) > in order to support the composite field being potentiall

Re: Composite fields

> It doesn't result in good table design and adds restrictions/complication to the ORM/migrations. Well, honestly, making all subfields always nullable (whether it is or not) in order to support the composite field being potentially nullable doesn't really result in good table design either. > En

Re: Prospective GSOC applicant for 2015

Hi Acho, You'll need to research the various questions posed in the project description and come up with a proposal. It'll be easier to give you further guidance after that. You might want to take a look at the existing Trac tickets under the "Testing framework" component for related issues to

Re: Gsoc 2015: SQLAlchemy / NoSQL integration

Hi Abhishek, I am the GSOC 2014 student who refactored the Meta API, please contact me if you need any details on my work, or if you want to know more about implementation and/or design of the new Meta API. You can also find me on IRC as pirosb3. Good luck! Daniel 2015-03-02 1:32 GMT+01:00 Russe

Re: CSRF cipher in xor + base64 or Vignere cipher

To be fair to the Vigenère cipher algorithm, it is insanely simple; I think when I wrote the implementation in that pull request, I was probably inappropriately using lambdas and generator expressions, and in doing so making it look more complicated than it really is. A neater, more readable Vigen

Re: Password validation in Django revisited

Hello Simon and Raphael, Thanks for your input. I’ve adopted all your suggestions into the PR. For the settings, I’ve now mirrored the TEMPLATE structure. I entirely agree that adding a new structure is an unnecessary burden on our users. I’m not too fond of Simon’s suggestion, as I’d like to h

Re: Password validation in Django revisited

Hi Erik, This looks promising. I like how the validators can be chained and the whole simplicity of the patch. Here's some comments I also left on the PR; 1. I think the settings should be name AUTH_PASSWORD_VALIDATORS since it's being use by the auth contrib app; 2. I would avoid mix

Re: Composite fields

-1 on silently changing the field definition. At best this would result in an unnecessary migration when the error is discovered. Django should error out with a message that the composite field definition is invalid. Regards, Michael Manfre On Sun, Mar 8, 2015 at 12:29 PM, Thomas Stephenson wrot

Re: Composite fields

On Sun, Mar 8, 2015 at 12:12 PM, Thomas Stephenson wrote: > @Aymeric > > Here's why I think the `isnull` column is necessary. > > Say you've got a custom field implementation: > > class Point(models.CompositeField): > x = models.IntegerField() > y = models.IntegerField() > # etc. >

Re: Composite fields

ps. There's a third option which I just thought of: class Point(...): x = models.IntegerField() y = models.IntegerField() z = models.IntegerField(null=True) def __init__(self, null=False, **kwargs): if null: x.null = y.null = True super(Point, self).__init__(**kw

Re: Password validation in Django revisited

Hi Erik, Am Sun, 8 Mar 2015 15:47:27 +0100 schrieb Erik Romijn : > I've taken another stab at 16860[1]: having a password > validation/policy in Django. I've made an initial simple PR[2] to > show the approach I'd like to use - no tests or documentation yet, > the example validators are not very n

Re: Composite fields

@Aymeric Here's why I think the `isnull` column is necessary. Say you've got a custom field implementation: class Point(models.CompositeField): x = models.IntegerField() y = models.IntegerField() # etc. and you use this to define a coordinate system to locate objects in your mode

Password validation in Django revisited

Hello all, I've taken another stab at 16860[1]: having a password validation/policy in Django. I've made an initial simple PR[2] to show the approach I'd like to use - no tests or documentation yet, the example validators are not very nice, possibly bad naming, etc. But this should be sufficien

Prefix use in reversing urls

Hi all, currently the reversing mechanism for urls accepts a prefix-kwarg [1], which is not documented [2]. It seems like this prefix is used to prefix the entire generated url and make script_name possible, to which it defaults. It is not used in the entire code base except for tests which ca

Re: how to run django in window 8

I think you should ask https://groups.google.com/forum/#!forum/django-users Here is a django-developers mailing list. *Best Regards！* *Chao Yan--About me ： http://about.me/chao_yan * *My twitter： @yanchao727 * *My Weibo： htt

Prospective GSOC applicant for 2015

Good day, My name is Acho Arnold Ewin and I am a junior student studying Software Engineering in the University of Buea in Cameroon (West Africa). I have been developing websites/webapps for 3+ years now. I'm very much interested in how technology can be used to change human lives especially

how to run django in window 8

What is the problem you are facing while installing django on windows. As far as remember its just a piece of cake. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop r

Re: how to run django in window 8

Hi, This group is for the development of django framework itself. for the type of problem you are facing better post your questions to https://groups.google.com/forum/#!forum/django-users regards On Sunday, March 8, 2015 at 8:07:20 AM UTC+6, Alok Rodhiya wrote: > > i spend the overnight in ins