On Sat, Feb 7, 2015 at 12:05 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> As the test suite is growing, it’s getting slower. I’ve tried to make it
> faster by running tests in parallel.
>
> The current state of my experiment is here:
> https://github.com/django/dj
Hi Marten,
I can understand the motivation, and the approach you've taken makes sense.
It definitely strikes me as a much better alternative to tickets like
#24288 than a setting.
https://code.djangoproject.com/ticket/24288
The DRY issue isn't a huge problem for me - it's certainly ungainly to n
Hi Andriy,
If we're going down this path, I can't think of any reason we wouldn't
target ever available aggregate. It doesn't need to be all in one patch/PR
- in fact, I'd suggest that unless the implementations are particularly
intertwined, one patch per aggregate (or aggregate group - e.g., all
On Fri, Feb 20, 2015 at 9:29 AM, Diana Probst
wrote:
> The last time I logged into GitHub was at least one computer ago. And
> that computer blew up a bit. I'll try to get on, but this is contingent on
> many factors, and I don't have control over them all. What I will do is
> read the docs on
nf werkzeug/+webOb in django will let
>>> eliminate some of django's built in way of handling request/response
>>> processing, urlresolving, url routing, view processing some error handling
>>> etc.
>>>
>>> Sould I go for a detail one with what I hav
? where will
> I get Ideas about what are considered as best practise in django 1.8/+? or
> other suggestions?
>
> Regards
>
> On Sun, Feb 22, 2015 at 6:36 AM, Russell Keith-Magee <
> russ...@keith-magee.com> wrote:
>
>>
>> To my mind, the goal of this projec
Hi Aron,
Short version - if you're eager to look into this, we're eager to have
composite keys in Django - it's probably one of the last features I can
think of that was discussed for the 1.0 release but we bumped so that "we
can add it for 1.1".
(ahem. :-)
Yes, there have been a lot of changes
On Tue, Feb 24, 2015 at 11:59 PM, Riccardo Magliocchetti <
riccardo.magliocche...@gmail.com> wrote:
> Il 24/02/2015 16:18, Florian Apolloner ha scritto:
>
>> On Tuesday, February 24, 2015 at 3:23:23 PM UTC+1, riccardo.magliocchetti
>> wrote:
>>
>> I'm no UI/UX expert but modals are more or les
On Wed, Feb 25, 2015 at 10:39 AM, Loïc Bistuer
wrote:
> >
> > On Feb 25, 2015, at 09:07, Russell Keith-Magee
> wrote:
> >
> > I have an operating system with a graphical user interface. The
> developers of that operating system spent an immense amount of time
Hi Gavin,
I've lost track of how many times I've written that exact code when setting
up a new box - I just didn't wrap it up as a management command. There's a
similar testing cycle with new cache settings.
My only concern would be the one that Tim expressed - that it's ultimately
a one line she
Hi Abhishek,
On Sun, Mar 1, 2015 at 1:16 PM, Abhishek Kumar wrote:
> Hi,
>
> I am Abhishek and am interested in the project titled "SQLAlchemy / NoSQL
> integration". I am good at data-structures and algorithms and have worked
> with C,C++, PHP, Python,C#, Javascript and Mysql. I have an interns
Hi Yichun,
On Mon, Mar 9, 2015 at 4:13 PM, Yichun Duan wrote:
> Hi,
>
> I'm Yichun and I'm interested in the Project ' Improving the less popular
> database backends' in GSOC 2015. I major in computer science in Peking
> University. I've worked with C++, Java, Python and I've written several
> w
Hi Benjamin,
A few more details to whet your appetite (because this is a thing I've been
*thinking* about, but don't have anything to show)
The biggest sticking point at the moment is getting Python on the client
side. I'm aware of many attempts:
* Brython (http://www.brython.info) is an in-bro
Hi Mitchel,
Thanks for submitting a proposal (and for starting the process earlier than
2 days before the deadline). You get extra credit for being ambitious and
proposing something that isn't on the suggested projects list :-)
I have three concerns about this project:
Firstly, what's the curren
Hi Yichun Duan,
Thanks for submitting a proposal - what you've submitted is a good start,
but it needs some more detail and clarification.
4.1: You say you're going to save the database-specific tests "to another
place" - Can you give specifics, or at least an idea of you current
thinking? How wi
On Wed, Mar 18, 2015 at 5:38 AM, Curtis Maloney
wrote:
> I found when taking the CBGV session in MelbDjango School, it was best to
> approach teaching CBV as an exercise in Interfaces.
>
> Once the students were familiar with writing basic views, and the patterns
> therein, much of CBGV became "o
that there is 12 weeks
worth of work here - the problem is that you need to convince us that *you*
know where those 12 weeks of work are.
Yours
Russ Magee %-)
On Sun, Mar 22, 2015 at 8:32 PM, Yichun Duan wrote:
> Thanks. Updated. :)
>
> 在 2015年3月18日星期三 UTC+8上午6:39:46，Russell Keith-M
On Sun, Mar 22, 2015 at 4:12 PM, Mesut Gülecen
wrote:
> Hi, my name is Mesut Gülecen, currently in second year of engineering
> at Canakkale Onsekiz Mart University in Turkey.
> I want to contribute to the development of Django. I have working upon
> Django already and I want to learning somet
Hi Mesut,
It wasn't clear that you were asking a question.
Django's GSoC wiki page contains details of what you need to do in order to
be a GSoC student for the Django project; the next step from your
perspective is for you to do some research on the projects that interest
you and write a proposa
Hi Zafack Billy,
Welcome! If you're interested in being a GSoC student with Django, you
should read our wiki page on the program.
https://code.djangoproject.com/wiki/SummerOfCode2015
>From there, you need to pick a project, and prepare a proposal describing
what you expect to achieve over the 12
I agree with Tim's assessment - this is not a compelling proposal at the
moment.
There is value in converting *some* of the function based views to CBVs,
but unilaterally converting all of them doesn't seem especially worthwhile.
The key thing is to identify what features need to be factored out.
Hi Varun,
I've just taken a look at this proposal; I've got some concerns.
* You say you can get test coverage from 81% to 90% - that's an admirable
goal, but is there any reason to believe that it is achievable? In many
cases, the coverage is low because a feature/branch is so difficult to test
Hi Alex,
On Thu, Mar 26, 2015 at 7:03 AM, Alexander Patel <
alexanderpa...@college.harvard.edu> wrote:
> Hello, all,
> My name is Alex Patel, and I am an undegraduate at Harvard College in the
> United States studying mathematics and philosophy. I intend to submit a
> proposal to work on Django's
Hi Paulo,
On Sat, Mar 28, 2015 at 8:12 AM, Paulo Maciel
wrote:
> I started working with formset and found half cast, for example, when
> configuring a formset with min_num = 1, django requires that the first form
> of the formset (form-0) is completed, I see this as a bug, it should check
> for
On Mon, Mar 30, 2015 at 1:36 AM, Pkl wrote:
> Hello all,
>
> I've noticed that all sql* commands that were in django core management
> have disappeared from the latest sources.
>
> However, even though Django now has builtin south-style migrations now,
> these *sql** commands (especially sql-all)
On Sat, Apr 4, 2015 at 12:24 AM, Loek van Gent wrote:
> Hi all,
>
> Is anyone using DKIM signing for densing emails? Does it make sense to you
> to have a feature like that in Django core or is this typically something
> that should be in it's own app?
> We use it to sign our emails so the don't
Hi Anoop,
I agree with Tim and Markus' comments - you're proposing to implement
a specific behavior where there is no "clearly right" answer. This
strikes me as something that is entirely site-dependent logic. You
don't even need a custom user model - a template tag (or even a
filter) could do thi
I'm completely on-board with the idea of switching to a "real" web server
rather than continuously improving our own.
However, there might be better options than gunicorn. Graham Dumpleton has
released mod_wsgi-express:
http://blog.dscpl.com.au/2015/04/introducing-modwsgi-express.html
which is a
On Thu, Jun 4, 2015 at 4:19 PM, Tim Graham wrote:
> I think we should keep Trac focused on tracking bugs. The dsf-members
> mailing list seems like a natural place to raise these ideas, although
> that's a more limited audience, so I'd feel free to raise them here unless
> someone else can sugges
On Mon, Jun 29, 2015 at 7:32 AM, Josh Smeaton
wrote:
> I'm not quite up to date on XML in databases (I've never had to use XML in
> a database), but don't the majority of core backends support XML in some
> way? If so, I'd probably like to see an attempt to build out XML support
> such that all/m
day, June 28, 2015 at 7:51:22 PM UTC-4, Russell Keith-Magee wrote:
>
>>
>> On Mon, Jun 29, 2015 at 7:32 AM, Josh Smeaton
>> wrote:
>>
>>> I'm not quite up to date on XML in databases (I've never had to use XML
>>> in a database), but don'
Hi James,
I'm inclined to agree - the fact that Django added a new field type in 1.8,
but can't serialize that type should be considered a bug, not a new feature.
If there's no objection on this thread, then the ticket should be
re-opened, and a pull request for the backport submitted.
Yours,
Ru
On Mon, Jul 13, 2015 at 11:00 PM, Donald Stufft wrote:
> I’m fine with this, but just be warned that it does mean anything
> that ships a Django app will need a zip_unsafe=True or else they
> no longer support being installed with easy_install.
... and I'm sure both the people who still use eas
On Thu, Jul 23, 2015 at 12:40 AM, Tim Graham wrote:
> Lately we've had some packaging problems due to mistakes in MANIFEST.in,
> mostly due to missing files in the source distribution because we forgot to
> update MANIFEST.in for new or moved files. Currently it looks like this:
>
> include READM
Hi Mudassar,
If you're looking for help on how to use or deploy Django, you should post
to the django-users mailing list. This list is for discussing the
development of Django itself.
Yours,
Russ Magee %-)
On Tue, Aug 4, 2015 at 7:36 AM, Mudassar Hashmi <
mudassarziahash...@hotmail.com> wrote:
On Fri, Aug 7, 2015 at 3:06 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> > On 7 août 2015, at 05:43, Curtis Maloney
> wrote:
> >
> > I'd probably go with updating the documentation to say they're legacy
> > tags, you're better off using {% if %} now, and warn they may be
>
On Fri, Aug 21, 2015 at 7:35 AM, Tim Graham wrote:
> In my experience the "easy pickings" flag is ill-defined and insufficient
> for describing the difficulty of a ticket. I don't want to get stuck in
> categorizing tickets just for the sake of it, but I think a drop down with
> options like the
On Sat, Aug 22, 2015 at 8:28 PM, Tim Graham wrote:
> I agree it would be great to get some help running the Django tests on
> Windows. I run them in a local virtual machine every so often, but I would
> love to be able to delegate fixing Windows issues. Meet, can your team
> provide ongoing help
Hi Meet,
The Fellowship committee has just approved this, so go ahead and plan
whatever you need to plan.
Yours,
Russ Magee %-)
On Sat, Aug 29, 2015 at 6:21 AM, Meet Bhagdev wrote:
> Thanks Russ!
>
> On Tuesday, August 25, 2015 at 6:34:54 PM UTC-7, Russell Keith-Magee wrote:
>&g
Hi Tim, Meet
I know this is very late to be mentioning, but one idea that worth
raising: DjangoCon US is next week (in Austin). Thursday and Friday
are coding sprints, where there will be many people (including a good
chunk of the core team) looking for projects to hack on.
Microsoft is already a
On Wed, Sep 2, 2015 at 10:29 PM, Tim Graham wrote:
> Russ tried to complete the "EmailUser" solution for 1.7, but if I remember
> correctly, there was some issue with testing that couldn't be easily
> resolved.
>
> https://github.com/django/django/compare/master...freakboy3742:emailauth
The issue
Hi Asif,
It depends entirely what you mean by "support".
Django is just Python, so there's absolutely no reason you can't write
a Django site that uses Django for the URLs, views and forms, but
SQLAlchemy for the data access.
Out of the box, you won't be able to use ModelForms or the Admin.
Howe
On Wed, Sep 23, 2015 at 7:06 AM, Josh Smeaton wrote:
>> Could we have permanent backward-compatible (no deprecation timeline)
>> shims? I'm -0 if not because it's yet-another thing that everyone needs to
>> change when upgrading.
>>
> +1
That would be my preferred approach, too.
Yours,
Russ Mage
On Wed, Sep 23, 2015 at 12:54 AM, Tim Graham wrote:
> The second patch has been committed, and the first one is still under
> review.
>
> Florian says "with all that forth and back [on the pull request] I am not
> sure if it is not better to defer it to 1.10, i.e. I completely missed the
> base64
Hi Yash,
The Google Summer of Code 2016 hasn’t even been announced yet. Django
hasn’t applied to be a mentor organization, and it’s not yet certain that
we’ll even apply.
However, assuming that we do - the best thing you can do to improve your
chances to be accepted as a Django GSoC student is to
On Sat, Oct 24, 2015 at 5:42 AM, Marc Tamlyn wrote:
> I disagree with this system check and I would like to see it reverted
> before 1.9 final.
>
I agree - I’d argue that this check is demonstrably *incorrect*.
> I admit that my opinions here are skewed by the fact that I think model
> level v
Agreed. This didn’t really affect 1.4 because 2.7 was in a very stable
place, and we didn’t support Python 3. Now that we’re Py3 focussed, and
Python has a similar backwards compatibility policy to Django (i.e., Python
3.7 isn’t going to break all Python 3.6 code in subtle ways), it makes
sense tha
+1. Sounds like a great idea to me.
Russ %-)
On Tue, Oct 27, 2015 at 1:22 AM, Tim Graham wrote:
> On Trac [1], Alex says, "Django did a tremendous service to its users by
> making strong password hashing be the default. The world is pushing
> forward, and now 2fa is the next standard that many
Hi Tim,
On Wed, Oct 28, 2015 at 12:50 AM, Tim Graham wrote:
> In 2014 I started to research if we could offer a Google Summer of Code
> project aimed at improving Django's process for collecting and organizing
> CLAs. I didn't complete that proposal when I found some existing solutions,
> in par
Hi Asif,
On Wed, Nov 4, 2015 at 12:17 AM, Asif Saifuddin wrote:
> I would like to create an experiemental repo on my github for
> experiementing the sqla support to django orm, hence some useful resource
> indicator would be great. sqla have core engine and orm on top of it, so
> the idea way to
HI Alex,
On Wed, Dec 9, 2015 at 9:57 PM, Alexandru Damian wrote:
> Hi,
>
> I've compiled the django.template.{base,context,context_processor} modules
> with cython in order to speed up template rendering.
>
> I've come to the conclusion that this is needed after profiling long page
> loads that
On Thu, Dec 10, 2015 at 7:52 PM, Alexandru Damian wrote:
> Hi Russ,
>
> Thanks for coming back to me so quickly.
>
> On Thursday, December 10, 2015 at 12:30:03 AM UTC, Russell Keith-Magee
> wrote:
>>
>> HI Alex,
>>
>> On Wed, Dec 9, 2015 at 9:57
On Sun, Dec 27, 2015 at 11:00 PM, Wim Feijen wrote:
> By default, when you create a formset from a model, the formset will use a
> queryset that includes all objects in the model (e.g.,
> Author.objects.all()).
>
> In most use cases, people will want to use a specific subset of data and
> will co
On Mon, Aug 23, 2010 at 1:56 AM, Timothy Makobu
wrote:
> Hi all,
>
> Django is truly outstanding software. Thank you all for your great
> work.
On behalf of the core team, and the huge community of developers that
have contributed to Django -- you're welcome!
If you want to show your appreciatio
On Mon, Aug 23, 2010 at 5:21 AM, Waldemar Kornewald
wrote:
> Hey Flavio,
>
> On Sun, Aug 22, 2010 at 12:40 PM, FlaPer87 wrote:
>> Hi Alex,
>>
>> I agree about leaving the backend outside django too (IMHO, all
>> backends should live outside django). Is there any link that points to
>> the apps yo
On Tue, Aug 24, 2010 at 3:15 PM, Rodney Topor wrote:
> [Cross-posted from Django Users]
The answer you've got on django-users is dead on the money. It says
right at the top of the overview "This is not a tutorial or
reference". It's meant to be a brief taster for what Django has to
offer, and if
On Wed, Aug 25, 2010 at 5:11 AM, Michael Manfre wrote:
> I don't think namespacing is a valid objection against query hints. By
> design, query hints are specific to a database version and if a
> generic django app were to include them, then the author is doing
> something wrong or setting the exp
On Thu, Aug 26, 2010 at 12:09 AM, Michael Manfre wrote:
>
> On Aug 24, 9:30 pm, Russell Keith-Magee
> wrote:
>> I don't follow your logic here.
>
> I guess I'm more of the mindset of query hints having as much to do
> with the stored data as the schema
On Thu, Aug 26, 2010 at 12:55 AM, mucisland wrote:
> I posted this also in Django users but got no response - maybe the
> question is too stupid or it was the wrong group...
>
> Here's the deal:
>
> I have various views which break on the additional csrfmiddlewaretoken
> in request.POST when using
On Fri, Aug 27, 2010 at 8:06 AM, Yo-Yo Ma wrote:
> I'm sure this will be met with criticism, but there is a reason why
> just about all template languages allow the setting of variables.
Yes. It's because most template languages are trying to be a Turing
complete programming language. Django's te
On Fri, Aug 27, 2010 at 2:28 AM, Joshua Russo wrote:
> I've developed and I'm currently using a mod to allow auto-increment id
> fields to be editable. I'm curious if I should produce a ticket to allow
> this, or will it cause a problem on some DBMS I'm not aware of.
The problem will come with da
On Fri, Aug 27, 2010 at 12:25 AM, Yo-Yo Ma wrote:
> I'm speaking about something like http://code.google.com/p/django-nav/
Whenever you're proposing to add something to the core, the big
question you have to ask is "What do we gain by adding it to core?".
The guideline for adding something to dj
On Fri, Aug 27, 2010 at 2:12 AM, Carl Karsten wrote:
> I would like to discus my patch to add support of nullable fields to
> get_next_by_FOO
>
> http://code.djangoproject.com/ticket/13611
>
>> You say "we" discussed this on IRC, but you don't say who "we" are.
>
> I forget who was involved in the
On Fri, Aug 27, 2010 at 9:12 AM, Russell Keith-Magee
wrote:
> On Fri, Aug 27, 2010 at 2:12 AM, Carl Karsten wrote:
>> I would like to discus my patch to add support of nullable fields to
>> get_next_by_FOO
>>
>> http://code.djangoproject.com/ticket/13611
>>
>&
On Fri, Aug 27, 2010 at 9:22 AM, Yo-Yo Ma wrote:
> I see what you're saying Russell. I myself am reluctant to use the
> template tag I created in some ways. Although I cannot seem to find a
> DRY way of doing what I'm doing
Factor the logic out of your template so that your template is just
descr
On Fri, Aug 27, 2010 at 9:27 AM, Brian O'Connor wrote:
> I think this got brought up in the forums a month or so ago, but I'd like to
> see a 'shortcut' for setting variables much like we have a shortcut for
> registering inclusion templatetags. Having to write a full fledged
> templatetag to set
On Sat, Aug 28, 2010 at 12:32 PM, Yo-Yo Ma wrote:
> I think the thing that would be helpful to most django users is bit
> really a navigation helper per se. I think what I need could be solved
> with a more generic tool.
I don't doubt that for a second. What I'm challenging is why this
needs to b
Hi Nowell,
First off -- apologies for taking so long to get back to you.
On Sun, Jul 11, 2010 at 10:54 PM, Nowell Strite wrote:
> Hey Russ,
>
> In the Artist example there are actually two many to many fields
> pointing to songs (songs, and best_songs) so currently when you call
> artist.songs o
On Wed, Sep 1, 2010 at 1:24 AM, stefanw wrote:
> Hello,
>
> I guess the most interesting point in this discussion is:
>
>> After a while that I spent time to develop new tags and filters
>> especially for
>> new projects, I began to think a way to implement a template engine
>> that
>> would let m
On Wed, Sep 1, 2010 at 6:41 PM, Gregor Müllegger wrote:
> I ran into the same problem as George before. And it always hits when I try to
> modify my admin pages in undocumented ways. So I would also be for some
> changes in this area.
>
> But I think we cannot simply remove it. Most constraints ma
On Wed, Sep 1, 2010 at 2:03 PM, George Karpenkov
wrote:
> Steps to reproduce:
> 1) Specify a custom admin class (say A) which mentions a custom inline
> with a custom template, say "a.html"
> 2) Write anything to "a.html" which will raise TemplateSyntaxError -
> ie "{% extends "a.html" %}
> 3) Obs
On Wed, Sep 1, 2010 at 10:29 PM, Ramiro Morales wrote:
> Hi all,
>
> SQLite 3.6.19 from Oct 14 2009 added support for enforcing these
> constraints. The relevant documentation is available at
> http://www.sqlite.org/foreignkeys.html
>
> I've opened ticket [1]14204 with a initial patch.
>
> In shor
On Thu, Sep 2, 2010 at 1:42 PM, burc...@gmail.com wrote:
> Hi George,
>
> I believe this is a bug since any other errors in admin (not related
> to inlines) don't pass silently.
>
> Silencing errors should always be documented, especially if error is
> silenced when DEBUG is turned on.
>
> So it's
On Thu, Sep 2, 2010 at 2:30 PM, burc...@gmail.com wrote:
> Hi Russell,
>
> I'd define
>> {% for templ in template_list %}
>> {% include templ %}
>> {% endfor %}
> as a special case, for which special command or pattern should exist.
>
> Should it be
> {% for templ in template_list %}
> {% tr
On Thu, Sep 2, 2010 at 5:04 PM, burc...@gmail.com wrote:
> Russell,
>
> Sorry, we didn't understand each other,
>
> You're talking about additional problems for templates with variable names.
>
> However main point that George made was that he wanted template
> rendering to break when including te
On Thu, Sep 2, 2010 at 7:08 PM, Simon Meers wrote:
> Users regularly get confused when you present them with a raw_id popup
> window which shows action checkboxes beside the list of items they are
> selecting from -- they try to click the checkboxes, and wonder why the
> window isn't closing. IMHO
On Thu, Sep 2, 2010 at 7:40 PM, George Karpenkov
wrote:
> Dear Russ,
>
> I still don't quite get why "runtime template errors are
> unacceptable". My understanding is that if user has DEBUG=True, and
> TEMPLATE_DEBUG=True, then clearly (at least to me) the user does want
> to see all of the errors
On Thu, Sep 2, 2010 at 7:43 PM, George Karpenkov
wrote:
> Would you accept the patch that would simply allow functions as well
> as iterables?
Possibly, yes. Specifically, I'd be happy with any proposal that put
ModelAdmin into alignment with other parts of Django, like the
Syndication framework,
On Thu, Sep 2, 2010 at 8:47 PM, burc...@gmail.com wrote:
> On Thu, Sep 2, 2010 at 6:27 PM, Russell Keith-Magee
> wrote:
>> On Thu, Sep 2, 2010 at 5:04 PM, burc...@gmail.com wrote:
>>> Russell,
>>>
>>> Sorry, we didn't understand each other,
>>
On Thu, Sep 2, 2010 at 9:34 PM, stefanoC wrote:
> bumping an already old question, is django going to run on python
> 3.x ?
>
> I found a few discussions talking about this, eg. and
> http://groups.google.com/group/django-developers/browse_thread/thread/f8c747a26aa5d8ed/0749bfa67b47c802
> and
>
On Thu, Sep 2, 2010 at 4:25 PM, Waldemar Kornewald wrote:
> How often should I ping, so my patch won't be forgotten? :)
Look - I don't want to appear rude or disparaging, but it will happen
when it happens.
Your patch is on a long list of things needing review -- including
hundreds currently sit
On Sun, Sep 5, 2010 at 5:05 PM, VernonCole wrote:
> "Once we're at a Django 2.6 minimum supported version, using 2to3 to
> maintain
> parallel implementations becomes a lot easier."
>
> As much as I admire Russ, and I do, I don't think that the above
> statement is correct.
My apologies -- in the
On Tue, Sep 7, 2010 at 4:08 AM, Patryk Zawadzki wrote:
> Hi,
>
> Since CSRF is already being reafactored up-side down in the trunk, I
> thought it might be a good idea to propose a slight modification.
Erm... it is? That's news to me.
Django 1.2 introduced a bunch of very big changes, but those
On Thu, Sep 9, 2010 at 11:26 AM, Simon Litchfield wrote:
> Hi all
>
> Default behaviour of sending an email on 500 error is great.
>
> Problem is on high traffic sites, and you might just be making a quick
> update- literally within seconds you can bring your mail server down-
> crash your mail cl
On Thu, Sep 9, 2010 at 10:24 PM, Javier Guerra Giraldez
wrote:
> from Eric Florenzano's slide 41:
>
> In models.py:
>
> class Favorite(models.Model):
> item = LazyForeignKey(‘fave’)
> user = ForeignKey(User)
> date = DateTimeField(default=utcnow)
>
>
> In settings.py:
>
> LAZY_F
On Fri, Sep 10, 2010 at 6:42 AM, Javier Guerra Giraldez
wrote:
> On Thu, Sep 9, 2010 at 4:02 PM, Alex Gaynor wrote:
>> So how does this work? Where do args come from?
>
> args (for lack of a better name) is the same dictionary passed as the
> second part of the tuple in the INSTALLED_APPS list.
On Fri, Sep 10, 2010 at 6:37 AM, Javier Guerra Giraldez
wrote:
> On Thu, Sep 9, 2010 at 3:59 PM, Russell Keith-Magee
> wrote:
>
>> What you're proposing here is two things: a LazyForeignKey, and
>> configurable applications.
>
> not really, it's only conf
On Tue, Sep 14, 2010 at 12:50 AM, Tobias McNulty wrote:
> On Sun, Sep 12, 2010 at 11:55 PM, Tobias McNulty
> wrote:
>>
>> At the DjangoCon sprint this weekend I setup Django on our CI server for
>> OSS and had it reporting on builds in the #django-sprint IRC channel. Would
>> that be useful to c
On Thu, Sep 16, 2010 at 2:28 AM, Yo-Yo Ma wrote:
> I think it might be a good idea to document the direct usage of the
> FileField, and ImageField model fields.
Sure -- sounds like a reasonable proposal to me. Open a ticket on Trac
so the idea isn't forgotten.
We also accept patches :-)
Yours,
On Thu, Sep 16, 2010 at 3:05 PM, akaariai wrote:
> Is there any continuous speed testing done for Django? It would be
> nice to see how performance of Django is evolving. For example while
> working on ticket #14290, seeing how my changes to utils/translation/
> __init__.py affect other parts of t
On Sat, Sep 18, 2010 at 12:49 AM, Jim D. wrote:
> I recently asked a question on Django Users related to executing
> certain code during the global setup and teardown routines that run in
> Django's test runner. In my particular use case, I was looking for a
> hook where I could disable some third
On Sun, Sep 19, 2010 at 3:08 PM, Yo-Yo Ma wrote:
> I got a printout of a stack trace on a white screen: I don't know how
> I can help you guys find the bug since I have zero context with this
> stack trace, but hopefully it helps.
There isn't a great deal we can do to help here. A stack trace by
On Wed, Sep 22, 2010 at 6:00 PM, rihad wrote:
> I have these fields in a model:
>
> ipaddr1 = models.IPAddressField()
> ipaddr2 = models.IPAddressField(blank=True, null=True)
>
> When I "wrap" this model in a ModelForm, fill the form, and call
> form.save(), empty ipaddr2 gets insert
On Sat, Sep 25, 2010 at 8:59 AM, Yo-Yo Ma wrote:
> Chuck - Thanks. Perhaps there isn't such room for improvement on the
> topic.
>
> Jacob - It appears to me that you don't read things before you comment
> on them. That's two times in one post. Patience is a virtue, my
> friend.
This conversation
Hi all,
I've just uploaded a first draft at a patch introducing logging into
Django [1]. I'm calling for feedback on this patch.
[1] http://code.djangoproject.com/attachment/ticket/12012/t12012-alpha1.diff
This patch is heavily drawn from the work that Vinay Sajip has done in
this area, but it a
from url resolution.. something I think I need to add.. I'll
> busy a ticket for it :)
>
> D
>
> On Sat, Sep 25, 2010 at 4:16 PM, Russell Keith-Magee
> wrote:
>> Hi all,
>>
>> I've just uploaded a first draft at a patch introducing logg
On Sat, Sep 25, 2010 at 8:47 PM, Waldemar Kornewald
wrote:
> Hi,
> in my last discussion on django-users Russell told me that he'd like
> to see four proof-of-concept (or better) backends before considering
> NoSQL for inclusion in trunk.
The number 4 wasn't actually the important bit - it was th
On Sun, Sep 26, 2010 at 1:24 AM, Waldemar Kornewald
wrote:
> On Sep 25, 4:21 pm, Russell Keith-Magee
> wrote:
>> My reason for wanting this is that I'm simply not an expert in any of
>> these backends. I know SQL quite well, but I haven't had occasion to
>> try
On Sun, Sep 26, 2010 at 1:47 AM, Carl Meyer wrote:
> Hi all,
>
> I've seen some level of interest in the idea of a lazy foreign key
> (one whose target table is determined by project configuration in some
> way, not hardcoded by the app/model in which it lives). The idea was
> most recently brough
On Sunday, September 26, 2010, Yo-Yo Ma wrote:
> I apologize Russell. There's been a gross understanding of what I was
> asking. I'm not asking how to do "if settings.debug: x = y". I'm
> asking for a way to set settings.debug to true dynamically without
> having to rely on deployment specific iss
1401 - 1500 of 2850 matches
Mail list logo
