On Fri, Aug 14, 2009 at 3:13 AM, ccahoon wrote:
> One bit of advice I am looking for is what people's opinions are on
> the use of isinstance versus hasattr to determine functionality. I am
> personally partial to hasattr, because it covers subclasses, but I do
> not know what the community tends
On Mon, Aug 17, 2009 at 10:57 AM, Jonas Obrist wrote:
> Thanks for your opinion on this, didn't know django had this feature
> once. But I just can't get it out of my head that there's gotta be a
> better solution than this profile-extending... It just seems ridiculous
> to me that half of the use
On Mon, Aug 17, 2009 at 11:35 AM, James Bennett wrote:
> def __getattr(self, name):
> if hasattr(self.user, name):
> return getattr(self.user, name)
> else:
> return getattr(self.profile, name)
And for some reason gmail ate the trailing dou
Please don't feed the troll.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
Due to an issue with a misapplied patch in the recent Django 0.96.4
security release, tonight the Django project has issued Django 0.96.5.
Full information is available here:
http://www.djangoproject.com/weblog/2009/aug/19/bugfix/
Please note that this will be the *final* release in the Django
So, the USStateField in contrib.localflavor got neutered a while back,
removing a number of items from its choices list which -- while not
actually US states -- are valid postal codes which the US Postal
Service recognizes and considers as "US" addresses. When this
happened, Django lost useful fun
On Fri, Aug 28, 2009 at 10:09 AM, Yuri Baburov wrote:
> but could anyone please tell me what's planned time frame for GSoC
> projects integration into Django if there's any.
There is no timeline I'm aware of. And, personally, I don't think
there's a need for any sort of special process: these are
On Fri, Sep 4, 2009 at 2:21 PM, andybak wrote:
> 1. I think worrying about projects vs. apps is a red-herring. We are
> talking about a way to configure an admin app. There might be several
> of these on a 'site/project/whatever'
Since this all seems to be specific to particular instances of
Admi
On Fri, Sep 11, 2009 at 4:36 PM, Jared Kuolt wrote:
> Please correct me if my interpretation is wrong (for example, is there
> a show-stopper about which the community is not aware?).
Personally, my opinion is that there are good bridges from all the
popular DVCS tools to Subversion, and that ch
On Fri, Sep 11, 2009 at 5:10 PM, James Bennett wrote:
> Personally, my opinion is that there are good bridges from all the
> popular DVCS tools to Subversion, and that choice of DVCS is such a
> flamewar topic right now that it's best to stick with the lowest
> common denomina
On Mon, Sep 14, 2009 at 12:45 PM, Patrick J McNerthney
wrote:
> I am new to Django and am deep in the middle of my first major project
> using Django. When I encountered get_absolute_url, my reaction was,
> "What were they thinking!". Why does the model have any knowledge about
> it's presentat
On Mon, Sep 14, 2009 at 7:10 PM, Patrick J McNerthney
wrote:
> The objective is not to completely separate the two. URLs are roughly
> the "Controller" in the MVC world, and need to know about both the
> models and the views. It is the "glue" that binds the two together.
> URLs already do know
On Tue, Sep 22, 2009 at 6:57 AM, Simon Willison wrote:
> Yeah, I'd like a builtin shortcut like that - used like this:
> render(request, 'template_name.html', {'foo':bar })
> The biggest problem, for me, is finding a decent name - since
> 'render_to_response' is already taken. Maybe something a
On Mon, Sep 21, 2009 at 9:04 PM, Luke Plant wrote:
> I've committed my change [1], and also replaced _CheckLogin with my method [2]
> (it was essentially the same method, just generalised).
The decorator_from_middleware change appears to have broken
cache_page; I'm now getting "AttributeError: '
On Tue, Sep 22, 2009 at 4:07 PM, Luke Plant wrote:
> Bummer, I tried hard not to break it - I added backwards
> compatibility tests for the basic different uses. Could you produce
> a test case?
So, I've worked out what the problem is.
Previously either of these worked:
cache_page(timeout, vi
On Sat, Oct 3, 2009 at 1:58 PM, Thierry wrote:
> I know this is not a problem for most users. But when working with
> complex projects or projects requiring some performance optimization
> django orm doesn't suffice. Its a pity to see strong development on
> django orm, while at the same time the
On Fri, Oct 2, 2009 at 9:37 AM, Russell Keith-Magee
wrote:
> Django's ORM is designed to make the simple cases really simple, but
> once you move beyond the basics, you really should be looking to use
> raw SQL.
Indeed. I look at raw() really as "I know *exactly* the query I want
to run, get the
Today the Django project is issuing a set of releases to remedy a security
issue. This issue was disclosed publicly by a third party on a high-traffic
mailing list, and attempts have been made to exploit it against live Django
installations; as such, we are bypassing our normal policy for security
In light of yesterday's security issue, I'd like to propose that we
significantly dumb down the regex Django uses to validate email
addresses.
Currently, the regex we use covers many common cases, but comes
nowhere near covering the entire spectrum of addresses allowed by the
RFC; several tickets
On Fri, Oct 16, 2009 at 3:01 PM, Michael P. Jung wrote:
> So I wonder what would be wrong with putting the request object in a
> threading.local object. It would neither kill performance nor cause a
> poor architecture by itself.
What's wrong, to me, is that it's a code smell which conflicts wit
On Sat, Oct 17, 2009 at 10:29 AM, Leaf wrote:
> Sorry to propose this right up against the voting deadline for 1.2
> features, but it's one of the things that has always bugged me about
> Django and I would really like to see this in 1.2.
-1.
Replacing regular expressions with... well, what loo
On Tue, Oct 20, 2009 at 8:44 AM, Yuri Baburov wrote:
> Moreover, new contributors are considered the least important
> creatures in the world!!!
As they say on Wikipedia, "[citation needed]". This list grows with
every new release:
http://code.djangoproject.com/browser/django/trunk/AUTHORS#L27
On Wed, Oct 21, 2009 at 7:36 PM, Russell Keith-Magee
wrote:
> Let me tell you a store about three people named Everybody, Anybody,
> Somebody and Nobody.
Four! The four people in this story are...
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---
On Thu, Oct 22, 2009 at 10:27 AM, Phillip Temple
wrote:
> django-registration - rewritten to have pluggable work flow, this is a
> fundamental feature of so many web sites
I'm -1 on adding django-registration to contrib.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of c
On Thu, Oct 22, 2009 at 11:20 PM, Vinay Sajip wrote:
> How about using BitBucket? Does it have the same limitation? I see
> there's already a Django mirror there:
If anyone's interested, I can see about maintaining a copy pulling
from any branches people are maintaining on bitbucket.
(and with
On Fri, Oct 23, 2009 at 5:12 AM, rjc wrote:
> The only reason I will migrate to 1.2 is if you include schema
> migration. It is that important for us (we have a lot of production
> code out). Anyway, why did we pick south instead of django-evolution ?
> I'm +1 (+1 +1) for any db schema migration.
On Sun, Oct 25, 2009 at 8:30 PM, Russell Keith-Magee
wrote:
> A wiki page doesn't really solve the problem either. If you make it an
> exclusive list, someone has to decide who is on the list and who
> isn't. If you make it a comprehensive list, a wiki page will very
> rapidly become unusable due
On Mon, Oct 26, 2009 at 6:53 AM, kugutsumen wrote:
> Support for non-relational databases (AppEngine, #10192) +1
Repeating once again: the voting's over and done with. The proposals
have been assigned their priorities. Time to move on.
--
"Bureaucrat Conrad, you are technically correct -- th
On Fri, Nov 27, 2009 at 6:07 AM, noel wrote:
> I really love this application Reinteract. Its an enhancement to
> Python Interactive Shell. And it would be lovely if I can use
> Reinteract with manage.py shell.
Before submitting feature requests, please check the release cycle;
Django 1.2's featu
On Fri, Dec 4, 2009 at 2:42 PM, Yuri Baburov wrote:
> Like, calling current Manager a DefaultManager, and making "Manager =
> load(settings.MODEL_MANAGER) or DefaultManager". Or
> Manager.get_queryset calling customizable method. Any.
If a suggestion like this is going to be implemented, I'd pref
On Mon, Dec 7, 2009 at 11:05 AM, Adrian Holovaty wrote:
> My preference is (slightly) for class-based, because it's (slightly)
> less magic. I think we should try to avoid requiring people to
> remember what to name things.
I like this as well, albeit for a slightly different reason: asking
you t
On Wed, Dec 9, 2009 at 8:10 PM, Karen Tracey wrote:
> Yes, it's easy to do yourself. But to me this seems like an oddly basic
> type to be missing from the base, with enough users potentially wanting it
> that it deserves to be officially supported. So I'd be willing to spend
> some time on it,
On Tue, Dec 15, 2009 at 4:23 PM, Luke Plant wrote:
> We need a section in our release notes about dropping support for
> Python 2.3. I was trying to write it, and I wanted to say "as
> announced in such & such a place", but I can't actually find that
> place. I know the decision was made somehow.
On Tue, Dec 15, 2009 at 9:15 PM, DULMANDAKH Sukhbaatar
wrote:
> Please note that python 2.4 is default in RHEL5.
I'm aware of that, and concerns about RHEL were noted when I
originally proposed the roadmap. But that's Red Hat's problem; if they
want to keep shipping ancient versions of Python, th
I've previously brought up some issues with the removal of certain
options from the choices on localflavor's USStateField[1] as a result
of ticket #8425[2] and, with feature freeze for 1.2 approaching and
perhaps more time soon to be available for such things, I'd like to
call attention to it again
Technically, the major feature freeze for Django 1.2 was to have
happened sometime yesterday, US Central time. As of this moment, we're
not actually frozen, but will be as soon as I hear status reports on
the following (high-priority features which have not yet listed a
commit on the 1.2 features p
Since it appears there are some people who have code ready but have
time constraints due to holidays, I'm going to (by release-manager
fiat, unless Adrian or Jacob want something else) plan 1.2 alpha (and
corresponding major feature freeze) for Tuesday, January 5. Any major
feature not in trunk by
On Wed, Dec 23, 2009 at 9:44 PM, Russell Keith-Magee
wrote:
> I could live with either approach existing in the codebase. I won't
> express a preference, though - I'll leave the decision of which
> approach is preferable to those that will actually have to use it.
Honestly, given both the controv
On Thu, Dec 24, 2009 at 5:22 AM, Russell Keith-Magee
wrote:
> My concern with having two fields is that it introduces a false
> dichotomy. There aren't just 2 options here - potentially any
> permutation of the following list is possible:
While this is true, there are three common cases, which ca
On Tue, Dec 29, 2009 at 6:15 PM, Nic Pottier wrote:
> I'd be curious to hear what the reason for not accepting this patch
> is. String truncation is a pretty common task, and having it built in
> seems like a no-brainer.
It is built in, though, it's just called "slice". The only thing
people se
On Wed, Dec 30, 2009 at 2:35 PM, Jerome Leclanche wrote:
> This thread is 20 hours old, you've got a bunch of people who made clear
> points on why the filter was needed/expected. You don't want to take lesson
> off that? fine, as I said you can browse IRC logs, or even google
> results[1]. I don'
On Wed, Dec 30, 2009 at 5:05 PM, Jerome Leclanche wrote:
> When truncating characters, we are obviously talking about truncating just
> that: characters. Truncating bytes is a behaviour implemented by |slice.
You misunderstand: I'm not talking about bytes, I'm talking about
composed and decompose
Simon, the amount of pushback this is getting, and the changes which
need to be made to start bringing it up to snuff, make me feel far too
nervous about this being ready in time to make 1.2 at all. I know
you've put in the effort to shepherd this along, but I'm starting to
think it's time to push
The first alpha preview package for Django 1.2 is now available.
* Release notes: http://docs.djangoproject.com/en/dev/releases/1.2-alpha-1/
* Download instructions: http://www.djangoproject.com/download/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You r
On Wed, Jan 6, 2010 at 8:17 AM, sago wrote:
> What is it about Django and NT scholars - have you come across James
> Tauber (of Pinax fame?)
There are at least three Django committers who can list one or another
ancient Greek dialect among their studies. Not sure why that is, but
it does make for
On Fri, Jan 8, 2010 at 1:41 AM, ssc wrote:
> Has anyone ever come across this before ? Could not find anything
> related in Trac, but I thought I better ask in here before I file a
> bug...
If you import a signal, using one particular path to specify the
import, you get that signal object. If you
On Thu, Jan 7, 2010 at 10:40 AM, Honza Král wrote:
> ModelForm has a save() method that saves the model. It is reasonable
> to assume that if the form is valid, the save() method call should
> succeed, that's why the entire model is validated.
Actually, I can see a strong argument against this: i
On Fri, Jan 29, 2010 at 3:02 AM, pyleaf wrote:
> hi,all.
> how REST looks like in django?
General usage questions belong on the django-users list.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message because you are subscribed to the G
I'm kind of choosing this arbitrarily, but as far as I can tell we
should be good to go for rolling a beta any time. So I'm picking
Thursday.
If there are any blockers I'm not aware of, let me know. Also, note
that this will be the final feature freeze for 1.2; if it ain't in
trunk when I roll the
Due to a combination of exhaustion and illness on the part of the
release manager (me), I'm going to slide the 1.2 beta release one day;
that means beta tomorrow (Friday, February 5, probably evening-ish US
Central time). If anyone's got last-minute commits, get 'em in.
--
"Bureaucrat Conrad, you
Tonight we've released Django 1.2 beta 1:
* Blog entry: http://www.djangoproject.com/weblog/2010/feb/06/12-beta-1/
* Release notes: http://docs.djangoproject.com/en/dev/releases/1.2-beta-1/
* Checksums: http://media.djangoproject.com/pgp/Django-1.2-beta-1.checksum.txt
Note that this constitutes f
My thoughts, as concisely as I can express them:
1. I'm not in favor of redesigns for redesigns' sake; yes, the current
admin UI has been around for a while, but if we rework it, we
should rework it because there are actual issues with it which need
to be resolved. A good first step would
On Tue, Feb 9, 2010 at 2:09 AM, Harro wrote:
> - Make email unique and username non-required on the model. That would
> make implementing something that authenticated by email a lot
> easier :)
1. It's *extremely* unlikely that changes will be considered which
require every Django install on the
Once again:
This is really not the time to be discussing this; anything in this
thread's going to be long forgotten by the time 1.2's out and 1.3
feature discussions are going on.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message bec
On Tue, Feb 16, 2010 at 4:39 AM, Ivan Sagalaev
wrote:
> It's not the question of responsibility. We're changing a minor version
> which is supposed to be backwards compatible. If a site will break in this
> case people won't go looking for some responsible person they'll just blame
> Django for br
On Sun, Feb 21, 2010 at 11:22 PM, Jacob Kaplan-Moss wrote:
> A bit more background: I've been told at PyCon that cmemcached is
> unmaintained and deliberately being left to die in favor of pylibmc.
>
> Because of that I'm +1 on your proposal, and I'll argue that we not
> consider it a "feature add
On Thu, Feb 18, 2010 at 3:30 PM, orokusaki wrote:
> I have thought for a year, pertaining to Django, about one thing: Why
> doesn't validation propagate from the lowest level? Why should this
> have to take place at a higher level? What happens with I want to do
> things without using forms? Then,
On Fri, Feb 26, 2010 at 3:26 PM, orokusaki wrote:
> 1) Allow for subclasses of normal models to override attributes of the
> parent model. Then, if any attributes exists that override the parent,
> simply use the subclass to create the table and treat the parent as an
> ABC adding its attributes (
On Wed, Mar 10, 2010 at 4:55 PM, Andrew Godwin wrote:
> The question is, is it even worth fixing? I'm tempted to conclude that
> you're limited to shorter model/field names by your database (or use
> db_table/db_column), but there's also the possibility of that method using a
> much shorter way of
This message is inappropriate for this list. Before sending mail to
Django discussion lists in the future, please read up on the
difference between the django-developers list and the django-users
list.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You re
On Fri, Mar 12, 2010 at 2:43 AM, Harro wrote:
> See ticket: http://code.djangoproject.com/ticket/13095
Quoting from http://docs.djangoproject.com/en/dev/internals/contributing/#id1
"Don’t post to django-developers just to announce that you have filed
a bug report. All the tickets are mailed to a
On Fri, Mar 12, 2010 at 9:50 AM, orokusaki wrote:
> @James Bennett I was suggesting a new feature. Is it still not
> appropriate?
It still is not appropriate, and it's not hard at all to see why:
*ANY* question which begins "How do I do this in Django" belongs on
the djang
On Fri, Mar 12, 2010 at 4:39 PM, aditya wrote:
> The trouble is, there is no straightforward way to configure the name
> and domain of a site.
Sure there is: create a Site object, or edit an existing one, setting
the values you want on it.
> Currently, Django uses "example.com" for both the doma
Russ is about to put up a post on the Django weblog with the current
state of 1.2. There's been quite a bit of progress since the last
update, but there are still around 60 tickets which will need in-depth
attention before we hit the point of releasing 1.2; the remainder of
the tickets on the miles
On Tue, Mar 16, 2010 at 10:36 AM, orokusaki wrote:
> It doesn't seem that the core team is interested in working on Model
> validation at the moment: http://code.djangoproject.com/ticket/13121
> (my failed ticket)
Stop right there and actually go back and *read* all the feedback
you've gotten, be
On Wed, Mar 17, 2010 at 1:00 AM, orokusaki wrote:
> Actually I'm not lying. Russell hasn't given me any feedback regarding
> my idea or patch. I didn't simply reopen tickets. Russell changed my
> ticket to a documentation ticket, so I opened a new ticket to discuss
> that which he avoided in his d
On Thu, Jan 21, 2010 at 1:28 PM, Gerry wrote:
> without using ModelForms? I really like the new Model validation but I
> don't
> like (nor think its very DRY) to override the save method for all of
> my models
> to just call full_clean(). It would be nice if there was someway I
> could enable
> va
This message isn't appropriate for django-developers; in the future,
please direct announcements of software releases (other than Django
itself) to appropriate forums.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message because you are
On Fri, Apr 16, 2010 at 4:34 PM, Taylor Marshall
wrote:
> There's already a unofficial mirror on GitHub which is maintained by jezdez:
AFAIK there are mirrors on pretty much every DVCS/"social code"
hosting site; bitbucket's got one as well, for example.
--
"Bureaucrat Conrad, you are technica
On Mon, Apr 19, 2010 at 10:16 AM, Richard Laager wrote:
> On Mon, 2010-04-19 at 07:55 -0700, orokusaki wrote:
>> With all respect, you still haven't addressed my main concern: You
>> told me that it was because of backward compatibility that this simple
>> change couldn't be put in the trunk. It i
On Mon, Apr 19, 2010 at 12:09 PM, orokusaki wrote:
> Firstly, thanks to Jacob for the highly hostile nature of his bedside
> manor.
>
> Secondly, I didn't assert anything. I merely referenced the docs (I
> suppose this will be another case where you simply adjust the docs to
> mirror your recent a
Tonight we're proud to announce, finally, the first Django 1.2 release
candidate. If all goes well, it will also be the *only* release
candidate, and Django 1.2 final will release one week from today.
For more information, consult:
* The Django project weblog:
http://www.djangoproject.com/weblog/
On Wed, May 5, 2010 at 11:53 PM, Rajeev J Sebastian
wrote:
> When can we start discussing potential small/micro fixes for the next
> version of django?
A week or two after 1.2 final is released.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received
We're pleased today to announce the release of both Django 1.1.2 --
the second bugfix release in the 1.1 series -- and the long-awaited
Django 1.2.
More information is available over at djangoproject.com:
* Django 1.1.2 release announcement:
http://www.djangoproject.com/weblog/2010/may/17/112/
*
Following up on last week's Django 1.2 release, today we'd like to
announce Django 1.2.1, the first bugfix release in the 1.2 series:
* Announcement blog post: http://www.djangoproject.com/weblog/2010/may/24/121/
* Download: http://www.djangoproject.com/download/
* Checksums: http://media.djangopr
On Tue, Jun 1, 2010 at 2:26 AM, Dougal Matthews wrote:
> It's fine from here (Edinburgh) and I've not had any problems lately.
There was an issue a few days ago where Media Temple -- which provides
our hosting -- was under a DDoS attack, and so sites hosted there were
intermittently available. Th
This list is for discussion of the development of Django, not for
discussing uses of Django.
Also, generally it's a good idea to use Google to search for an answer
to questions like this.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this mes
On Thu, Jun 17, 2010 at 3:39 PM, Jacob Kaplan-Moss wrote:
> That said, your suggestions are sensible enough -- though personally I
> think MediaWiki is a load of ... ahem .. -- so you probably should get
> in touch with Charles or James (see links in the footer) and offer to
> help out.
That woul
On Sun, Jul 4, 2010 at 12:05 PM, dffdgsdfgsdfhjhtre wrote:
> It seems right now, django's documentation is trying to do both at the
> same time. One project that does reference documentation really well,
> imo, is PHP. For example: http://us3.php.net/preg_replace Say what you
> will about PHP, but
While trying to answer a question in the IRC channel today, I was
poking around in the template system and noticed that resolve_variable
has a comment about a particularly odd "gotcha": because it catches
and silently hides a TypeError raised by calling a method without the
appropriate number of a
On 5/9/06, Bryan <[EMAIL PROTECTED]> wrote:
> I understand that this is not a priority for Django, but I would like
> to know if anyone is working on Ajax support in Django. I read through
> the proposals and was wondering if I could do anything to help with one
> of the layers (preferably with t
On 5/10/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I need to be able to use models like this:
>
> class Xlwzl(models.Model):
> xl = IntegerField(primary_key=True)
> wzl = IntegerField(primary_key=True)
You'll probably want to read this and save yourself some time:
http://ww
On 5/10/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> But I need this for an ugly existing database (tm) that I cannot
> touch. And, of course, it's a ManyToManyField in very open disguise,
> but it has additional attributes. Unfortunately, a ManyToManyField is
> based on an association table w
On 5/10/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I think you'll run into many problems since everything expects that
> it can do a get(pk=...), which wouldn't work.
Well, considering that Django explicitly advertises zero support for
this situation, I'd say getting *anything* to work is p
> On 05/11/06 17:02, [EMAIL PROTECTED] wrote:
> (myself included -- I am not about to put my production db
> password into a subversion repository that everyone in the company can
> read).
On 5/11/06, Steven Armstrong <[EMAIL PROTECTED]> wrote:
> For putting the dsn in the env I'm -1 as it may ca
On 5/12/06, arthur debert <[EMAIL PROTECTED]> wrote:
> I have an app that uploads a 4mb file and is taking a ton of memory.
> >From tickets 1484/1569 they are set as fixed, but I cannot find them on
> django's source code. Are these patches active in trunk? If not,
> anyones knows if they're worki
On 5/14/06, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> Django documentation page titles are like: "Django | Documentation | Model
> Reference", "Django | Documentation | Template Guide", "Django | Code |
> RemovingTheMagic". If you have multiple tabs open with these pages, all you
> get to see is
On 5/15/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> In the very beginning, I often made trivial errors in some functions
> used by the methods. Sometimes this resulted in exceptions that were
> ignored and resulted in missing data. This is then hard to spot since
> you don't get a hint what e
On 5/29/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> The "Add Field" functionality is nearly ready.
You are aware that a full implementation of schema evolution for
Django was accepted as a Google Summer of Code project, right?
--
"May the forces of evil become confused on the way to your h
On 5/30/06, Bryan <[EMAIL PROTECTED]> wrote:
> If we implement
> that verification view by having it turn on is_active (is_active =
> True) instead of using is_approved, then we can never explicitly make
> our users inactive, because all they would have to do to reactivate
> their account is click
On 5/30/06, Bryan <[EMAIL PROTECTED]> wrote:
> I need their email to be verified at sign up and when they change it in
> their profile. I don't understand how this system would verifiy
> someone changing their email address.
Honestly, now that I've read through this more thoroughly, I think
what
On 5/30/06, Bryan <[EMAIL PROTECTED]> wrote:
> Now that you've mentioned it, first_name and last_name should not even
> be in User. They should be in profile. Profile is for
> personalization, not for user specific login criteria like (is_active,
> is_staff, is_superuser, IS_APPROVED).
My perso
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Additionally: The fact that I have _not_ the full domain knowledge (=
> background information) enables me to make those "sweeping suggestions"
> from a newcomers point of view (who cares not much about project details
> and internals, but j
On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 1) a commandline util only (via manage.py)
This would maintain consistency with the rest of Django's management
options; I'd always figured that at least part of the schema evolution
interface would involve manage.py.
--
"May the fo
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> The term 'Audit' explained here:
>
> http://case.lazaridis.com/multi/wiki/ProjectOverview
That page is a lot of marketing speak along with a note that open
source projects can order your services at a "reduced rate". So now
you sound like y
On 5/25/06, lazaridis_com <[EMAIL PROTECTED]> wrote:
> * Replace command "django-admin.py" by "django-admin" or "django"
Naming it 'django' would likely cause confusion, leading users to
believe that it runs an entire Django-powered site. There is a web
server built in to it, but this web server
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Please feel free to send me any concrete criticism about my website via
> private email (your comments are very welcome).
I seem to have screwed that up by forgetting that replies go to the
list by default. My apologies for the mistake.
--
OK, the other thread's getting a bit long and I doubt there's much
more productive discourse to be wrung from it, so let's start anew.
What follows is my own rambling personal opinion, and nothing more.
One of the issues that seems to have come up from the "audit" thread
is that of the usability
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Is such a document available, which lists e.g.
>
> * committers
Not that I'm aware of.
> * subsystem leads (or component leads)
Except for the i18n system, there really aren't "component leads" for Django.
> * code level contributo
On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Is is possible to have an overview of the currently _active_ team,
> including roles? e.g. on a page on the project wiki?
The Django project defines pretty much two roles: "core developers"
and "everybody else". Again, with the exception of
1 - 100 of 1014 matches
Mail list logo
