Ludvig Ericson wrote:
> On Nov 25, 2008, at 18:08, Jacob Kaplan-Moss wrote:
>> I'd like to officially drop Python 2.3 support in Django 1.1. Discuss.
>
> Oh god please, YES! Gimme my decorator syntax sugar, oh yeah.
... and generator expressions, too!
+1
--~--~-~--~~~--
Waylan Limberg wrote:
> For a start, you may want to take a look as Malcolm's recent
> multi-part series on the subject. Note the third one with regard to
> content-types.
>
> http://www.pointy-stick.com/blog/2008/12/09/implementing-http-services-django/
> http://www.pointy-stick.com/blog/2008/12
Ed Summers wrote:
> In my
> case I'm implementing an AtomPub interface for a data repository at
> the Library of Congress instead of wanting to stream XML, but the
> mechanics are the same.
Yes. It's expected to look something like this:
if request.META['Content-type'] == 'application/atom+
Malcolm Tredinnick wrote:
> Russ, Nicolas and, to some extent, myself, have been working fairly
> solidly on the aggregates stuff which is now close to completion (I've
> got one thing to commit before Russ does a final merge).
BTW does it include F-expressions thing? I had an impression that it
Russell Keith-Magee wrote:
> 1) Expose the underlying operations, warts and all. Provide a minimal
> test suite
I'm +1 for this option. Here are some comments why I don't like others:
> 2) As for (1), but provide a comprehensive test suite that checks the
> different expected results for each b
Russell Keith-Magee wrote:
> Expected:
>[('id', 2), ('isbn', u'067232959'), ('manufacture_cost',
> ...11.545...), ('mean_auth_age', 45.0), ('name', u'Sams Teach Yourself
> Django in 24 Hours'), ('pages', 528), ('price', Decimal("23.09")),
> ('pubdate', datetime.date(2008, 3, 3)), ('publisher_i
Alex Gaynor wrote:
> Probably stupid question
Which it was :-). I didn't realize that it's doctests.
> you need to replace it with
> >>> Decimal("3.0") == Decimal('3.0')
> True
So why not?
--~--~-~--~~~---~--~~
You received this message because you are subs
Vladimir Prudnikov wrote:
> So, at my point it, lets say, "bad style" of coding. The idea is to
> keep original field content without any modification. XML and RSS
> specification allow and recommend it, why to not use it?
As Malcolm said, Django does use it, i.e. it does escape HTML to
pres
Russell Keith-Magee wrote:
> For those watching trunk, revision 9742 added aggregate support to
> Django. (Yay!)
Thank you all very much! This is big.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django develope
Karen Tracey wrote:
> For the most part this change should be invisible, except for the speed
> improvement when running tests. However, if you have tests that need to
> actually test the effects of transaction commit or rollback, you will
> now need to use a django.test.TransactionTestCase in
Ivan Sagalaev wrote:
> Karen Tracey wrote:
>> For the most part this change should be invisible, except for the speed
>> improvement when running tests. However, if you have tests that need to
>> actually test the effects of transaction commit or rollback, you will
Karen Tracey wrote:
> Hmm, not sure what is going on here. Django's admin_views testscase
> uses client and fixtures, and doesn't have a problem. It should not
> happen that data loaded by one TestCase persists in the database to
> another test. TestCase setup starts a transaction and disabl
Julien Phalip wrote:
> There probably are a few other tickets in
> that situation (#9404 is another example).
And http://code.djangoproject.com/ticket/9591 is yet another.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gr
Marty Alchin wrote:
> I'm not opposed to adding readline(). It's part of the standard file
> protocol
BTW, it's required by PIL when it reads file objects. So it's useful in
practice, not only for completeness.
--~--~-~--~~~---~--~~
You received this message beca
Hello!
This Malcolm's reply in a nearby thread:
> Unless you're
> using really huge querysets, the memory usage is not going to kill you.
> Pulling back the huge number of results already uses a bunch of memory
> and that's a property of the db wrapper.
... has reminded me that this behavior wa
Malcolm Tredinnick wrote:
> So, once again, it was Jeremy stirring the pot and it's you keeping the
> issue alive a couple of years later.
Well, the issue wasn't resolved. What could I do? :-)
> I think the comments and requests for information Younger Me made in
> that thread are still valid. T
Russell Keith-Magee wrote:
> Semmel and yourself both hang your arguments on the claim that Monday
> as the start of the week is the "most supported" option, or the "most
> common" option. I simply don't see any evidence that this is the case.
I was always under an impression that Sunday is consi
Hello everyone!
Just played with new defer() and only() and noticed that fields deferred
with only() aren't loaded when asked explicitly. I.e.:
a = Article.objects.defer('text')[0]
a.text # <-- does a new query as expected
a = Article.objects.only('date')[0]
a.text # <-- do
Alex Gaynor wrote:
> 8) Time permitting implement a few common replication patterns.
I'm kind of not very excited with this point.
To me replication is a major use-case. I suspect most people who move
beyond single server setup and beyond 10'000 - 20'000 visitors realize
that replication shoul
Jacob Kaplan-Moss wrote:
> I've mostly stayed out because it's not something I feel strongly
> about, but I am +0 on the change. The reason I don't much care is that
> it really comes down to a lines of code argument; is::
>
> obj.update(x=1, y=2, z=3)
>
> really that much "better" than::
>
Malcolm Tredinnick wrote:
> On Mon, 2009-03-23 at 10:44 +0300, Ivan Sagalaev wrote:
>> Looks like a "+0" useful API wrapper around direct calling of
>> _default_manager.
>
> Would they also like a stable and saddle with that pony?
Actually, this very concept has
bkonrad wrote:
> 1.Predictable URI Naming
Apart from my serious doubt that this can be done at all I'd like to
point out that the very notion of *predicting* URLs is not RESTful. URLs
are generated by server (by whatever logic it chooses) and client treats
them as opaque identifiers. The m
Glenn Maynard wrote:
> TransactionMiddleware assumes that when process_request is called,
> either process_exception or process_response is guaranteed to be
> called. This isn't the case if another middleware raises an exception
> first. If this happens, the call to
> transaction.enter_transacti
Adys wrote:
> Clean:
> http://example.com/foo/bar
>
> Unclean
> http://example.com/foo/bar/
> http://example.com/foo///bar
> http://example.com///foo//bar///
Sorry for interrupting your lively conversation gentlemen... If you
allow me to give an advice then your proposal will look better wi
Adys wrote:
> And please don't speak "on behalf" of other Django developers.
I don't. It's a simple matter of fact that APPEND_SLASH defaults to True
and CommonMiddleware is installed be default and djangoproject.com uses
trailing slash and first four sites from http://djangosites.org/ also do
Zachary Voase wrote:
> I just found out that a particular Django ORM trick [1] seems to work
> just fine but is undocumented.
By the way... While it may be really neat it doesn't quite "eliminates a
lot of the race conditions" as you write. If you're incrementing a field
in several parallel tra
Marc Fargas wrote:
> You could write an Exception middleware that takes care of processing
> your "special" exception. Bu anyway, note that you are willing is to
> give "response" so the right thing to do would be returning a response
> object
The latter is not very convenient. Often the code tha
Forest Bond wrote:
> But your model code shouldn't have HTTP-related bits buried in it. That's a
> layering violation. That code should raise a more generic exception that your
> view code converts to an HTTP response.
Yes, this is may be more correct way. But having one exception without a
co
Brent Hagany wrote:
> The issue of making shortcuts better (and decreasing the number of
> imports in views.py files) was brought up at DjangoCon
Another angle on the issue of reducing imports is that we can do it not
with shortcuts only but by packing some smaller modules into larger
ones. For
Malcolm Tredinnick wrote:
> As a general process, I'm inclined to think it's the wrong direction --
> making namespaces larger and larger. That way lies PHP or web2py.
Having read your replies in this thread I refrain from speaking about
general directions :-). This one was about particular issu
Hello!
A couple of days ago a sudden thought has struck me while thinking on
the matter of logging in Python libraries. I consider a good practice
for a library to log what it's doing into a named logger without setting
up logging by itself. It's then a responsibility of an application that
w
Russell Keith-Magee wrote:
> For the record, there is one notable use for the legacy behavior -
> debugging at the console. i.e., issue a query at the Python prompt,
> then print connection.queries[-1] to see what was executed.
Yes, and we can keep it. As I said a simple custom log handler can do
Malcolm Tredinnick wrote:
> Adrian, in particular, has been historically against adding logger
> module hooks in Django. So you have to work around that.
Interesting... Adrian, can you elaborate?
> I have a patch I've been holding over for 1.2 that reduces the current
> debug wrapper's log metho
Malcolm Tredinnick wrote:
> Unfortunately, this ticket doesn't solve Ivan's problem of the moment,
> as far as I can see.
Yeah, it sends signals in addition to maintaining connection.queries. My
point (or one of them) is to replace current hard-coded implementation
with something lower-level a
13 01:23:52 UTC+1 schreef Russell Keith-Magee het
> volgende:
>>
>>
>> On Thu, Mar 28, 2013 at 7:13 AM, Ivan wrote:
>>
>>>
>>> Yes, you are right. But I asked for another reason.
>>> For example, I see, that werkzeug's cache write cache tro
> During cache body creation, concurrent processes can also make useless
cache bodies in case usage tmp file (not locking).
-- sorry, during cache writing to tmp file...
2013/5/31 Ivan Smirnoff
> I was also created the backend, but did not have time to make a fork.
> Se
ser stories.
What do you think?
Best regards,
Ivan
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
T
Hi, Carl,
On 09/27/2013 09:01 PM, Carl Meyer wrote:
> Hi Ivan,
>
> On 09/27/2013 03:07 AM, Ivan Kharlamov wrote:
>> Maybe I'm a careless kind of guy, but when I test out new versions of
>> Django, reading all of the release notes is rarely the first thing that
>
en I was
running the project with `gunicorn_django` in conjunction with Django
1.6, but I didn't take time to debug and report them since
`gunicorn_django` command is deprecated and switching to `gunicorn`
command fixed everything.
Regards,
Ivan
> --
> You received this message becau
y` anyone?
I'm not going to say that this is a very big deal, of course, since a
custom template filter is easy to write.
Philosophically speaking, by insisting that this issue should be solved
outside of templates and inside of views, you are putting something that
doesn't belong there, si
On 06/26/2014 06:00 PM, e.generalov wrote:
> Hello!
>
> In my AngularJs application I want to reuse some django admin forms (to
> "add", "edit" and "delete" orders)
> but show them in the iframe instead of popup windows.
>
> In order to display "add" form in iframe I create a template:
>
>
On 08/18/2014 02:03 PM, Anssi Kääriäinen wrote:
> As for changing ForeignKey to virtual field plus concrete field
> representation - I just realized this will be backwards incompatible no
> matter what we do regarding categorization. An all-fields including
> get_fields() call will return separate
On 08/20/2014 12:46 PM, Marc Tamlyn wrote:
> I'd say ArrayField is a straight up data field at the moment. It stores
> 0-1 lists of data. It's no different to CommaSeparatedIntegerField
> (seriously, why does that exists...)
>
> *If* PG gets the relevant update that will allow `integer[] reference
On 08/20/2014 03:52 PM, Ivan Kharlamov wrote:
> On 08/20/2014 12:46 PM, Marc Tamlyn wrote:
>> I'd say ArrayField is a straight up data field at the moment. It stores
>> 0-1 lists of data. It's no different to CommaSeparatedIntegerField
>> (seriously, why does that ex
On 08/20/2014 04:28 PM, Ivan Kharlamov wrote:
> On 08/20/2014 03:52 PM, Ivan Kharlamov wrote:
>> On 08/20/2014 12:46 PM, Marc Tamlyn wrote:
>>> I'd say ArrayField is a straight up data field at the moment. It stores
>>> 0-1 lists of data. It's no di
Hi guys,
I am new to Django and I want to contribute to the project soon. Sorry for
the question if it's not appropriate. Do you consider using SonarQube (or
something similar) for code quality analysis?
Regards,
Ivan
--
You received this message because you are subscribed to the G
some
"code smells". That way we can prioritize some of the findings for fixing
in the next releases.
PS: I accept the criticism and won't use guys annymore :)
Regards,
Ivan
On Sunday, August 28, 2016 at 10:23:02 PM UTC+3, Aymeric Augustin wrote:
>
> On 28 Aug 2016, at 20:46,
OK, I will try to do that on my machine and will post the results here
(because frankly speaking I haven't done it before on my own). I don't know
when I will have enough time to do it but I guess 3 to 4 days.
Regards,
Ivan
On Sunday, August 28, 2016 at 11:16:57 PM UTC+3, Aymeri
steps in my blog so some of the Django members could
set up Sonar on his/her machine and see a lot more details and figure out
if it's worth it to fix some of the issues.
On Sunday, August 28, 2016 at 11:16:57 PM UTC+3, Aymeric Augustin wrote:
>
> On 28 Aug 2016, at 21:43, Ivan Seva
t how to export
the whole report in a convenient format.
Regards,
Ivan
On Wednesday, August 31, 2016 at 12:55:35 AM UTC+3, Tim Graham wrote:
>
> Perhaps you could tell us about some of the critical issues so we could
> get a sense for that.
>
> On Tuesday, August 30, 2016 at 4:26:
w the major issues by groups.
Regards,
Ivan
On Wednesday, August 31, 2016 at 2:15:48 PM UTC+3, Tim Graham wrote:
>
> Any security issues should be reported to secu...@djangoproject.com
> , otherwise it's fine to share the information here.
>
> On Wednesday, August 31, 2016 at 2:25
plus some other rules. It's just more convenient.
Regards,
Ivan
On Sunday, September 4, 2016 at 2:38:06 AM UTC+3, Sergei Maertens wrote:
>
> I kind of like these reports, since they can take away some of the early
> review work. I would put it on the same level as the `isort` checks
ed but in my honest opinion I'm not the right person for doing
that. I can copy/paste the rules here but I'm not sure that some of them
are understandable from their short description.
Regards,
Ivan
On Monday, September 5, 2016 at 5:40:41 PM UTC+3, James Bennett wrote:
>
> On Wed,
Hello everyone,
It's been a while since I last posted here, please forgive if I break any
new rules inadvertently.
I'd like to revisit a decision made in [18993][]. My use case is very
simple and obvious: I want all logging going into stdout.
As currently implemented, I can't do it easily with
>
> It’s unclear to me as well how the current system is intended to be used.
>
I can speculate, that the idea was that you *can* disable the existing
loggers and define your own, but the effect of it actually disabling all
logging from Django instead of it falling through to the custom root lo
>
> Just to be sure, which version of Django are you using? There were some
> simplifications in Django 1.9 that attempted to make writing custom logging
> configurations easier and further changes in Django 1.10.
>
I'm using 1.9, but I'm referring to the code in master.
>
> https://github.
oggers` is explicitly set to False, then we could
initialize them as we do now.
How does that sound?
On Tuesday, September 6, 2016 at 5:44:37 PM UTC-7, Carl Meyer wrote:
>
> On 09/06/2016 04:57 PM, Ivan Sagalaev wrote:
> > I'm
> > talking about this function:
> > https
>
> It sounds like you are maybe proposing to decide whether to pre-initialize
> logging with the built-in default config or not based on whether the user's
> LOGGING setting has disable_existing_loggers set to True or False?
>
Yes, I was thinking on my feet and this was one idea I came up with
setting up
SonarQube, sonar-scanner and Python plug-in and post it here. It takes not
more than 15 minutes, so you can see the issues yourself.
Regards,
Ivan
On Tuesday, September 6, 2016 at 3:32:41 PM UTC+3, Ivan Sevastoyanov wrote:
>
> Hello,
>
> I'm back from the vacation.
&
Hello,
Here is my blog post
<https://sevastoyanov.blogspot.bg/2016/09/install-and-configure-sonarqube-for.html>
about setting up SonarQube. I think it takes about 15 minutes, so you can
run it yourself if you want (and if you have time of course). Have a good
day!
Regards,
Ivan
On
pm13 wrote:
> I noted that you would like to implement auto-escaping. It will mean
> third dimension of potential problems with strings.
Why that? Unicode branch is designed to work with byte strings only for
backward compatibility, all new code should use unicode everywhere.
Escaping is just a
Russell Keith-Magee wrote:
> URL path. When rendered, it should take into account settings.MEDIA_URL.
As a matter of fact it's not a universal practice to have css and js
filed under this root. A couple of my projects had them in separate
places (even js separate from css). It can be handled as
Russell Keith-Magee wrote:
> I mostly just want to make sure
> that I fully understand Ivan's use cases, so we can make sure that
> there isn't a better solution lurking around.
My use case was that I just had STYLE_ROOT and JS_ROOT that both were
completely independent on MEDIA_ROOT. I don't re
Malcolm Tredinnick wrote:
> What I'd like to see us do is move "editable" out of the model field
> declaration entirely as part of newforms-admin. It's presentation
> related
I disagree with this specific point. "Editable" is useful to distinguish
calculated (or automatically produced, if you pr
Malcolm Tredinnick wrote:
> No. It has strong "user created semantics", which are orthogonal to the
> data itself. The number "4" exists as a piece of data, irrelevant of
> whether it was created by a user, a machine or a bunny rabbit. The
> database doesn't care. Code using that data doesn't care
Hello everyone (and Malcolm especially)!
This is about template rendering in unicode branch. Template's render
now returns a byte string encoded in a DEFAULT_CHARSET. However just
yesterday I've come across a case where a developer needed to render a
template not to send it over HTTP connectio
Malcolm Tredinnick wrote:
> That sounds reasonable.
Just was about to make a patch but saw your changeset implementing it.
Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
Malcolm Tredinnick wrote:
> Merged in [5609].
Thank you very much!
--~--~-~--~~~---~--~~
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@googlegroups.com
T
Adrian Holovaty wrote:
> I'd like to add a QuerySet.exists() method, which would return True or
> False if the given QuerySet contains at least one record. This would
> be more efficient than qs.count() or len(qs) because it would perform
> the following SQL under the hood:
>
> SELECT 1 FROM
Russell Keith-Magee wrote:
> Hi all,
>
> I've just uploaded a patch to #4460 which adds the ability to start
> individual tests or test cases from a test suite.
Wow, this is handy! Looking forward for commit!
--~--~-~--~~~---~--~~
You received this message becaus
Russell Keith-Magee wrote:
> If all you want is the fixtures, why not use a unittest.TestCase, and
> put a call to management.load_data() in your TestCase.setUp() method?
Speaking for myself I switched to Django's TestCase because it was just
more convenient: it has fixture loading and self.clie
Michael Radziej wrote:
> {% autoescape %} always needs an {% endautoescape %}, generating a node
> during template parsing. Everything between {% autoescape %} and {%
> endautoescape %} is put in its subnode list.
>
> If a VariableNode is below an {% autoescape on %} in the template node tree,
>
Michael Radziej wrote:
> To make this clear, I'll provide an example:
>
Thanks! That's cleared it up.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
Hi!
I am now at the prospect of using a MySQL database in the form of a
2-machine master-slave cluster. If I understand things right this
requires Django to actually know which queries should be directed to
which host, i.e. writes on master, reads on both master and slave.
I'm about to start
Alexis Smirnov wrote:
> If the goal is scalability, one needs to assume a cache-based solution
> isn't appropriate or isn't enough, right?
Yes, we need scalability. We are expecting couple of tens of millions
request a day in a near future.
As for cache... I didn't evaluate it in practice but o
Jacob Kaplan-Moss wrote:
> Yeah, it's gonna be a long road...
Guido's tool "2to3"[1] should make those boring syntax conversions
automatically and leave only juicy parts to human brains.
[1]: http://svn.python.org/view/sandbox/trunk/2to3/
--~--~-~--~~~---~--~~
Y
Yuri Baburov wrote:
> I can't subclass ModelAdmin, because:
>
> class ModelAdmin(BaseModelAdmin):
> def __init__(self, model, admin_site):
> self.model = model
> self.opts = model._meta
> ...
>
> I have no model and have no _meta, have no QuerySet subclass (I have
> v
Malcolm Tredinnick wrote:
> As soon as
> you start to move to situations where your publically exposed resources
> don't map more or less one-to-one onto models, things become a lot
> trickier and we haven't quite solved that
Weren't custom descendants of the Resource class designed for this? I
Malcolm Tredinnick wrote:
> However, I think all our Python db wrappers pull things to the client
> immediately
BTW, a couple of months ago we were investigating behavior of mysqldb in
this regard and found out that doing fetchall and fetchmany indeed eats
the whole data into memory. Even with
Jeremy Dunck wrote:
> Cache invalidation? I agree it's a bit messy, and there's a slight
> chance of the PK value being reused, losing the race. But I've
> thought about using the delete signal for such things.
We actually do this currently in our project. I remember being grateful
to whoever
Hello!
A similar issue was raised on this list some time ago but as far as I
remember there wasn't any proposed solution. I think I have a good one.
I'm trying to solve a problem with the current implementation of
conditional get where ETag and Last-Modified are taken into account only
after
Jeremy Dunck wrote:
> Neat-o. License? If it's OK, I'll use it whether it goes into django
> trunk or not. :)
Let's say it's BSD. This is a part of the tutorial on writing forum in
Django and I didn't think about wrapping it as a product. But if I did
it would be BSD usually :-)
--~--~-
Malcolm Tredinnick wrote:
> So, as an addition to the current behaviour, I'm probably +1 on
> including this. There's a bit of common stuff we can factor out from
> that code to avoid duplication with the middleware and other ETag
> handling code people might want to write, but that's minor stuff.
Hello, Django developers!
When writing reusable apps I've developed a pattern for including
settings specific for the app. For example my forum needs settings for
pagination, unread articles expiration etc... I include such settings in
a settings.py inside an application which serves both as d
SmileyChris wrote:
> The problem is, that it still gets double-escaped. Django's
> FilterExpression checks to see if the incoming object is SafeData, but
> at this stage it is a Model object - it hasn't be translated to its
> __unicode__ value yet.
As far as I understand the thing *now*, it shoul
SmileyChris wrote:
> I should have clarified that for this model, I have it's __unicode__
> method return a safe string:
>
> return mark_safe('%s (%s contacts)' %
> (escape(self.name), self.contacts_total)
Hm... I give up then :-). From my looking around the code I think it
should behave as you
Adrian Holovaty wrote:
> Without further ado, here's my list:
>
> * newforms-admin
> * queryset-refactor
> * django.newforms becomes django.forms
> * Model-level validation
> * Change django.templatetags not to use __path__ hacking
> * #3591 -- Make INSTALLED_APPS an instance, and each app an ins
Have no idea, how to post ticket on djangoproject.com. Server return
to me "500 Internal Server Error (Submission rejected as potential
spam)".
As i understand, 'name' and 'codename' columns for 'auth_permission'
table generated automatically from object class name. 'name' are
consist 'Can add+[c
Thank you.
On 3 дек, 11:37, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 03-Dec-07, at 10:17 AM, Ivan Markeyev wrote:
>
> > Have no idea, how to post ticket on djangoproject.com. Server return
> > to me "500 Internal Server Error (Submission rejected as poten
Travis Terry wrote:
> 4. P2's get_or_create() tries to create the item. One of two things
> happens:
> a. a second item is created with the same parameters if this doesn't
> violate a UNIQUE constraint
> b. the second create fails (because of a UNIQUE constraint) and
> raises an except
Travis Terry wrote:
> It's my understanding that SELECT ... FOR UPDATE only locks the rows
> that it reads (so you can be sure they can be updated or referenced
> later in the same trasaction). However, in the case of get_or_create(),
> there is no existing row
Oh... Indeed. Then this won't h
Adrian Holovaty wrote:
> The settings file syntax could look like this:
>
> INSTALLED_APPS = AppCollection(
> App('django.contrib.admin'),
> App('ellington.news'),
> )
Why not also use actual module objects here instead of strings like with
view functions in urlconfs?
-
Sandro wrote:
> Right now, django produces:
> value="P" name="language" /> Python
Not related to the discussion but for the accuracy's sake I'd like to
note that right now Django produces without for=".." at all
which this bug is about.
--~--~-~--~~~---~--~~
Y
Patryk Zawadzki wrote:
> Which is correct and desired. If not Internet Explorer, even for="..."
> and id="..." wouldn't be needed (and it's not there with current
> Django).
BTW, in current Django presence of for and id should be controlled by an
auto_id parameter of a form. However RadioSelect
Jacob Kaplan-Moss wrote:
> It's *extremely* useful to be able to inspect settings files *without*
> triggering imports of all INSTALLED_APPS
Got it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers
Malcolm Tredinnick wrote:
> Okay, I think my brain just melted trying to follow the various
> sub-problems mentioned here. Can somebody make sure that whatever issues
> are brought up here are turned into tickets,
I'll try to clarify since it looks that I'm responsible for most of the
confusion.
James Bennett wrote:
> This means the default implementation can happily use
> django.contrib.auth and the existing is_staff flag and permission
> system, but that using something else is as easy as subclassing and
> overriding the right methods. And with a little refactoring to remove
> the direc
Joseph Kocherhans wrote:
> I don't want to speak for James, but that's how I see it.
Then this is great!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email t
David Cramer wrote:
> With the latest trunk I actually had 4 unit test failures -- maybe my
> setup is screwed. http://www.pastethat.com/VulU5
>
> These happened either way though, the same errors.
David, looks like your test DB is not created in utf-8 charset. Try
these two settings:
http://w
I suggest using python 2.5 standard library functools.partial when it
is available instead of django.utils.functional.curry. This functions
are technically the same with the exception that partial is written in
C and is about 2 times faster.
Just replace every:
from django.utils.functional import
401 - 500 of 569 matches
Mail list logo
