tests are really
read only ? If yes, I would be interested. If no, then (sorry to say
this), but the "read-only" part is only wishful thinking.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
n 32-bit/64-bit Python, i'm not sure there
are even any or we would get a report on that, wouldn't we ?).
I think it's important for the Django core team to voice their opinion
on this matter in python-dev.
Thank you!,
Łukasz Rekucki
--
You received this message because you are subscribed to th
this list, we have the right to
> discuss things which feels on topic with this list without being
> discriminated for no reasons.
>
You're not discriminated - everyone is treated the same way here and
judged only by their actions. By disobeying the rules of this list,
you're disrespectin
y from the database,
> with django itself providing some version of the Unicode collation
> algorithm:
>
> http://unicode.org/reports/tr10/
>
> This might hook into django's internationalization and localization
> features, and/or be accessible at a lower level, e.g., with a keywo
llate.html
[2]: SQLite doesn't support UCA by default, but lets you define any
collation:
http://docs.python.org/library/sqlite3.html#sqlite3.Connection.create_collation
[3]: http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch9sql.htm#i1006311
--
Łukasz Rekucki
--
You received t
2012/2/2 Łukasz Rekucki <lreku...@gmail.com>:
> On 2 February 2012 03:34, Anssi Kääriäinen <anssi.kaariai...@thl.fi> wrote:
>>
>> Now, my proposed solution would be to have some way of doing:
>> SELECT name, ...
>> FROM authors
>> ORDER BY name collate
.dajaxproject.com/ does exactly that.
What I would like to see instead is providing HTML5 attributes for
standard fields and
making it easier to add ones to custom ones. Some simple to implement
ones are: "required", min/max for number fields, max_length for a
textarea. Regular expr
GSOC), so that we can fix things like that.
So the general solution would be doing that ;). Just changing it,
helps new installations, but breaks old ones.
PS. Since Facebook started generating fake addresses, 75 characters on
the email field is also no good, so matching that doesn't solve
any
or similar features... sometimes "similar" is not enough. I'm
not a regular Bitbucket user, so I maybe just didn't discover that,
but how can you add per line comments in patches on Bitbucket ?
Without that, code reviews for non-trivial patches is a real PITA.
--
Łukasz Rekucki
--
You rece
hink a few times more before
sending that. Also, it wasn't my intention to "bash bitbucket" or
anything like that so sorry for that too.
I'll just shut up now and let the silence hide this thread.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Gr
that. The
super() problem actually makes a great Python puzzle so it's easy to
remember the dangers after solving it ;)
[1]: https://code.djangoproject.com/ticket/14512
[2]:
https://github.com/lqc/django/blob/cbvdecoration_ticket14512/tests/regressiontests/utils/decorators.py#L120
--
Łukasz Reku
lready, so an extra label shouldn't
surprise you.
[1]:
https://docs.djangoproject.com/en/1.3/ref/forms/fields/#django.forms.ModelChoiceField.empty_label
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, se
n 822.943s
FAILED (failures=39, errors=1, skipped=109, expected failures=2)
It's a bare install, so there may be more within the skipped ones.
Most look harmless and only needs updating the testcases, so it
doesn't require specific order.
Created ticket https://code.djangoproject.com/ticket/17758 -
If it was such a big issue, that LOTS
would either spam this list or fork Django long ago.
With a clear BDFL veto, it's better to search for an alternate
solution then waste everyone's energy on a bikeshed.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the G
On 24 February 2012 17:29, Łukasz Rekucki <lreku...@gmail.com> wrote:
> With all the voting and aesthetic discussion, maybe let's get back to
> technical details:
>
> On 24 February 2012 05:18, colinta <coli...@gmail.com> wrote:
>> 1) It's an easy fix.
>
> Mayb
meone actually provides a patch with no
performance hit. Really, we know people fork Django for their private
use. If this is such a big deal, we should have at least one person
using this in production for a while now and have an excellent quality
patch to show.
--
Łukasz Rekucki
--
You received this mes
ters to the {% with
%} and/or make an include with changed context. A year after, It turns
out the use cases aren't so rare anymore.
Now, if your blocktrans contains 10 variables and all have more then 2
dots in them, then maybe there are other reasons that it looks ugly
then lack of multi-lin
at
> means a large update (if not a reboot) of the py3k branch.
>
Why would you want to do that, when the py3k is already working with
unicode_literals ? That's a step backwards.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Djan
del can have an UUIDField as it's pk instead of a
sequential integer).
For making assertions about QuerySets, there already is
assertQuerysetEqual(), so -1 on adding __cmp__ to Model.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django de
quot;we
don't want to have to fix this again" thing.
[1]: http://tools.ietf.org/html/rfc5321#section-4.5.3.1.1
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
On 9 March 2012 21:10, Tom Evans <tevans...@googlemail.com> wrote:
> 2012/3/9 Łukasz Rekucki <lreku...@gmail.com>:
>> On 9 March 2012 17:46, Tom Evans <tevans...@googlemail.com> wrote:
>>>
>>> Lets look at one isolated aspect. The User email field i
ration + presentation)? This is what most REST
frameworks do. First you serialize the objects into Python native
types, then render it to any format.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
/commit/84dc450ec861e34de068fde891537f0481342ef7
--
Łukasz Rekucki
--
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.
To unsubscribe from this group, send email
On 22 March 2012 13:38, Ramiro Morales <cra...@gmail.com> wrote:
> 2012/3/22 Łukasz Rekucki <lreku...@gmail.com>:
>
> Maybe we should split these problem reports in their own tickets?
>
I can do it later today. There probably should be 3 tickets: the ORM
bug, th
On 22 March 2012 16:54, Aymeric Augustin
<aymeric.augus...@polytechnique.org> wrote:
> Le 22 mars 2012 13:22, Łukasz Rekucki <lreku...@gmail.com> a écrit :
>> If the whole patch can't be merged, lets at least fix that bug[2]. Is
>> there any work I can do to make i
:)
--
Łukasz Rekucki
--
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.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
gt; Well, it is the kind of magic that gets you burned at the stake for
> witchcraft :-)
>
That only means it must be effective ;)
As for the GitHub migration, I noticed this little repo[1]. Are you
collecting only major contributors or is it open for pull requests ?
[1]: https://github
On 27 March 2012 03:01, Alex Gaynor <alex.gay...@gmail.com> wrote:
>
>
> On Mon, Mar 26, 2012 at 9:00 PM, Łukasz Rekucki <lreku...@gmail.com> wrote:
>>
>> On 27 March 2012 02:44, Reinout van Rees <rein...@vanrees.org> wrote:
>> > On 26-03-12 18:13, F
want to enable
passing context variables as view names? Did you notice that almost
everywhere in the template language literal strings are quoted?
Technical arguments usualy work better then calling things "stupid".
--
Łukasz Rekucki
--
You received this message because you are su
, not yet. There's a features/py3k branch, but I'm not sure if
it's up to date with Tarek's bitbucket repo. My bet is that py3k merge
will happen after the GitHub migration which everyone seems to be busy
with ;)
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Goog
On 27 March 2012 14:44, Łukasz Rekucki <lreku...@gmail.com> wrote:
> On 27 March 2012 14:22, Shaggy <kfu...@gmail.com> wrote:
>>
>> and btw. is there repo for developing 1.5 with python3 support?
>>
>
> AFAIK, not yet. There's a features/py3k branch
"django.utils.simplejson" in 1.5 and remove it 1.6
3) Replace the code with anyjson, so it does something useful:
http://pypi.python.org/pypi/anyjson
What do you think ?
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django de
it, so you can decide
about it at the project level.
--
Łukasz Rekucki
--
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.
To unsubscribe from this group, send
der]
>>
I' sure you meant:
def greet(self):
return {self.MALE: 'Hi, boy', self.FEMALE: 'Hi, girl.'}[self.gender]
Unless you defined MALE/FEMALE as globals too :) Otherwise you'll get
a NameError.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Grou
re.
>
That's not how it works. Code that executes when creating a new class
does not define a lexical scope. There is no such thing as "class
scope". Try it yourself:
http://ideone.com/xbr0q
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
e, it means it's a non-empty sequence that's not a subclass
of dict, right? Did you manage to track what type of value it is?
There must be a bug somewhere else too.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" g
ossibly want to have is a way to create extra
constraints on the tags, but as a matter of fact, the current Trac
instance doesn't do that! (you can have an issue with "tests needed"
but without "patch needs improvement").
--
Łukasz Rekucki
--
You received this message because
On 25 April 2012 17:32, Jacob Kaplan-Moss <ja...@jacobian.org> wrote:
> OK, done! Thanks for your patience.
>
> Jacob
Am I supposed to see the "Admin" tab or did I just haven't noticed it before?
--
Łukasz Rekucki
--
You received this message because you are subscr
ts", etc. to do triaging.
Now that I know I have access to it, I'm scared I'll break something
be accident ;)
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dja
h (depends on DB):
qs = User.objects.all()
user = None if not qs else qs[0]
F) Use the iterator protocol
user = next(iter(User.objects.all()), None) # you can add LIMIT or
not, see Alex's comment
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Go
On 10 August 2012 18:56, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote:
> I think Option 2 is better, for the reasons you state.
>
How about wrapping those 3 lines of code into a class decorator
(preferably named more explicit then StrAndUnicode) ? That would be at
least a little DRY.
t; models.
I'm pretty sure everyone with South will still be pretty unhappy about
updating all their migration files.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-d
on to an unauthorized session in
hope it will become authorized again can be anything but a bug.
Regards,
Łukasz Rekucki
--
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.
To u
and post if I find anything interesting.
[1]: https://gist.github.com/3875701
--
Łukasz Rekucki
--
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.
To u
l into 30 char limit.
PS. I'm pretty sure you want to have:
db_table='"mnoworka"."defined_daily_dose"'
If the name is already quoted, Django won't alter it. OTOH, see issue
#18514 (which shouldn't be a problem if you have managed=False).
[1]: https://code.djangopr
rs to make them part of
> the name. But -- save length issues -- the ploy succeeds:
It seems none of the backends implement any form of quote escaping in
their quote_name() methods. But is it actually possible to have a
table in Oracle with a name containing a double quote?
--
Łukasz Re
name\"'
>
> This only works for unmanaged models. For managed models it results in an
> error when it tries to create the sequence and trigger using syncdb.
Why all the slashes ? Unless you specify r'' or make them double, they
don't do anything!
>>> '\"' == '"'
Tru
Hi,
Isn't this https://code.djangoproject.com/ticket/19235 ?
Regards,
Łukasz Rekucki
--
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.
To unsubscribe from
to join
the thread as they feel their views are represented.
Personally, I don't see any big advantage of having a yet another init
method, but OTOH I already replaced Django's view hierarchy with my
own, as I needed a more advanced data flow.
--
Łukasz Rekucki
--
You received this m
e case.
After all, the %-coded bytes can be some binary data that's not possible to
reasonably decode with any charset.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-dev
On 1 March 2013 22:38, Alon Nisser wrote:
> at least from my windows exprience with Django (yes, I know this isn't a
> common use case, but still) the current django-admin.py and manage.py do
> need python preface to run right (while inside a virtualenv)
I'm not 100% sure
;needsinfo" is almost identical to
"cannot reproduce" (aka "worksforme") and I can't think of a reason to keep
such a bug open.
Of course, there are people who will take everything personal. Even if it's
getting your ticket closed by a stranger on a public bug tracker.
--
Łukas
system/tracker I sometimes
see: -1 votes (setting WONTFIX is effectively a veto just like -1) without
giving conditions for improvement to at least -0. Having a clear path of
action (even a one that involves a lot of work) to convince the person
vetoing your proposal is always better then just &qu
On 15 May 2013 20:29, Shai Berger wrote:
> On Wednesday 15 May 2013, ptone wrote:
> > On Wednesday, May 15, 2013 10:31:36 AM UTC-7, Daniele Procida wrote:
> > > On Wed, May 15, 2013, Shai Berger
> > > >
> > > >Will there be an effective way to do this
possible and some major pitfalls. There
is no gain in *disallowing* this. Personally I wouldn't use this as
it's counter-intuitive and works in exact opposite to Python's import
mechanism which by default does an absolute search (since 3.x).
Regards,
Łukasz Rekucki
--
You received this message because
a PR for the old one ?
--
Łukasz Rekucki
--
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.co
.
It's not a bug. As per documentation:
If you provide content_type (e.g. text/xml for an XML payload),
the contents of data will be sent *as-is* in the POST request, using
content_type in the HTTP Content-Type header.
This means that you're responsible for proper encoding the data
parameter i
--
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this grou
o the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com>
&g
erring to is here:
>
> http://code.djangoproject.com/browser/django/trunk/django/utils/text.py#L158
>
> Thanks!
>
> - Gabriel
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send emai
because you are subscribed to the Google Groups
>> "Django developers" group.
>> To post to this group, send email to django-develop...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-developers+unsubscr...@googlegroups.com.
>&
2to3 already handles most of this
stuff, so it's the right way to go. At least now. What I really wanted
to say, is that using 2to3 on a 2.6 code that uses (for example)
__future__.unicode_literals is more likely to succed.
>
> -Gul
>
--
Łukasz Rekucki
--
You received this mes
r...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-developers?hl=en.
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> http://www.apgwoz.com
>>
>> --
>> Y
lex
>
> --
> "I disapprove of what you say, but I will defend to the death your
> right to say it." -- Voltaire
> "The people's good is the highest law." -- Cicero
> "Code can always be simpler than you think, but never as simple as you
> want" -- M
Hi, if i'm wrong, please ignore this post ;)
2010/1/21 Jerome Leclanche :
> A decimal backend was a lot worse than a bigint backend on that matter
> (slower, made a lot less sense as well).
>
> Keep in mind, TIME fields are for storing time, not for storing
> durations. For
mns."""
After seeing all this mess, i'm +1 on using BigIntField. Good work.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.c
nt() function have to return an integer value without
> any exceptions.
I disagree. If you're standing in an empty room and someone asks you
"How many apples inside the yellow basket do you see?", you anwser
"What basket, there is nothing here!", not 0.
Regards,
Łuka
the include and restore foo, bar to old values
(if any). Using a clean context instead is a bit non-obvious to me.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-devel
p://code.djangoproject.com/ticket/7817
I'm willing to improve the existing patch, so I assigned it to myself.
The ticket is marked as DDN, so I guess this thread is a request to
accept it.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Dja
nner provide a class which
will be then extended by django.test.TestCase. Just thinking aloud.
Generally, +10 for doing this.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
quot;environment" is in method parameters or
request (is this right?).
Anyway, I think this discussion in on a wrong track. From a Django
user POV, I really don't care how it's implemented. I'm far more
concerned with the API that generic views will provide.
--
Łukasz Rekucki
--
You received
in
case of invalid(valid?) data ? Can you give a more complete example ?
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from thi
y want to return
to the user. Relevant ticket:
http://code.djangoproject.com/ticket/5515. Also, it's not really
documented anywhere and because it's outside of http module, it's hard
to find on your own.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Goog
the PermissionDenied handler) get is not very useful to
the end user. Showing a big "Permission Denied" with nothing else on
the screen makes my users feel like they broken something. Without an
option to customize the response content, it's not very useful (which
is the point of ticket #5
Hi,
I was wondering if I could get some feedback on this ticket. It was
recently briefly discussed here:
http://groups.google.com/group/django-developers/browse_thread/thread/fb8a4a0eb4e1d35e.
It has a patch with tests and probably not-so-good docs, but still
needs a decision.
I'll gladly
On 9 August 2010 22:48, Paul McMillan wrote:
> I agree with the person who closed the ticket again, since this should
> have been discussed on the mailing list prior to re-opening it.
That would be me ;)
>
> That said, I'm strongly +1 on this issue. I've had to write
>
Hi,
Since revision 13588, tests fail on trunk without Docutils installed.
This was also reported by Paul:
http://code.djangoproject.com/ticket/14123 and currently makes all the
buildbots on Hudson fail, so I would like to bring your attention to
it
Regards,
Łukasz Rekucki
--
You received
A_withB::
{% extends "A" %}
{% include "B" %}
If yes, then I would support this, because it makes templates more
maintainable. You avoid both the include and "A_withB" type templates.
--
Łukasz Rekucki
--
You received this message because you are su
ut it wasn't clear to me if you meant the spider-bot that
indexes your page. The main issue here is that parsing the date is
probably much slower then a simple compare. We don't want to trade
speed for no real-life gain.
--
Łukasz Rekucki
--
You received this message because you are subscribed t
kwargs):
return type(view_cls.__name__, (view_cls,), kwargs)
# in urls.py:
(r'^somepath', with_args(MyView, option=False)),
# or even
(r'^somepath', MyView.with(option=False)),
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
&qu
On 2 October 2010 12:32, Russell Keith-Magee <russ...@keith-magee.com> wrote:
> 2010/10/2 Łukasz Rekucki <lreku...@gmail.com>:
>> On 2 October 2010 10:34, Russell Keith-Magee <russ...@keith-magee.com> wrote:
>>>
>>> Another option wou
On 3 October 2010 04:44, Russell Keith-Magee <russ...@keith-magee.com> wrote:
> 2010/10/3 Łukasz Rekucki <lreku...@gmail.com>:
>> On 2 October 2010 12:32, Russell Keith-Magee <russ...@keith-magee.com> wrote:
>>> 2010/10/2 Łukasz Rekucki <lreku...@gmail.com&
likely to do.
+1 on having a compare table between other frameworks.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe f
-1_3-release-schedule/
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubs
yes this is the best solution raised so far.
>
The only problem is decorators: You can't just simply apply
login_required() to the class or the dispatch() method. Otherwise, I
like this approach.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Djang
l to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
--
Łukasz Rekucki
--
You receiv
o_template
Use a TemplateView with get_response() overriden. The patch on the
ticket adds a response class as a parameter. Should we add a similar
to TemplateView ?
#13953: Generic CRUD views: support for callable in post_ACTION_redirect
There are no post_ACTION_redirect parameters anymore, can
in Python 2.4[1].
Possible solutions I can see right now:
* revert the logging patch (that would be quite bad)
* try to do some ugly monkey patching to the logging module
* drop Python 2.4 support
Opinions ?
[1]: http://docs.python.org/library/logging.html#logging.debug
--
Łukasz Rekuck
implify a bit create_user()
> by just calling set_password() for all cases. No need to test password
> inside this function anymore.
>
> - basic.py tests are now unittests and not doctests
Good work :)
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google
I just noticed we have 2 new Core Developers: Alex Gaynor and Andrew
Godwin and a new Admin Specialist Simon Meers.
Just wanted to say: Congratulations guys and keep up the good work! :)
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"D
On 14 October 2010 18:19, Russell Keith-Magee wrote:
>
> The following things are still needed:
>
> * An audit of create/update views.
> * An audit of date views.
I was planning on hacking onto this on today/tomorrow. Also see below.
> * Documentation, including
>
ttp://blip.tv/file/4109272
[2]: http://blip.tv/file/4108781
[3]: http://bitbucket.org/freakboy3742/django
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop
is on a per-view basis with just a mixin. I could catch
Http404 exception, but it won't trigger middleware handling as it
normally does. Any suggestions ?
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To pos
s thread, I proposed a similar
thing ;) but instead of a whole descriptor, you can just subclass the
classmethod decorator:
class classonlymethod(classmethod):
def __get__(self, instance, owner):
if instance is not None:
raise AttributeError("This method is availble
se, but i'm kinda half
asleep at 3 am.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-de
l work done this time. My other targets would be popular 3rd party
applications. If you know of any that have some really complicated
views, I think trying to rewrite them to CBV would be a good test of
the API, so send me a link :)
--
Łukasz Rekucki
--
You received this message because you are sub
at would
> lend itself to subclassing.
>
> Plus, some preliminary work now might provide a good base when we *do*
> work out what changes need to be made to auth views.
>
Yes, this is mostly an academic exercise, so I'll take a look at
contrib.comments too.
--
Łukasz Rekucki
so add something like a "boundary" argument just in case
someone will want to escape "{% endverbatim %}":
{% verbatim boundary="my_random_string" %}{% endverbatim %}{%
endverbatim_my_random_string %}
--
Łukasz Rekucki
--
You received this message because you are
e that practice,
> but that pattern might be hard to encourage since class-decoration is
> less obvious (and certainly much less well established in the Django
> code base) than method decoration.
OTOH, it'a annoying to have to write an dispatch() method with a super
inside (which effectively doe
t; To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
-
1 - 100 of 186 matches
Mail list logo