.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/52e4d514-fe86-4867-a640-3484939dd882%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
--
Łukasz Rekucki
--
You received this message because you are sub
stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
>
0googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To
ngo-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/9b713601-589d-4685-ab85-93f4fa8d9950%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
--
Łukasz Rekucki
--
You received this message
795467-24c7-4a61-af78-1a5b1a16299d%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
--
Ł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
On 2 July 2014 21:14, Aymeric Augustin
<aymeric.augus...@polytechnique.org> wrote:
> 2014-07-02 15:36 GMT+02:00 Łukasz Rekucki <lreku...@gmail.com>:
>
>> It doesn't just alter it, but makes it conform to HTTP standard.
>
>
> As usual, given a different set of exp
On 2 July 2014 15:42, Florian Apolloner <f.apollo...@gmail.com> wrote:
> On Wednesday, July 2, 2014 3:36:22 PM UTC+2, Łukasz Rekucki wrote:
>>
>> It doesn't just alter it, but makes it conform to HTTP standard. While
>> most browsers will accept relative urls,
On Jul 2, 2014 2:09 PM, "Aymeric Augustin" <
aymeric.augus...@polytechnique.org> wrote:
>
> I find it wrong to alter the response created by the developer
unconditionally and not provide any escape hatch.
It doesn't just alter it, but makes it conform to HTTP standard. While most
browsers will
evelopers/1d33bd04-a509-4c34-8bfe-2e4df31a3add%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from thi
t;
>
> Gregor
>
>
> 2014-04-10 11:41 GMT+02:00 Tino de Bruijn <tin...@gmail.com>:
>
>> Wouldn't this be easier?:
>>
>> {'required': "", 'name': 'fieldname'} => > />
>>
>> {% for name, value in attrs.items %} {{ name }}{%
On 6 April 2014 17:24, Andrew Pashkin wrote:
> Some Pytest advocacy:
> 1) Pytest has convenient tests collection options - you can just specify
> folder to run all tests in it. It is also possible to filter tests by regex,
> and select specific ones.
Sounds good, but
O, It would be better for everyone if ugettext_lazy() and friends
fail immediately when given anything other then text (unicode on
Python 2, str on Python 3), but it's probably too late for that now.
At least until Python 2 support is dropped completely.
--
Łukasz Rekucki
--
You received thi
nywhere?
AFAIK, this is already the case as long as the wrapped cursor does it.
[1]: https://bugs.pypy.org/issue736
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and sto
.
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
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
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
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
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
;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
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
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
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
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
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
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
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
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
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
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 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.
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
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
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
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
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
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
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
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
"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
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
, 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
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
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
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
:)
--
Ł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
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
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
/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
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
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
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-
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
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
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
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
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
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
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 -
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
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
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
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
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
.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
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
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
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
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
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
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
flag doesn't solve the memcached issue, right? IMHO, it only
adds to the false impression that you can have any control on what
gets flushed by memcached.
I also agree with Aymeric that not clearing cache state is a bug.
Having a flag to fix/restore buggy behaviour seems weird.
--
Łukasz Reku
Z"
wording (which implies it may be removed in any (Y+m).(Z+1+n) n,m>=0
version).
--
Ł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.c
don't have any failing tests to look at right
> now. YAY! :)
> Matt.
My Python 2.7 says:
self.assertEqual(result['active'], 2)
AssertionError: 1 != 2
So, no. The message in Python is order agnostic.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the
t;? Where's the consistency in that?
>
My guess is that the choice is somehow connected to Yoda conditions,
where you actually write:
if(5 == x) { ... }
to avoid assigning 5 to x by mistake. If you write all your conditions
like that, then the assert order makes sense.
But Python thankfully doesn
ts.create()
> u = User.objects.create_user('roald', 'downa...@gmail.com', 'password')
>
>
> # these things I can't do:
> m.users.add(u)
> m.users.add(u, comment='Blablabla')
>
> Cheers, Roald
>
I'm 100% sure there's *at least one* ticket for this. You jus
On 16 September 2011 10:17, Roald de Vries <downa...@gmail.com> wrote:
> On Sep 16, 2011, at 12:11 AM, Łukasz Rekucki wrote:
>>
>> As the ticket creator I feel obligated to reply :)
>
> Me (as the poster of the latest patch) too :)
Nice to meet you.
>
>> Think
osal on this list before introducing CBV. It
didn't gain much love.
--
Ł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
rs+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this grou
2011/9/16 Łukasz Rekucki <lreku...@gmail.com>:
> Hi,
>> I believe, however, I've figured out a different technique to make
>> this work: don't try to detect bound versus unbound methods, but
>> instead look for the HttpRequest object. It'll either be args[0] if
>>
to Django?
>
It would be great to have that meta-decorator, so everyone else could
upgrade their decorators just by decorating them.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, se
it. There is also the problem of signed int.
PS. Cross-posting like this to django-users and django-developers is
probably not a good idea as people on django-users will send emails
here by accident.
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google Groups
&quo
None) == False, so it wouldn't be backwards compatible.
--
Ł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 em
that ? How does your application help me handle
client-side translations ?
--
Ł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 unsubscr
modified since it relies on Python's gettext module to load the
> translations.
By 'locale interface' I actually meant the CLDR. Django's
"localflavor/**/formats.py" mostly duplicates information provided by
Babel.
--
Łukasz Rekucki
--
You received this message because you are sub
. Whether we do this in the release branch or in
> trunk I don't care.
Following this metaphor, it's autumn, it's raining and the materials
for a new roof won't be coming until late winter, so covering the
bikes with a some tilt, so they don't rust might be a good idea :P
**You ment
ng existing bug
and doesn't touch any public APIs. I tested the patch on my code with
good results.
--
Ł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
f you're
on python >= 2.7, try running "python -W manage.py runserver".
--
Ł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.
T
t is tricky. I need help finding diabolical
> test cases for my lexer (https://bitbucket.org/ned/jslex). Anyone care to
> come up with some Javascript source that it can't properly find the regex
> literals in?
I'll give it a spin on my code :) Thanks for doing this!
--
Łukasz Rekuc
()[1], but I'm not
sure how you can make a Query object with "self.where" attribute that
would evaluate to False.
[1]:
http://code.djangoproject.com/browser/django/trunk/django/db/models/sql/query.py#L478
--
Łukasz Rekucki
--
You received this message because you are subs
pp on uWSGI, not compare it
against other solutions. You also mention some features, but never
show how to enable/use them which is confusing.
PS. Do you think having a `runuwsgi` command similar to `runfcgi`
would be useful ?
--
Łukasz Rekucki
--
You received this message because you are subscr
this work. You
> may be removed again, but with all the great triaging work you've been
> doing I imagine you ought to stay there.
Thanks. I noticed the email after about 20 tickets, so sorry for all
that emails.
--
Łukasz Rekucki
--
You received this message because you are sub
On 1 April 2011 00:58, Karen Tracey <kmtra...@gmail.com> wrote:
> 2011/3/31 Łukasz Rekucki <lreku...@gmail.com>
>>
>> I just started updating my custom TestSuiteRunner to Django 1.3 and it
>> seems that reorder_suite() is broken. At least I think it is, becaus
and rename to flatten_suite() ?
--
Ł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
the doctype and input elements' types.
--
Ł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-de
TA.
>
-1 on guessing anything, especially something that doesn't change.
Also, a fairly common configuration is Apache behind an nginx proxy.
In this setup, I want nginx will be the one serving static files, not
Apache.
--
Łukasz Rekucki
--
You received this message because you are subscri
proposing. Do you want to change the
default project template or the docs ?
--
Ł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
les didn't had an option to include
dynamically generated content.
--
Ł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 uns
are
defined in the same class before the CompositeField:
http://ideone.com/LPNzS
--
Ł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 gr
ib.admin.AdminSite.login_form
PS. If you're really concerned about messages from admin you should be
really outraged by _("Your e-mail address is not your username. Try
'%s' instead.") % user.username
--
Łukasz Rekucki
--
You received this message because you are subscribed to the Google
trator of
the system. Ordinary users shouldn't even know that the admin
interface exists.
I can imagine a confused staff memeber, that didn't got his account
activated properly, but this can be fixed by putting extra help on
your admin's login page, imho.
--
Łukasz Rekucki
--
You received this m
1 - 100 of 186 matches
Mail list logo