Re: The problem of versioning a large project.

ch are created for each application. > > > > why? what's the reasoning for this? django already has apps, so why do you > need to make multiple projects for single components? > On Friday, March 31, 2023 at 10:15:06 AM UTC-4 cha...@gmail.com wrote: > >> >&g

The problem of versioning a large project.

The problem of versioning a large project. Hi guys, I really got stuck with the challenge, with the design of versioning for a large project. Now we have organized versioning, where our project is divided into separate GIT repositories which are created for each application. The new necessit

Re: Can we move the activity on this list to the Forum now?

o A) speak up saying they want it done B) test the underlying API to verify that it actually solves the problem. Alex On Fri, Jan 20, 2023 at 2:24 AM Carlton Gibson wrote: > OK, I've updated the Trac wiki page to point to the forum too. (We use > this as a wiki-link in responses

Re: Revisiting multiline template tags in Django Templates (again)

Hi Thibaud, I don't have many contributions to Django, but FWIW, I'm happy to help with development. On Wednesday, September 28, 2022 at 1:42:11 PM UTC+3 carlton...@gmail.com wrote: > Hey Thibaud. > > Thanks for following up! Yes — happy to sheppard. > > (My other comment was to make sure t

Re: __slot__ like behaviour for Model classes?

ield name on the model and raise an error. This way the migration would have failed and the transaction would have been reverted, rather than committing without any of the data I was trying to save into the new column. Alex On Sunday, September 2, 2007 at 11:07:16 AM UTC-4 Jay Parlar wrote: &g

Re: Google Groups contingency plan

k like whatever. (If you don't get what I mean by processing, compare the API response for that thread with what you see when you do "show original" in Gmail.) Alex On Sun, Apr 26, 2020 at 8:11 PM Abayomi Oloko wrote: > I think it’s premature to posit that Groups isn’t going t

Re: Form customization

will stop there. Let me know what you think. On Tuesday, October 8, 2019 at 12:53:42 AM UTC-7, Carlton Gibson wrote: > > Hi Alex > > Can you be more specific please? > > On Sunday, 6 October 2019 01:11:52 UTC+2, Alex Scott wrote: >> >> Would it be a terrible idea t

Form customization

from ":" to "". The current "solutions" seem hacky and non-DRY, usually requiring custom code for every form used in a site. Would it be a terrible idea to allow these to be set in settings or in a base form that gets inherited by everything else? Thanks, Alex --

Re: Proposal for a new template tag to disable invoking callable variables

The reason for this suggestion is over the years, while writing templates, I've had to spend a lot of time trying to figure out why I was getting an unexpected value (often an empty string) substituted for a template variable when that variable clearly had a different value. The reason that h

Proposal for a new template tag to disable invoking callable variables

hese tickets. If there is consensus, I'd be happy to take a shot at implementing it. Thanks, Alex https://github.com/aepshteyn -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscri

Re: revisiting the Python version support policy

The biggest issues with beginners I see at events like Django Girls or just regular Python meetups involve people needing to edit their .bash_profile or .bashrc files. Most people can figure out how to download the right version of Python for their platform, but then their shell to actually use

Re: Password reset token safety

(Which I didn't knew), this is totally useless. Thanks you for the clarification ! Alex -- 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 receiving email

Password reset token safety

Hello, I'd like to discuss about Django's password reset token functionality. I've been able, with a simple Python script, from having read-only access to my Django webserver to a full read-write by crafting a reset token. Isn't it one of the main goals of hashing passwords ? Protecting from

Re: Proposal: make Model __unicode__() default to self.name

Hi Collin, On Tuesday, December 12, 2017 at 3:48:38 PM UTC+1, Collin Anderson wrote: > Yes, having a good __str__ is important, and thats why i think defaulting > it to the pk is good, because it's better than nothing. Yes, you'll still > want to override __str__ with something better (that lik

Re: Proposal: make Model __unicode__() default to self.name

Sorry to resurrect this, but I commented on the bug tracker ( https://code.djangoproject.com/ticket/28839#comment:4 ) and was told to take the discussion here. I want to point out that __str__ is used for "GUI" purposes (such as dropdown texts in ModelForm/ModelAdmin) and putting a default __st

Re: Django 2.0 Python version support (Python 3.6+ only?)

One platform that only supports up to Python 3.4 ElasticBeanstalk with Amazon Linux. A few months ago they said they were going to release a new AMI, but that hasn't happened yet. I'm personally happy seeing support for 3.4 dropped and possibly just waiting a few months to upgrade to Django 2.0

Re: Methodology for increasing the number of PBKDF2 iterations

That's a correct assumption -- you won't be able to use pip without OpenSSL. Alex On Mon, Jan 9, 2017 at 7:39 PM, Tim Graham wrote: > About "we cannot just assume that all Python 3 installs have a "fast" > PBKDF2 implementation" -- I'd expect very

Re: Working towards a simpler GCBV implementation?

If most everyone agrees that Tom's Vanilla Views are superior than what's currently in core, maybe the path forward is to integrate into 2.0? On Wednesday, January 4, 2017 at 3:00:03 PM UTC-5, Adam Johnson wrote: > > Fair enough, there are other community resources for this. > > The PR adding a p

Re: Methodology for increasing the number of PBKDF2 iterations

9 40378 6 2.7.10 25213 7 3.4.3 23223 8 2.7.13 20657 9 2.7.5 17256 (That's an HTML table, no clue what happens if you use a plaintext email client) Alex On Wed, Jan 4, 2017 at 2:13 PM, Martin Koistinen wrote: > I think this is a pretty solid guess. Bear in mind this was a direct > i

Re: Methodology for increasing the number of PBKDF2 iterations

Python 2.7.12 will look the same as 3.5.x, they both have the optimized implementation. Only 2.7.X where X<8 will have the slow implementation. If someone was motivated, they could look at the PyPI bigquery and see what versions of 2.7 people are using to install django. Alex On Wed, Ja

Re: Page not found (404) passing two variables through URL django

This list is for the development of Django, not development with Django. Please use the django-users mailing list. That said, the problem is that you have an extra "<" after the "(" in the amount capture. Alex On Fri, Dec 16, 2016 at 6:38 AM, Ravin Kohli wrote: >

Re: LiveServerTestCase change in Django 1.11 means can't run functional tests against external server?

>>> >>> On Mon, 17 Oct 2016 at 23:16 Tim Graham wrote: >>> >>>> Good points -- given the existing subclassing needed to get >>>> LiverServerTestCase to support that use case, it might be reasonable not >>>> to >>>> worry about b

Re: LiveServerTestCase change in Django 1.11 means can't run functional tests against external server?

Thanks for including a link to the TDD tutorial! As far as I can tell, the author wants to use `--liveserver` to point his functional tests at an external server so he can run his tests through nginx after running the same tests in his normal test environment. Based on the shell prompts in htt

Re: disclosing security release dates on django-announce

We already have one :-), our bounty indicates several severity levels: https://hackerone.com/django Alex On Mon, Oct 10, 2016 at 3:40 PM, Tim Graham wrote: > Providing an indication of severity would be fine with me. Does anyone > know of other web frameworks that have descriptions of se

Re: Should the Django session-id be hashed?

this adds complexity for limited gain. Another relevant factor is that this is only applicable to the database sessions backend. Alex On Thu, Sep 22, 2016 at 7:33 AM, Florian Apolloner wrote: > > > On Thursday, September 22, 2016 at 1:26:19 PM UTC+2, Violet Gibson wrote: >&

Re: Sonar for the Django rpoject

If these are what qualifies as critical, I don't think this is a good use of our time. Alex On Wed, Aug 31, 2016 at 1:50 PM, Ivan Sevastoyanov < ivan.sevastoya...@gmail.com> wrote: > > <https://lh3.googleusercontent.com/-E2m40QeK7JE/V8cY0CHgj4I/BZs/ba0v7kckZ_w5X9d5F

Re: Add an optional dependency on python-fastpbkdf2

AFAIK upstream Python does use an optimized PBKDF2 (and OpenSSL 1.1.0 also has it). Alex On Sat, Aug 20, 2016 at 4:02 PM, Florian Apolloner wrote: > Ups, just realized that we use pbldf2 for more than just password hashing > -- if that where not the case the multi-library approach li

Re: Extend support for long surnames in Django Auth

t isn't. - I can imagine myself as a new user wasting cycles wondering what the reason behind the different field lengths is, so I imagine others might too. Cheers, Alex On Thursday, August 11, 2016 at 3:43:05 AM UTC+8, Florian Apolloner wrote: > > On Wednesday, August 10, 201

Re: bulk_create for multi table inheritance support

I'm interested in this as well. Two points to make. One, why not start with postgresql, which if I understand correct already supports getting ids in bulk_create. I think the "how to support getting ids in MySQL" is a separate issue. Second, I strongly agree with Shai, falling back should eithe

Re: Admin-Actions also in the object details view

s/card/csrf/ autocorrect grabbed that one from me. On Monday, July 11, 2016 at 7:55:17 AM UTC-4, Alex Riina wrote: > > Here's an implementation: > > https://github.com/crccheck/django-object-actions > > Combining with other admin plugins that change the template req

Re: Admin-Actions also in the object details view

Here's an implementation: https://github.com/crccheck/django-object-actions Combining with other admin plugins that change the template requires overriding the template to fit both changes in. The actions are GETs and have no card protection. -- You received this message because you are subsc

Adding dynamic TLD to session cookies to enable subdomain usage

Hi All, First post here, please redirect me where needed if is not appropriate. I wanted to suggest a feature. Our current plan is to use the same Django on subdomain.domain.com and domain.org, and a different Django with CMS on the TLD domain.com We want to enable cookie saving with the TL

Re: Add HTML5 required attribute on form widgets

What's the plan for formsets with extra? I could see the required only getting applied to the first min forms but I'm not sure there is an actual workable case there. It seems like it will get too messy with adding and deleting at the same time. If can_delete is false and extra is 0, it seems

Re: Lazy operations refactor regression with abstract models #25858

te subclasses belong to the inheriting class (unlike in concrete inheritance), we have app label placeholders for related names, etc. I see them more as a blueprint or template than a model. Options 1 and 2 both reinforce that distinction, option 3 muddies it a bit. Cheers, Alex On Thursd

Re: #25897 - managers defined on non-abstract base classes inherited by child classes

... some fields, still no manager > > Now, are you suggesting that Comment.objects must be defined explicitly? I > find > that odd. > > Shai. > > On Saturday 06 February 2016 18:07:22 Alex Poleha wrote: > > Thank you for the suggestion. Pull request is adjus

Re: #25897 - managers defined on non-abstract base classes inherited by child classes

warning for a couple releases? If > anyone is relying on the behavior, they just need to add the managers to > any subclasses, correct? > > On Wednesday, February 3, 2016 at 9:16:41 AM UTC-5, Alex Poleha wrote: >> >> Hi. >> >> According to documentation >

#25897 - managers defined on non-abstract base classes inherited by child classes

Hi. According to documentation managers defined on non-abstract base classes are not inherited by child classes. In fact they're inherited via python MRO. I made pull request

Call for comments: test (remote) connections using the checks framework

d with the core? Shall we make the connections test skip other checks, or maybe just make the connection-related ones the warnings? Here's the link to the ticket for your convenience: https://code.djangoproject.com/ticket/24475 <https://code.djangoproject.com/ticket/24475> Thank

Re: Methodology for increasing the number of PBKDF2 iterations

Sure, but such a problem has nothing to do with password upgrades, it can already be triggered by registration, or even just logging in without a password upgrade. Alex On Tue, Sep 22, 2015 at 2:43 PM, Tim Graham wrote: > Sorry, I explained poorly. We do upgrade passwords when the iterat

Re: Methodology for increasing the number of PBKDF2 iterations

ecked). The only way to reconcile this is for more users to get Python 2.7.8 and 3.4+, where there's a faster implementation of PBKDF2, or to entirely switch to alternate algorithms such as bcrypt. Alex On Sun, Sep 20, 2015 at 7:20 PM, Tim Graham wrote: > The latest guidance on increasing

Re: Add DoNotTrack (DNT) middleware?

I would say no: this does _so_ little, and it's completely implementable outside of Django. Moreover, adding the middleware doesn't change any behavior, you still have to do a bunch of work in your app to actually implement the not-tracking logic. Alex On Sat, Aug 29, 2015 at 1:17 PM,

Re: Password validation in Django revisited

Hi Erik, I've written such a patch, which also fixes an html escape bug and adds validation to the auth management commands. The pull request is here <https://github.com/django/django/pull/4969>. Sincerely, Alex On Friday, June 26, 2015 at 3:19:30 AM UTC-5, Erik Romijn wrote:

Re: Password validation in Django revisited

With the PR merged, password validation applies to the SetPasswordForm and the password changing forms, but not to the UserCreationForm or to the creation of superusers. Is there a reason not to apply validation to these as well? Alex Becker On Saturday, April 11, 2015 at 5:35:03 AM UTC-5

Re: Password validation in Django revisited

on by default. Thoughts? Alex Becker [1] https://github.com/alexbecker/password-strength Disclaimer: this is my first post to django-developers or any other oss mailing list for that matter. I apologize in advance for any breach of protocol. On Saturday, April 11, 2015 at 5:35:03 AM UTC-5, Erik R

Re: SSL support for Django-admin runserver‏

nfigure OpenSSL correctly" problem. Alex On Mon, May 11, 2015 at 6:30 PM, Florian Apolloner wrote: > > > On Monday, May 11, 2015 at 10:13:03 PM UTC+2, Steven Berry wrote: >> >> With all that said I'm in favor of what you suggest -- rely on gunicorn >> where

Re: Unneeded index created with unique=True and db_index=False in TextField

rn_ops operator classes only help with LIKE and regex queries; the unique constraint doesn't need them. I think we can change that to the following with no ill effects: if db_type is not None and field.db_index: Cheers, Alex [1] https://github.com/django/django/blob/28e89783254ac0899a26eee3245

Re: DKIM signing option for stmp.MailBackend?

I agree that DKIM is the responsibility of an MTA, not Django. Alex On Sat, Apr 4, 2015 at 6:53 AM, Bruno Ribeiro da Silva < bruno.dev...@gmail.com> wrote: > I do think DKIM is a task for the MTA too, so it doesn't make much sense > to have it in django's core. > On Apr

Overlap between Func and Transform

an they do more? Cheers, Alex [1] https://groups.google.com/forum/#!topic/django-developers/WYWrQkBJ2hs -- 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 receivin

Re: Refactor year, month, day lookups?

leared up - I'll start a new thread about it. Cheers, Alex On Wednesday, March 25, 2015 at 12:24:44 PM UTC+8, Josh Smeaton wrote: > > Hi, > > Firstly (and least importantly) opening a PR makes it a lot easier to > review code, especially when there are lots of commits. A [WIP] pu

Re: Adding an option on db_index to not create text/varchar_pattern_ops

e to use Expressions to create functional and multi-column indexes. So, that's my wishlist. All that said if you can come up with a patch that fixes your problem in a sane way, great! :) Cheers, Alex [1] https://github.com/django/django/blob/35b3158d52a5fe51d3b52aec1109a30a73

Re: Requesting eyeballs on a change to SQLite schema editor

Standalone PR now at https://github.com/django/django/pull/4122. Alex On Thursday, February 12, 2015 at 12:09:39 PM UTC+8, Alex Hill wrote: > > Hi all, doing a bit of yak shaving here. > > I'm currently refactoring Django's lazy operations [0], and ran into a bit >

Requesting eyeballs on a change to SQLite schema editor

uot; table This avoids ever having a model with a db_table set to the temporary table name. As well as fixing my problem, this seems a little more straightforward – there's a bit of awkward search-and-replace happening with the "__new" table name in the schema editor which we

Re: Abstract models and the app registry

ng anyway (e.g. abstract models with relations to "self"). Cheers, Alex On Thursday, February 12, 2015 at 2:49:34 AM UTC+8, Carl Meyer wrote: > > Hi Alex, > > On 02/11/2015 11:39 AM, Alexander Hill wrote: > > I'm looking for some background about abstract models,

Re: ANN: Django website redesign launched

pecific, *actionable* suggests or feedback, that's fine, but just shitting on other people's hard work is not. Alex On Tue Dec 16 2014 at 2:55:42 PM Schmitt, Christian < c.schm...@briefdomain.de> wrote: > Somehow I hate it. The website is the worst website I've seen since a

Re: Should annotations allow model field constraints?

t; We could instantiate with no args, but I'm not sure that's a better API. > It's nicer at least in the sense that you don't ignore constraints. The lack of constraints on the output field is implied by the API. I quite like that. Cheers, Alex -- You received this message

Re: Should annotations allow model field constraints?

27;price')), where the sum value violates the constraints, without any error. That provides sensible default behaviour which can be easily overridden if necessary. Cheers, Alex On Friday, December 5, 2014 10:04:21 AM UTC+8, Josh Smeaton wrote: > > Trac user jbg has found a re

Re: Websockets... again

And after you throw away the ORM, you have to throw away every other library that does blocking IO (anything in the stdlib, memcached, redis, requests, etc.). There are absolutely no affordances in WSGI for use with non-blocking libraries like asyncio or Twisted. Alex On Wed Oct 29 2014 at 1:45

Re: #23646 Enhancement: Updating multiple values in a single sql update using Django ORM

No, it doesn't. The atomicity semantics of update() are impossible to implement without it, this isn't the case for a multi-object UPDATE as far as I can tell. Alex On Sun, Oct 19, 2014 at 11:34 PM, Anshuman Aggarwal < anshuman.aggar...@gmail.com> wrote: > Thanks for the inp

Re: RFC: "UPSERT" in PostgreSQL

rs (Contributions to Django itself)" 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 django-developers@googlegroups.com. > Visit this group at http://groups.goo

Re: Two proposals for the Django Code of Conduct.

their behavior was disallowed. On reflection, I completely agree with their reasoning and am very glad we included it. Alex On Tue, Sep 9, 2014 at 11:43 AM, barbara.shaurette < barbara.shaure...@gmail.com> wrote: > As someone who has been the target of harassment at conferences (I'v

Re: Requiring GitHub login for actions on Trac

et-another-JIRA-instance. Alex On Wed, Aug 6, 2014 at 5:58 PM, Andre Terra wrote: > > On Wed, Aug 6, 2014 at 9:47 PM, Shai Berger wrote: > >> Today, it is possible to contribute to the Django project without a >> Github account. I would like this to remain the case. >&g

Re: Supporting and using EOL'd software (was Re: Time to drop support for Oracle < 11?)

y in non-technical and non-English speaking demographics. > > I think an important consideration is "can a user work around it in their application", e.g. if we remove something from common middleware, they can add it into their own middleware easily enough, if we change t

Re: Solving the select+1 problem.

at yielded post. Alex On Wed, Jun 11, 2014 at 6:37 AM, Jacob Kaplan-Moss wrote: > I'm not great at Haskell, either, but this looks to me to be very similar > to prefetch_related ( > https://docs.djangoproject.com/en/dev/ref/models/querysets/#prefetch-related > ). > > Jacob

Re: Terms for database replication

can replicate to another "slave"), the desire to cling to these misleading terms is simply perplexing. Alex On Thu, Jun 5, 2014 at 1:42 PM, Stan wrote: > Alex, > > With all due respect (I mean it), > The perception from the outside is that you didn't put the Django pr

Re: Terms for database replication

Hi everybody. The Django core developers have made our decision on the terminology we're going to use; I'd ask that you stop using django-developers to debate this further. Alex On Thu, Jun 5, 2014 at 10:43 AM, Unai Zalakain wrote: > Greetings! > > > I saw that som

Re: "Master/slave terminology"

to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/4da37237-adb4-49bd-b710-280dda186aea%40googlegroups.com<h

Re: "Master/slave terminology" (was: Master/slave trolling pull request accepted to django master branch)

ussion on the web visit > https://groups.google.com/d/msgid/django-developers/aaee8850-e135-44fd-8821-d0c3bd8fe423%40googlegroups.com<https://groups.google.com/d/msgid/django-developers/aaee8850-e135-44fd-8821-d0c3bd8fe423%40googlegroups.com?utm_medium=email&utm_source=footer> &g

Re: Displaying (some) M2M fields with through models specified

uot;greedy core developer" point of view, it would > be nice to see the *whole* problem solved, not just the subset you've > restricted yourself to. However, I'm sure we'll take whatever patch we can > get :-) > Thanks again for taking a look at this, Russ. Alex

Re: DEPs: Django Enhancement Proposals

The same way we do now? On Mon, Apr 14, 2014 at 3:34 PM, Andrew Farrell wrote: > Who is responsible then for deciding what the conclusion of the discussion > was? If there is no such person, how does the process handle the case when > people talk past each other and don't actually come to a conc

Re: DEPs: Django Enhancement Proposals

DEPs. Alex -BEGIN PGP SIGNATURE- Version: Mailvelope v0.8.0 Comment: Email security by Mailvelope - http://www.mailvelope.com wsFcBAEBCAAQBQJTTCE4CRASX1xn3+lAhAAAjBoP/3c3P30xlHh1Z3BDvrS5 LHuzyQR/Lp3rws+83Cnh0Xi154xcWkd1np5PvbXXya747NSLEIayryDHiYlw hhdeGFA7

Re: Support byte range requests in django.views.static.serve

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I'd be +1 on doing this -- I know we've always said that Django's static serve isn't for production use, but as video and audio are increasingly common on the web, Django should support them seemlessly. Alex PS: I'm of cou

Re: Using namedtuple instead of pure tuples

chmark, even as idiotically simple as: "a = 1; (1, 2, a)" would more accurately mirror the real world. Alex On Sun, Feb 23, 2014 at 7:57 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > > Hi Stratos, > > Thanks for providing those benchmarks -- that's rea

Re: Accelerated deprecation of fix_ampersands and clean_html

For what it's worth, source graph is unable to find any callers of clean_html in OSS code (maybe github only?) either: https://sourcegraph.com/github.com/django/django/symbols/python/django/utils/html/clean_html Alex On Sun, Feb 23, 2014 at 2:15 PM, Erik Romijn wrote: > Dear all, >

Re: RawQuerySet as subquery when used with an __in filter

Hi all, In implementing this I ran into a bug in the way SQLite returns column information: https://code.djangoproject.com/ticket/21603 It affects raw queries in general, but this feature in particular due to the way the code generate nested SQL queries. Cheers, Alex On Friday, December 13

Re: Django ORM support for NoSql databases

swer. > Fair enough on not issuing policy proclimations :-) But I think it would be helpful to get some feedback on the question: should django try to 'open up' the ORM to make it easier to write backends for NoSQL DBs? Add more hooks, sharper divisions between layers, etc.

Re: RawQuerySet as subquery when used with an __in filter

t.com/ticket/21604 Would love to get some feedback. Cheers, Alex On Friday, September 7, 2012 5:34:16 PM UTC+8, Anssi Kääriäinen wrote: > > On 6 syys, 11:22, Alex Hill wrote: > > Hi Anssi, > > > > Thanks for your feedback! Responses inline. > > > > 1.

Re: Self-referenced template recursion handling

Hi all, If anybody's interested in some background reading, there is an implementation of this in Mezzanine, using an "overextends" tag. https://github.com/stephenmcd/mezzanine/blob/1.4.16/mezzanine/template/loader_tags.py Cheers, Alex On Sunday, December 8, 2013 11:08:12 PM UT

Re: mod_python support

I'm -1 on this. If it's, in fact, just a normal WSGI container, we should add docs for it if it has any uptake, as we would for any other WSGI container, and I don't believe it has any uptake. Alex On Mon, Nov 25, 2013 at 10:36 AM, Kamil Gałuszka wrote: > Hi ! > > I wa

Django mysql over ssl (2026, 'SSL connection error: Failed to set ciphers to use')

Hy, Summary: I'm getting this error "(2026, 'SSL connection error: Failed to set ciphers to use')", on the django error page and I don't know what i happening!!! I'm using apache / wsgi and my aplication it's on a virtualenv. The main problem is that I can't connect to a remote mysql ove

Re: #18659 -- Deprecating request.REQUEST

Another +1 for removing it, it makes it way too easy to do something unfortunate, and it's behavior is only really intuitive if you come from PHP, otherwise my first question is, "Where does it look first!?!" every time I see it used. Alex On Wed, Oct 16, 2013 at 8:14 AM, Sha

Re: Specifying the field index types

-dbindexer that allows you to add more indexes, like for case-insensitive queries or contains queries. App Engine can't do these things out of the box. Currently, you use another special file for these indexes, but it would be nice to have this all configured on the field. --Alex > &

Re: Specifying the field index types

This is something that I'd also be interested in. For the Google App Engine backend, you have the ability to create indexes that require more configuration than just on/off. But I don't think a single additional field would do the trick for my case. Another option would be to open up the Meta c

Re: A policy on calling super()

_ won't be invoked. Alex On Sun, Sep 29, 2013 at 10:00 AM, Tom Christie wrote: > Calling super in base classes (ie anything that inherits from 'object') > just seems unnecessary and obscure to me. It's not a pattern I use or have > seen, and after playing around a bit I c

Performance Docs

and compatibility issues are common." is pure FUD, and unsubstantiated. I'd strongly prefer we remove this from our docs, and if anything we should be encouraging the opposite, people with performance issues should be encouraged to consider things like PyPy, not hide from them. Alex

Re: Thinking about NoSQL support

On Sunday, September 8, 2013 2:20:56 AM UTC-4, Benjamin Zuill-Smith wrote: > The django-nonrel project is alive and looking for contributors. >> > > Hi Alex, thanks for responding. I guess I was concerned by the lack of > commits lately, but looks like it's still alive a

Re: Thinking about NoSQL support

' db code should you need it. This is similar in concept to raw sql support in django... sometimes you just to need to write the query by hand. As for the arguments that document/nosql/whatever db != relational db, its close enough to not matter in a lot of very useful scenarios. --Alex --

Re: Odd behavior on proxy models should be on documentation

present the same data as their parent class. Everything else follows naturally. Best, Alex Ogier On Aug 18, 2013 12:32 AM, "Jorge C. Leitão" wrote: > Hi there. > > I was working with proxies models and I found an odd behavior on a > QuerySet, and I ask here whether it s

Re: Security Advisory: BREACH and Django

That's too hard to enforce. It would mean that you can't show user content on any public page, or any page that you want to be accessible from outside links. For example, you couldn't show blog comments to unregistered users. It would be too disruptive. Modifying the format of the secret token is a

Re: Hybrid Property request

veral with the composite fields GSOC for the virtual field, when we generalize fields to N>=1, I'm hoping that makes generlaizing them to N=0 easier. Alex On Wed, Jul 17, 2013 at 11:12 AM, Jacob Kaplan-Moss wrote: > On Tue, Jul 16, 2013 at 8:04 PM, Russell Keith-Magee < > rus

Re: Supported Python versions for Django 1.7

Debian Wheezy and Ubuntu 12.04 LTS are both on Python 3.2. On Mon, Jul 1, 2013 at 5:44 PM, VernonCole wrote: > > Dropping support of 3.2 would potentially aid projects which have not yet > converted to Python 3, since Python 3.3 supports u"Unicode Literals" but > 3.2 does not. Skipping over the

Re: Django+GoogleAppengine(datastore)

On Thursday, June 6, 2013 2:53:17 AM UTC-4, Rishi Kumar wrote: > > so can somebody help me on this.i need the details of django setup with > full funtionality of datastore,as we have with webapp2 framework. > Ask on the django-nonrel list. We have a django backend which works with the app engine

Re: Specifying lists/tuples in models - wtf?

No worries, that's always been one of the most awkward gotchas in python. It's made doubly so by the fact that iterating over a string gives more strings. On Jun 5, 2013 4:29 PM, "Cal Leeming [Simplicity Media Ltd]" < cal.leem...@simplicitymedialtd.co.uk> wrote: > Hi Noah, > > Sorry yes I remember

Re: Migrations, commands and syncdb

I'm broadly +1 on deprecating syncbd, it's possibly the most inaccurately named thing in all of Django (hint: it doesn't sync anything). Alex On Thu, May 30, 2013 at 11:03 AM, Andrew Godwin wrote: > Hi everyone, > > I'm starting to plan out the commands fo

Re: Cursor closing or reuse: am I missing something?

Anssi has removed those it should be more straightforward to close cursors there. Alex On Fri, May 17, 2013 at 5:23 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hi Vernon, > > On 17 mai 2013, at 13:26, VernonCole wrote: > > > After much debuggi

Re: first() and last(), earliest() and latest()

Querysets definitely support indexing. Alex On Thu, May 16, 2013 at 2:51 PM, Alex Ogier wrote: > QuerySets don't support indexing. I'm not entirely sure why, but I > think the reason is to encourage more efficient database usage, since > naive usage of indexing would le

Re: first() and last(), earliest() and latest()

>> >> That's what I thought- But why not just qs[0]? >> >> Doesn't qs[:1] and qs[0] both cause a LIMIT 1 on the query? It seems that >> the [:1] is unnecessary. I would expect both to raise IndexError. >> >> >> >> On Wed, May 15, 2013

Re: first() and last(), earliest() and latest()

Significantly better. The latter method loads every single model in the queryset into Python, potentially the whole database! On May 15, 2013 9:24 PM, "Lee Trout" wrote: > Is qs[:1][0] better form than list(qs)[0]? > > > On Wed, May 15, 2013 at 7:48 AM, Selwin Ong wrote: > >> I've updated the fi

Re: reconsider re-opening ticket 901

On Tue, May 14, 2013 at 7:38 AM, Shai Berger wrote: > On Tuesday 14 May 2013, Alex Ogier wrote: > > > > It's a totally new behavior that has > > plenty of corner cases such as foreign keys, and especially > OneToOneFields. > > > Another one is initializers:

Re: reconsider re-opening ticket 901

you could iterate over Meta.fields calling "setattr(old_a, field_name, getattr(new_a, field_name))" for each one, but that has the problem that field setters may expect to do some massaging of the data on the way in which can cause data corruption. Basically this is a Hard Problem(tm) w

Re: reconsider re-opening ticket 901

following should be equivalent to the previous example: bb = B() bb.save() aa = A(b=bb) aa.save() assert aa.b is bb assert bb.a is aa # back-reference is cached aaa = A.objects.get(id=aa.id) aaa.b = None aaa.save() aa.refresh() # back-reference is cleared assert aa.b is None assert bb.a is None

  1   2   3   4   5   6   7   8   9   >