On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> to make it work I had to replace in your views all occurences of:
> ManyToOne by ForeignKey
> ManyToMany by ManyToManyField
The patch was extracted from a modified copy of magic-removal which
I'd been running for a while, there should have been no ne
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> How do I specify the use of Dojo rich-text editing widget in my model ?
You'll want to take a look at Dojo's documentation at
http://dojotoolkit.org/docs/
> I don't know why M2M does not render properly, here is an excerpt of
> the displayed page so
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> What I see is a simple multiselection list, so I suspect that the
> related Dojo is not loaded.
Does your browser report any JavaScript errors?
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~-
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> Now just a silly question: what is the value added by Dojo ?
A few things.
The one that most people have been clamoring for is easy AJAX
functionality; Dojo's libraries for that are really simple to use.
But the big deal for me is the packaging sys
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> Note: the fact that I have to rename this is still relevant:
> ManyToOne by ForeignKey
> ManyToMany by ManyToManyField
In what files and locations are you having to do this?
--
"May the forces of evil become confused on the way to your house."
--
On 4/13/06, Viktor <[EMAIL PROTECTED]> wrote:
> Of course, every requested url must be URLencoded, but that is browsers
> job, and they all do it quite well.
Except that that runs contrary to the purpose of the slug. See below.
> Yes, they are (more and more every day)... (for example Wikipedia u
On 4/14/06, oggie rob <[EMAIL PROTECTED]> wrote:
> There was talk of processors that could possibly/probably do a cleaner
> job than this - not sure where these stand.
http://www.djangoproject.com/documentation/settings/#template-context-processors
--
"May the forces of evil become confused on t
On 4/14/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
> I would sooner blame your setup or software for not properly
> supporting such links.
The thing is, this *is* "proper support". The URL is still accessed
correctly, and the page is displayed correctly. But the URL string
itsel
On 4/21/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> so i have two problems.. the first is:
> - is there some dispatch thing I can connect to so that this function
> gets called at the right time
To clarify a bit after some late-night IRC chatting about this:
What Ian's trying to do, basically,
On 4/21/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> Which patch there is the "one true patch"(tm) ;) comments.3.diff?
Looks like it; it seems to match pretty closely with the patches I'd
submitted on #1659, which cover parts of the comments app as well (and
on that ticket, the most recent
On 4/25/06, Petar Mariæ <[EMAIL PROTECTED]> wrote:
> So, a free global licence for a buffed-up version to one of best
> WYSIWYG XHTML editors today in exchange for a link to xhtml.com? I'm
> so +1 on this :D
I'm so -1 on this that words fail me. WYSIWYG HTML editors should be
the concern of specif
I got bitten by ticket #1675 today, and took some time to work out
exactly what was going wrong. It turned out I was setting up my custom
tag library incorrectly, but the process revealed some magic that
magic-removal hasn't gotten rid of.
In looking at how the 'load' tag is implemented, I was co
On 4/27/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> A definite -1 on this from me, because it's out of Django's scope.
Agreed.
Also, for the as-yet-undetermined future when we have Dojo integration
merged, people who want WYSIWYG will be able to hang the Dojo
rich-text widget on any text fi
Tonight as part of the 1.4 development process, we've released the
first alpha for Django 1.4. You can read all about it on the blog:
https://www.djangoproject.com/weblog/2011/dec/22/14-alpha-1/
And in the release notes:
https://docs.djangoproject.com/en/dev/releases/1.4-alpha-1/
--
"Bureaucr
On Tue, Dec 27, 2011 at 8:30 AM, Ryan McIntosh wrote:
> With the utmost respect, I must rebuke Paul's claim that this discussion is
> misplaced on the dev list. We all have a stake in this legislation. All
> free software projects have a stake in this legislation. I urge those
> unfamiliar w
Folks, we've had three different members of core point out that,
important as it is, this is a topic for another list/forum. Please
take the discussion there, now.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message because you are sub
On Wed, Feb 15, 2012 at 4:37 PM, Donald Stufft wrote:
> I know this has been discussed before, but I wanted to bring it up again in
> light of the oncoming Djnago 1.4 beta.
So, here's the thing: you're asking for a fairly significant,
massively backwards-incompatible change which requires every D
Hot off the presses, it's the first Django 1.4 beta! Blog post with
more information is here:
https://www.djangoproject.com/weblog/2012/feb/15/14-beta-1/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message because you are subscribed to
We're nearly there!
The Django 1.4 release candidate package is now available, and you can
read all about it on the blog:
https://www.djangoproject.com/weblog/2012/mar/05/14-rc-1/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message be
Subject line says it all, and details, as always, are on the weblog:
https://www.djangoproject.com/weblog/2012/mar/14/14rc2/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroup
Django 1.4 is finally here!
For details, checkout the weblog:
https://www.djangoproject.com/weblog/2012/mar/23/14/
And the release notes:
https://docs.djangoproject.com/en/dev/releases/1.4/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group
On Mon, Mar 26, 2012 at 7:44 PM, Reinout van Rees wrote:
> Having a release before the tag? Sounds weird to me. Making a tag is
> integral to the actual release, right? Curious :-)
The tag and the release package are both just the same revision from
trunk, so there is no requirement for the tag t
Questions about how to use Django should be directed to the
django-users mailing list. This list is for discussion of development
of Django itself.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
Today we've issued several releases to remedy security problems
reported to the Django team.
Details are here:
https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/
All users are encouraged to upgrade immediately.
--
You received this message because you are subscribed to
Today we've issued Django 1.3.3, a quick bugfix release which restores
Python 2.4 compatibility in the Django 1.3 release series:
https://www.djangoproject.com/weblog/2012/aug/01/django-13-bugfix-release/
Affected users are encouraged to upgrade.
--
You received this message because you are sub
Django 1.4.2 and 1.3.4 have just been released in response to a
security issue reported to us.
Details are here:
https://www.djangoproject.com/weblog/2012/oct/17/security/
Everyone is encouraged to upgrade.
--
You received this message because you are subscribed to the Google Groups
"Django d
Our first milestone on the road to Django 1.5 came today, with the
release of the first alpha package.
Blog post about it is here:
https://www.djangoproject.com/weblog/2012/oct/25/15-alpha-1/
Release notes are here:
https://docs.djangoproject.com/en/dev/releases/1.5-alpha-1/
And you can get th
Our second milestone on the road to Django 1.5 came today, with the
release of the first beta package.
Blog post about it is here:
https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/
Release notes are here:
https://docs.djangoproject.com/en/dev/releases/1.5-beta-1/
And you can get the
Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued
in response to security issues.
Details are available here:
https://www.djangoproject.com/weblog/2012/dec/10/security/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
On Sat, Dec 22, 2012 at 6:28 PM, Kevin Veroneau wrote:
> I believe, it would be most beneficial for the Django website to provide
> such an option. I bet most Windows users who hear about Django visit the
> website, but don't see a download link for their system. These users will
> either seek h
1.5 is almost here!
Today marks the release candidate, which you can read about on the weblog:
https://www.djangoproject.com/weblog/2013/jan/04/15-rc-1/
Assuming no release-blocking bugs, Django 1.5 will be released next week.
--
You received this message because you are subscribed to the Goog
On Sun, Feb 17, 2013 at 1:17 AM, Skylar Saveland
wrote:
> I would be interested in getting this (or something like it) into 1.4.X and
> 1.5.X. Might this be possible?
Unless it fixes a release-blocking regression, it's not possible for
this to get into either of those release branches. Also, gene
We've issued several security releases today. Details are in the blog post:
https://www.djangoproject.com/weblog/2013/feb/19/security/
We recommend everyone carefully read this one, as it has an
end-user-visible change requiring action beyond simply upgrading your
Django package.
--
You receive
Yup, it's finally here!
* Announcement blog post here:
https://www.djangoproject.com/weblog/2013/feb/26/15/
* Release notes here: https://docs.djangoproject.com/en/1.5/releases/1.5/
* Download it here: https://www.djangoproject.com/download/
--
You received this message because you are subscribe
-1.
The conflict between niche "technically correct terminology even if no-one
actually uses these words" terms and "technically incorrect terminology but
everybody uses it anyway" should, in most cases, be won by the
technically-incorrect terminology. My favorite relevant examples of this
are the
On Thu, Jan 15, 2015 at 12:05 AM, Horacio G. de Oro
wrote:
> If you see the new hash in the database, I think that, maybe the admin, is
> saving the user instance with the new hash. And doing that, ie: save()'ing
> the user returned by authenticate() solved the issue for me too (but I
> don't wan
Please keep discussion going in this mailing-list thread, and keep in mind
Django's policies regarding re-opening a "wontfix" ticket (which are
essentially: don't do it).
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django its
There's been some recent discussion in a django-users thread[1] about
the impending end-of-life of Django 1.6, which in turn will mean
end-of-life for Django supported on Python 2.6. In addition, the
end-of-life of the current LTS release, Django 1.4, will mean
end-of-life for Django supported on P
On Wed, Apr 1, 2015 at 10:28 AM, Stan wrote:
> A classical pip install Django command without --mirrors or --use-mirrors
> modifier.
>
> I did some --upgrade, but the first installation is not 10 years old (2
> maybe).
>
>
> Pip is a Debian package (1.1.3)
>
> [$ whereis django-admin
> django-adm
There's not much to this, really, except what's in the subject line of this
message.
The problem of providing a single-file, no-build-step format for
distributing and installing Python packages has been solved by wheels, and
wheels also don't cause the pile of weirdness that comes with using eggs.
One option for declaring an app "unmanaged" could be via AppConfig. That's
fairly clean, mirrors the way you can already set a model as unmanaged in
its Meta declaration, and allows for the end user of the app to override by
supplying an AppConfig which will generate migrations (should they, for
so
On Tue, Aug 11, 2015 at 5:43 PM, Tim Graham wrote:
> It seems that django-contrib-comments has a moderation feature where you
> can specify a field on your model to control how comments are handled [2],
> so this was presumably used for that.
>
>
The field on FlatPage has been there since the beg
On Sat, Aug 29, 2015 at 1:54 PM, Florian Apolloner
wrote:
> Which is? Following the ticket I do not see any clear consenus at all. Imo
> Registration apps should handle that, which is not something Django ships
> with. I am -0 on changing the admin to disallow such users.
>
For what it's worth,
ms
of potential impersonation.
On Sat, Aug 29, 2015 at 2:59 PM, Tim Graham wrote:
> The suggested change is to not allow a new user if there's a
> username__iexact match.
>
> On Saturday, August 29, 2015 at 2:56:14 PM UTC-4, James Bennett wrote:
>>
>> On Sat, Aug 29,
8 years later, I still think we should figure out how to make exclude() do
what people expect it to do, rather than implement another lookup type that
overlaps with it.
On Fri, Nov 20, 2015 at 7:27 PM, Aaron C. de Bruyn
wrote:
> With all due respect, looking through the ticket and reading respon
Bumping this thread a bit because I subscribe to Debian's tracker for their
Django package, and there's some question of whether we do or do not
officially support Python 3.5 on Django 1.8. Was there ever a final
decision?
On Tue, Oct 27, 2015 at 5:19 PM, Ned Batchelder
wrote:
> BTW, there's a m
Never mind, just saw that 3.5 is listed in the 1.8 release notes and
answered my own question.
--
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 emails from i
About two months ago, ticket #25548[1] was opened, pointing out that
on an invalid form submission, FormView was calling form validation
methods twice (what was actually happening was that the original form
instance was discarded, a new one constructed with the same data, and
the first access to it
Thanks to everyone for the quick consensus, and to Tim for backporting it
and fixing the docs before I could get around to it :)
On Mon, Dec 7, 2015 at 9:23 AM, Tim Graham wrote:
> Done in
> https://github.com/django/django/commit/9c835990ea2911c06a877296fbc25157c1302e1d
> -- thanks for pointing
The Django team has just issued Django 1.2.2 to deal with a reported
security issue. Full details are available in the blog post:
http://www.djangoproject.com/weblog/2010/sep/08/security-release/
All users of Django 1.2 are urged to upgrade immediately.
--
"Bureaucrat Conrad, you are technicall
To correct several issues in the 1.2.2 package earlier this week,
tonight the Django team has issued Django 1.2.3. Details are available
on the Django weblog:
http://www.djangoproject.com/weblog/2010/sep/10/123/
All users are encouraged to upgrade as soon as possible.
--
"Bureaucrat Conrad, you
On Tue, Oct 19, 2010 at 1:49 PM, Jacob Kaplan-Moss wrote:
> Looks like a good idea to me. I've certainly used ssi as a hack for
> this before, so getting a noparse/verbatim tag into Django sounds
> great.
If we're going to do this, could we also look at deprecating the
'templatetag' template tag?
On Thu, Oct 21, 2010 at 1:29 AM, Ivan Sagalaev
wrote:
> Can someone of core committers clarify this: is it now recommended to write
> all views as classes?
Django cares about whether your views meet the following criteria:
1. Is a callable object.
2. When called, accepts an instance of HttpReque
On Thu, Oct 21, 2010 at 3:50 AM, Waldemar Kornewald
wrote:
> It's not even future-proof. We're heading towards larger client-side
> web apps which means there will be HTML5 offline manifests and apps
> consisting of more than 50 files. Even the combination of
> django_compressor with staticfiles c
On Tue, Oct 26, 2010 at 7:23 PM, Alex Gaynor wrote:
> It depends what you mean by "MySQL" compatible. If by that you mean
> that it's importable as mysqldb and implements the exact API it should
> work out of the box, more or less. However, if by that you mean it
> implements PEP-249 you really
The first alpha preview package for Django 1.3 is now available.
* Release notes: http://docs.djangoproject.com/en/dev/releases/1.3-alpha-1/
* Download instructions: http://www.djangoproject.com/download/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You
On Thu, Nov 18, 2010 at 4:38 AM, Valery wrote:
> guys, now also all the MongoDB Python developers are waiting for your
> signals about Python 3.
That's... a really bad idea.
Our Python 3 migration process, at this point, is more or less
dictated by two things:
1. WSGI on Python 3
2. Distributio
I've just opened ticket #14937[1] with a patch implementing what
seemed -- last time around -- to be the consensus fix for the ongoing
fracas that is the list of "state" choices in contrib.localflavor.us.
The patch attempts to avoid international incidents by use of
relatively fine-grained sets of
Tonight we've released Django 1.3 beta 1, as well as Django 1.2.4 and
Django 1.1.3 to correct a pair of security issues.
* Beta announcement: http://www.djangoproject.com/weblog/2010/dec/22/13-beta-1/
* Security announcement:
http://www.djangoproject.com/weblog/2010/dec/22/security/
All affected
On Tue, Jan 4, 2011 at 8:52 AM, Alexander Pugachev
wrote:
> Why http://code.djangoproject.com/ticket/14202 is not in trunk being accepted?
Short answer: because "accepted" doesn't mean "closed, fixed".
Longer answer: up until the beta release, just before Christmas, quite
a bit of development ti
On Wed, Jan 5, 2011 at 10:05 AM, Russell Keith-Magee
wrote:
> We will obviously to do a 1.2.5 release when we hit 1.3 final; but I'm
> not sure if we should push an 1.2.5 (and 1.1.4) ASAP addressing these
> regressions, and then do 1.2.6 when we cut 1.3 final.
I'm in favor of doing 1.2.5 as soon
On Tue, Jan 25, 2011 at 3:45 PM, Graham Dumpleton
wrote:
> Since the 'futures' module is only a part of Python 3.2, that must mean you
> are using that and thus have ported Django to Python 3 already. When can we
> expect that then. ;-)
So, here's what happened.
You all may remember that some ti
Tonight the Django team has released updated versions of Django 1.2
and Django 1.1 to correct multiple security issues reported to us.
* Details in the blog post here:
http://www.djangoproject.com/weblog/2011/feb/08/security/
* Download updated versions of Django here:
http://www.djangoproject.co
Tonight we're proud to announce the first release candidate for Django
1.3; if all goes well, the final release will happen in about a week.
Details for the release candidate are available on the official Django weblog:
http://www.djangoproject.com/weblog/2011/mar/03/13-rc/
--
"Bureaucrat Conr
It's here!
Django 1.3 has been officially released.
Blog post here: http://www.djangoproject.com/weblog/2011/mar/23/13/
Release notes here: http://docs.djangoproject.com/en/dev/releases/1.3/
Download here: http://www.djangoproject.com/download/
--
"Bureaucrat Conrad, you are technically correc
Today we've released Django 1.3.1 and Django 1.2.6 to deal with
several security issues reported to us. Details of these issues and
the releases, along with several important advisory notes, are
available in the blog post on djangoproject.com:
https://www.djangoproject.com/weblog/2011/sep/09/secur
Due to an issue with yesterday's 1.2.6 release package, today we are
issuing Django 1.2.7. All users of 1.2.X Django should upgrade to
1.2.7, rather than to 1.2.6.
Details here:
https://www.djangoproject.com/weblog/2011/sep/10/127/
--
"Bureaucrat Conrad, you are technically correct -- the best
We have the following constraints:
1. Django supports class-based views.
2. Django supports function-based views (ultimately these are the same
thing, which is that Django supports anything as a 'view' so long as
it's callable, accepts an HttpRequest as its first positional argument
when being ca
Sigh.
In [7555] I added a warning to the flatpages docs to hopefully silence
this issue once and for all. Note that I did this not because I feel
it's necessary or appropriate, but because I'm just getting really,
really, really tired of people complaining about this. Can we please
let this one g
On Sat, Jun 7, 2008 at 11:48 AM, Rob Hudson <[EMAIL PROTECTED]> wrote:
> I think the most often reason why I've heard is that it takes time to
> create a release, post it, push security patches to it, etc. Which
> makes sense, but at the same time there are a lot of valid points in
> the blog pos
On Sat, Jun 7, 2008 at 2:06 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> * Start a "train release" schedule: schedule a couple of 1.0 betas, a
> rc or two, and then a final release. Features that are done by the
> dates get released, those that aren't, don't. Make these dates
> aggressive bu
On Sat, Jun 7, 2008 at 7:46 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> Right now Backwards Incompatible changes are documented in a wiki page,
> with some disadvantages:
And in the release notes when a new release happens.
--
"Bureaucrat Conrad, you are technically correct -- the best kind o
And for the record, I do think that *post-1.0* we should do more
frequent releases, because it'll be quite a bit simpler to do at that
point. I just think that right now it's not really worth the trouble;
the same people who currently complain that they have to use a
packaged release but want a po
Just a quick procedural thing:
The 0.96.2 tarball created for the recent security fix was generated
from the 0.96 setup.py script, which gets you the Django source tree
but misses things like the documentation files that we distribute with
Django. This has caused a couple of issues with downstrea
On Sun, Jun 8, 2008 at 9:51 PM, Ashish <[EMAIL PROTECTED]> wrote:
> my proposal is
You do know that a list of what has to happen before 1.0, and a page
listing the status of each item, has been available for quite some
time, right? I
> Lack of visibility on what is going on with 1.0 and over an
On Mon, Jun 9, 2008 at 1:50 AM, Ashish <[EMAIL PROTECTED]> wrote:
> In short all I am looking for is commitment to " freezing the scope,
> publishing a plan and hitting it for 1.0 " That will greatly increase
> the community's trust.
Er. You linked to a well-known thread in which the plan for 1.
On Mon, Jun 9, 2008 at 11:54 AM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> I believe it's one official release back. James will know better.
For security we patch trunk, of course, as well as current stable
release plus the two previous releases. This means we currently
provide security updates
On Mon, Jun 9, 2008 at 1:09 PM, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Posting this here rather than someone's blog post comments:
Rob, let me step back a moment and point out how this comment would
strike me if I didn't know you and didn't know that it wasn't your
inention to come off this w
On Mon, Jun 9, 2008 at 2:47 PM, J. Cliff Dyer <[EMAIL PROTECTED]> wrote:
> I agree with the sentiment of this, but we've passed the point where
> it's a useful argument.
I'll concede that if you'll concede that we've also passed the point
where issuing interim pre-1.0 releases offers any real gai
On Tue, Jun 10, 2008 at 10:38 AM, Rob Hudson <[EMAIL PROTECTED]> wrote:
> I am curious if anyone thinks having support for outputting html4
> compliant markup in Django is a good thing? And if so, what can I do
> to help make that become a reality?
I for one would appreciate it, because I'm abot
On Tue, Jun 10, 2008 at 12:24 PM, testguy56 <[EMAIL PROTECTED]> wrote:
> Wow, starting a reply like that makes you sound like an elitist douche
> bag.
I love the smell of troll in the morning, don't you?
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~--
(incidentally, for anyone who's joining in and wants to genuinely add
to the discussion: starting your reply by calling one of the
developers a douchebag causes me, at least, to stop listening and
simply assume you're a troll. The more you know...)
--
"Bureaucrat Conrad, you are technically cor
On Tue, Jun 10, 2008 at 5:46 PM, Edgars Jēkabsons
<[EMAIL PROTECTED]> wrote:
> I'd like to remind everyone involved that Django development really
> seems to stale when looking at active tickets.
>
> There are 1116 active tickets right now, 341 of them haven't even been
> reviewed and 201 of the re
On Mon, Jun 9, 2008 at 3:57 PM, J. Cliff Dyer <[EMAIL PROTECTED]> wrote:
> As mentioned in my previous post, if it's indeed three months, I agree,
> but if it's only "hopefully" three months, then do we want to end up six
> or nine months out still waiting for 1.0 to land "in a couple months?"
We
On Wed, Jun 11, 2008 at 9:23 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> This does mean newforms-comments will be a late feature to the trunk (although
> only 3 weeks after the feature cutoff for other features), but if we encourage
> testing in its own branch, we should be able to mitigate
On Wed, Jun 11, 2008 at 11:17 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have to ask why must Django prevent work in this regard?
To be perfectly fair, it's not really "prevented". Django supports the
use of database backends not defined in Django itself, so third-party
development of b
On Thu, Jun 12, 2008 at 11:10 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> And this is great of course. But having to develop externally away
> from the many eyes of the Django community is sort of an impairment.
> It's a lot easier to get traction on a project that is in the Django
> repo
On Mon, Jun 16, 2008 at 9:22 AM, Johannes Dollinger
<[EMAIL PROTECTED]> wrote:
> Is there a rationale for multiple managers per model?
Yes, and I at least use them all the time. For example, I'll often
have one manager that does no special filtering, and another that only
returns things with a "l
On Mon, Jun 16, 2008 at 10:22 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Has anyone else noticed that development progress seems to have
> exploded since this thread was created? In the weeks/months after the
> qs-rf merge, several days would go by when there wasn't a single
> change commi
On Mon, Jun 16, 2008 at 9:44 AM, Johannes Dollinger
<[EMAIL PROTECTED]> wrote:
> If you're just want different querysets you can use something like
> this: http://dpaste.com/53948/.
Or I can use managers and also add other supporting methods (which I
also often do).
--
"Bureaucrat Conrad, you
On Mon, Jun 16, 2008 at 1:48 PM, Johannes Dollinger
<[EMAIL PROTECTED]> wrote:
> You could as stick them in a single manager as well (and wouldn't
> have to remember which method is available via which manager).
> My point is that one manager per model would be enough to do anything
> you can do w
On Wed, Jun 25, 2008 at 4:21 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> Specifically, I'd like you to note interactions with user "Magus-"
> (with trailing dash).
Four points:
1. His name is Collin.
2. He's one of the channel ops.
3. As someone who hangs out in the channel pretty much 24/7 I can
On Mon, Jul 7, 2008 at 8:29 PM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> Currently, ReverseSingleRelatedObjectDescriptor uses _default_manager,
> which is the problem (line 239 in django/db/models/related/fields.py).
> One clean solution would be to give each model a _pristine_manager
> attrib
On Tue, Jul 8, 2008 at 8:26 AM, vcc <[EMAIL PROTECTED]> wrote:
> I just updated this backend, it's look like everything work fine for me. I
> have some projects working with this backend, I'll keep improve it. Please
> check the patch in the attachments.
As Russ, and the many previous threads h
This list is not for general usage questions; rather, it is for
discussion of the development of Django itself. Please keep usage
discussion on django-users.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~-~--~~~---~--~~
Y
On Fri, Jul 18, 2008 at 1:59 PM, Frijole <[EMAIL PROTECTED]> wrote:
> Does anyone know how to get tickets for the DjangoCon, I though they
> were releasing them today?
When the time comes there will be a large and loud public announcement
that you will not be able to miss.
--
"Bureaucrat Conra
As of the newforms-admin merge, the IRC channel is seeing a sudden
rush of folks who try the tutorial and complain because the admin
doesn't work. And they're right, because as written the tutorial sets
up the admin in such a way that it's never aware of any models being
registered -- including th
On Fri, Aug 22, 2008 at 4:08 PM, Yuri Baburov <[EMAIL PROTECTED]> wrote:
> Really?
Dude. Don't be that guy. OK?
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~-~--~~~---~--~~
You received this message because you are subs
On Fri, Aug 22, 2008 at 4:08 PM, Yuri Baburov <[EMAIL PROTECTED]> wrote:
> 1) You have less than 2 weeks left and still 188 tickets marked with
> 1.0 tag
Correction: we have 153 tickets open with the 1.0 milestone. Not bad
for eight hours' work, IMHO, and we've still got a couple sprints left
to
On Sun, Aug 24, 2008 at 12:53 AM, Jonas Pfeil <[EMAIL PROTECTED]> wrote:
> P.S.: I should have brought this up here earlier instead of causing a
> somewhat lengthy discussion on IRC, sorry for that. I hope James
> doesn't hate me after this ;)
I stand by what I said in the dev channel yesterday:
501 - 600 of 1014 matches
Mail list logo
