Re: Is this true. that django really takes a lot of memory?

On Tue, Feb 17, 2009 at 3:52 PM, James Bennett wrote: > > On Tue, Feb 17, 2009 at 7:40 AM, NitinHayaran wrote: >> Today i read this article and was wondering whether django orm is >> really that bad. >> >>

Re: Is this true. that django really takes a lot of memory?

On Tue, Feb 17, 2009 at 6:49 PM, Malcolm Tredinnick wrote: ... > I'd be somewhat against this, I think. It's *very* easy to reuse > querysets and inadvertently cause extra database queries. ... > we're trading memory > usage for speed and ease of use (and providing a

Re: Is this true. that django really takes a lot of memory?

On Tue, Feb 17, 2009 at 7:13 PM, Malcolm Tredinnick wrote: ... >> if settings.DEBUG and self.prior_iteration: >>warnings.warn("dope!") > > This certainly sounds reasonable and doable today without any real > overhead. Go ahead and make a patch/ticket. OK. Do you

TransactionMiddleware and cursor.execute

The Django docs for TransactionMiddleware state: "When a request starts, Django starts a transaction. If the response is produced without problems, Django commits any pending transactions." This is apparently not actually true. I have some code using cursor.execute while doing no operations

Re: TransactionMiddleware and cursor.execute

On Fri, Mar 6, 2009 at 9:34 AM, Karen Tracey <kmtra...@gmail.com> wrote: > On Fri, Mar 6, 2009 at 10:28 AM, Jeremy Dunck <jdu...@gmail.com> wrote: >> >> The Django docs for TransactionMiddleware state: >> "When a request starts, Django starts a transaction.

Re: Cache related values without needing to hit database twice

On Tue, Mar 10, 2009 at 11:12 AM, Vinicius Mendes wrote: ... > What do you think in saving the author value in the blog instance if it is > achieved through the author instance? It's something like telling blog who > is his author in the moment you are retrieving it from the

Re: IPy for settings.INTERNAL_IPS

On Sat, Mar 14, 2009 at 6:33 PM, Rodrigo Guzman wrote: ... > So, it seems like it'd be a straight forward change to > django.core.context_processors.debug to implement it.  However, it > seems that this functionality would be better placed in the settings > module. Django

Re: IPy for settings.INTERNAL_IPS

On Sat, Mar 14, 2009 at 11:05 PM, Alex Gaynor wrote: ... > Why are you subclassing list if you're going to just add a cidrs attr that's > the list :) I'm handling INTERNAL_IPS which are multiple CIDR blocks. I could have constructed with [IP('...'),IP('...')], but that's

Re: IPy for settings.INTERNAL_IPS

Yeah, dumb bug. :) On Mar 15, 2009, at 4:12 PM, Ludvig Ericson <ludvig.eric...@gmail.com> wrote: > > On Mar 15, 2009, at 05:02, Jeremy Dunck wrote: > >> class CIDR_LIST(list): >> def __init__(self, cidrs): >> from IPy import IP >

Re: Reminder: Django 1.1 beta this week means feature freeze

On Thu, Mar 19, 2009 at 4:20 PM, Jacob Kaplan-Moss wrote: ... > > /me looks meaningfully at Justin. FWIW, I've been a terrible contributor on GIS. All praise to Justin's great work. --~--~-~--~~~---~--~~ You received this message

Dynamic urlconf

I have a need for dynamic URL definition, but I see that RegexURLResolver.reverse uses a cache, _reverse_dict. Option 1): Make a RegexURLResolver subclass which sets _reverse_dict back to an empty MultiValueDict when a URL is added or removed Option 2) Make me do it in my app ;-) Which do

Deletion of related objects

Malcolm, Jacob pointed me at you, since the code in question was a commit around QSRF-time. I'm aware of ticket #7539, but would prefer to keep the scope narrower and ask the hopefully-useful question-- is #9308 a bug? If so, I'd like to close it for 1.1. In summary, #9308 describes a

Dallas 1.1 sprint - dates?

Hey all, I was considering putting on a Dallas sprint for 1.1. I'm not sure exactly when 1.1 will ship, but soon-ish, so I was thinking about trying to make the sprint the weekend of 4/10 (Easter weeked) or 4/17. Any preference? Who can make it or will consider making it?

Re: Dallas 1.1 sprint - dates?

Gary, Justin? On Fri, Apr 3, 2009 at 9:47 AM, Alex Robbins <alexander.j.robb...@gmail.com> wrote: > > I live in the Dallas area and would be interested in coming, whenever > it happens. > > On Apr 2, 12:45 pm, Jeremy Dunck <jdu...@gmail.com> wrote: >> H

Dallas Django sprint 4/18 - 4/19 at CoHabitat

We've firmed up the Dallas Django sprint plans: Django 1.1 is around the corner, but there are lots of bugs left to squash. Come meet the other Django people around Dallas and check out Cohabitat, the great coworking spot in uptown. We'll start Saturday, April 18, 2009 at 9:00am through Sunday,

Re: My Proposal [GSoC '09 Admin UI Improvements]

On Fri, Apr 24, 2009 at 6:19 PM, Zain Memon wrote: > Hello, > As you might know, I'm one of the Django GSoC students this year. My mentor > is (the) Jacob Kaplan-Moss, and he's already started corrupting my innocent > mind. > This summer, I'm implementing a collection of ideas

Callable LazyObject?

I recently had a need for a LazyObject which was callable. The __call__ meta method isn't forwarded to _wrapped, so it's an error to call, even if the underlying _wrapped does support it. In my case, was trying to do the following: User = SimpleLazyObject(lambda: get_user_model()) User()... I

Re: Callable LazyObject?

:12 AM, Luke Plant <l.plant...@cantab.net> wrote: > On 05/03/14 23:05, Jeremy Dunck wrote: > > > if ... > > elif isinstance(value, LazyObject): > > pass > > elif callable(value): > > ... > > My gut instinct is that if Django's template code has

Re: Proposal for prepared statements API

On the None -> IS NULL issue, I presume there are, for any given use case, not that many argument permutations of None and not None passed. I suggest that the PreparedStatement abstraction map to multiple actual prepared statements, one for each None/not None permutation. Then when executing,

Re: django-firebird backend: migrations and NULL fields

How about adding a flag to Operations? implied_null, perhaps. On May 14, 2014 7:52 AM, "Andrew Godwin" wrote: > Hi, > > That's currently the only approach I'm afraid - there's an open issue > (raised by Shai Berger I believe) that column_sql should be broken down > into more

narrow writes (as 3rd-party library)

I'm attempting to implement narrow writes (that is, writing only fields which have changed). I would be able to do this as a 3rd-party Mixin library if some changes were made to Model.save_base. 1) returned whether the row was created or updated, e.g. if .save_base returned the `updated`

Re: Would AssertMaxQueries (similar to AssertNumQueries) be a useful addition

I use this method on my own test subclasses, and I find it useful as a tripwire: a cause for review and consideration, more than a hard error. Did the number of queries go up on this change? Is that reasonable or a mistake? Have we blown the perf budget so we should refactor? Or maybe the number

Re: Two proposals for the Django Code of Conduct.

As someone affected by an issue that would fall under the proposed change [1], I still support an explicit guideline about external behavior influencing internal acceptance. The safety of all members is more important than the risk of misapplication of the rule. [1]

Storage engine aliases?

Right now, I think that static/media handling is fairly confused in the documentation, and a bit confused in the code itself. We have a few special-cases floating around: default_storage (needed for legacy before storage backends) staticfiles_storage (needed for collectstatic/handling)

Re: Storage engine aliases?

ecurity. I think it’s useful to keep > the concepts separate, even if they ultimately depend on the same APIs — > basically the Storage base class that defines the usual file APIs plus an > URL. > > -- > Aymeric. > > > On 29 sept. 2014, at 22:46, Jeremy Dunck <jdu...@gmail

Re: status of 1.8 release blockers

Thank you, Tim, for shepherding this. On Jan 3, 2015 8:09 AM, "Tim Graham" wrote: > Here is the fourth update with a week to go until alpha. At this time, I > am thinking we'll have the feature freeze on Monday, January 12 as planned, > but perhaps issue the actual alpha

Re: Multiple template engines for Django - week 13

If getting proper support for other template backends would only delay the 1.8 release timeline by a couple weeks, I think that is preferable to a generalized 1.8 backend which only include DTL until 1.9. What do others think? On Sat, Jan 3, 2015 at 3:23 PM, Aymeric Augustin <

Trac exception

I was trying to view this: http://code.djangoproject.com/ticket/4 when I got this: " Oops... Trac detected an internal error: database is locked Traceback (most recent call last): File "/usr/lib/python2.2/site-packages/trac/core.py", line 531, in cgi_start real_cgi_start() File

Re: Idea: "fake" model fields

On 9/16/05, Simon Willison <[EMAIL PROTECTED]> wrote: > tagfield = meta.FakeCharField() > def load_tagfield(self): > # Returns the contents of the field when it is displayed > def save_tagfield(self, value): ... Instead of Fake*, I suggest Deferred, or Mapped*, or Extended*.

Re: Added MS SQL Server DB support: Testers wanted!

On 10/14/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > * Run the Django unit tests with SQL Server as the backend. Just run > tests/runtests.py ... > The more eyes we get on this one, the sooner we can make sure it's > solid. Thanks for any help! I have Sql Server at work, and can test this

Re: Added MS SQL Server DB support: Testers wanted!

On 10/15/05, Luke Plant <[EMAIL PROTECTED]> wrote: > > Queries with LIMIT and/or OFFSET probably won't work, because SQL > > Server appears to use "SELECT TOP" instead of LIMIT/OFFSET. Elegant > > solutions to this problem are welcome. :) > > From what I know from one of the more experienced MS

Ticket 683

I've added a half-patch to ticket 683. I don't understand all the magick going down in meta and models, but I hope the bit I did was useful.

Re: FYI: Oracle has free edition now

On 11/1/05, Ian Holsman <[EMAIL PROTECTED]> wrote: > > I guess I'm a bit ho-hum about it. > > why? > > 4G limit > single process > no replication > 32 bit only > and a expensive upgrade path I think this was a direct response to MySql 5.0 supporting views/procs etc. And MS has had MSDE for a

Re: Small report from Django/Rails meetup

On 11/9/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 11/9/05, hugo <[EMAIL PROTECTED]> wrote: > > I would say: release a 0.9 version now (or in the near future) and give > > a clear roadmap (that's what the trac feature is for ;-) ) of what will > > go into 1.0 before release. That way

Re: Django Ajax (WAS: Re: Small report from Django/Rails meetup)

On 11/14/05, Maniac <[EMAIL PROTECTED]> wrote: > But I think this whole approach is wrong and should not be supported. > There are certain reasons behind separating server and client part and > wishing to break this barrier smells like a bad design to me. If Django > will make such things easy

Re: Decoupling core Django handler from database

On 12/15/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > Currently, the core handlers (modpython.py and wsgi.py in > django/core/handlers/) wrap the main request handling in a > try/finally, where the "finally" part closes the database connection. > Obviously, this couples the handler to a

Re: Dojo Licensing

On 12/28/05, Tom Tobin <[EMAIL PROTECTED]> wrote: > IANAL, but it is my understanding that one can > only relicense code if the new license's terms are a superset of the > old license's terms. IANAL either, but my understanding, after reading AFL and BSD and GPL is that AFL is basically BSD with

Re: magic-removal: "Change subclassing syntax"

On 1/25/06, Max Battcher <[EMAIL PROTECTED]> wrote: > I've seen a home-brew Zope-based one. It would be real quick to build > one as a django app... In fact its own my personal project todo list. > How soon do you want it? :-) Mine, too, but you may get to it first. As Soon As Our Copious

Typo on magic-removal sql migration script?

I haven't been following the magic removal branch closely, but here: http://code.djangoproject.com/wiki/RemovingTheMagic There is a migration script for mysql. This line looks wrong: ALTER TABLE auth_groups_permissions RENAME TO auth_group_permissions; Rename to the same name? Perhaps: ALTER

Re: Django sprint at PyCon

On 2/27/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: ... > On other Open Source projects I've worked on, there has been a way to > indicate in the bug tracking system that a patch was attached to a > report. Either by adding [patch] to the title or setting a "patch" > keyword or something

Re: Schema evolution

On 2/28/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: > Actually, PySQLite 2.x does an implicit commit after any DDL > statement. I don't think this is enforced at the SQLite level, but > supposedly the PySQLite author had reasons to do this in the bindings. Do you know what the reasons were,

Re: What if instead of calling them "projects" we called them "sites"?

On 3/2/06, Sean Perry <[EMAIL PROTECTED]> wrote: > I am definitely -2 on this. Malcolm does a good job of starting the ball > rolling as to why. The range is -1..+1 ;-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Buglet in tutorial 2

At: http://www.djangoproject.com/documentation/tutorial2/ This: "By default, Django displays the repr() of each object." It actually uses str() now, right? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django

Re: Solving the POST-data-lost-after-redirect problem

On 6/6/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > * THROW ERROR ON POST: The CommonMiddleware, when adding a slash and > redirecting, can check for POST data. If it finds any, it somehow logs > the error or otherwise alerts the developer. Maybe if DEBUG=True it > can actually display an

Re: Solving the POST-data-lost-after-redirect problem

On 6/7/06, Luke Plant <[EMAIL PROTECTED]> wrote: > I already wrote a validator app that checks > outgoing HTML for validity, using a middleware to intercept the > response. It also stores all details of failed pages so you can go > back to them, which would be overkill in this case. Hmm, this

Middleware fiddling

Is there a reason _request_middleware's are called in the BaseHandler, while _response_middleware's are called in the subclass (i.e. ModPythonHandler)? Also, in BaseHandler.load_middleware, I noticed that an exception loading any middleware will leave the middlewares not None, but also not valid

Re: Solving the POST-data-lost-after-redirect problem

On 6/7/06, Steven Armstrong <[EMAIL PROTECTED]> wrote: ... > GET /some/url/?cm_data_id=78fsd8fasdf7ad8asaf7889sdf > > - load POST/GET data from /tmp/78fsd8fasdf7ad8asaf7889sdf, populate > POST/GET dicts with it > - remove cm_data_id from GET variables > - delete /tmp/78fsd8fasdf7ad8asaf7889sdf >

Re: Multiple database support (#1142) roadblock

On 6/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'd argue that the right solution here would be to push the brains > farther out to the edge. Have management functions call class methods > on models to execute table creation, initial data loading, etc, rather > than having them poll the

Re: "How Django processes a request", first draft

On 6/14/06, James Bennett <[EMAIL PROTECTED]> wrote: > It's up here: > http://www.b-list.org/weblog/2006/06/13/how-django-processes-request You're doing a more thorough thing, but this is a nice backgrounder to compare/contrast: http://simon.incutio.com/archive/2005/08/15/request

Re: "How Django processes a request", first draft

On 6/14/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > On 6/14/06, James Bennett <[EMAIL PROTECTED]> wrote: > > > It's up here: > > http://www.b-list.org/weblog/2006/06/13/how-django-processes-request > *sigh*. And now that I go to actually review yours,

Re: RFC: Django history tracking

On 6/17/06, Vitaliy Fuks <[EMAIL PROTECTED]> wrote: > It would be nice to record "who" made the change (optionally when there > is a user with an id available). +1 > I thought that storing complete row copies on both inserts and updates > to original object isn't that bad - it certainly

Re: trac updates/changesets not being sent?

On 6/21/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On Jun 21, 2006, at 8:25 AM, Malcolm Tredinnick wrote: > > I noticed earlier this evening that automatic documentation rebuilds > > aren't happening, either (models-api.txt and templates.txt have both > > been updated today). > > OK,

Re: Copyright and Contributions

On 7/4/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > fingers crossed about that lame-assed ORM patent -- so I'll do what Patents don't have much to do with copyright. ;-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: Unicodification of Django

On 7/5/06, Filipe <[EMAIL PROTECTED]> wrote: > and the first changes towards that will start appearing in python 2.5: > http://www.python.org/dev/peps/pep-0332/ That's rejected, so not actually in 2.5, right? --~--~-~--~~~---~--~~ You received this message

Dave Thomas keynote at Ruby Conf

Mostly on the topic of what Rails needs to do better to get more mainstream acceptance. Most not very sexy. Many, Django already does. http://blog.scribestudio.com/articles/2006/06/30/railsconf-2006-keynote-series-dave-thomas /me wishes he could work full time on dj 1.0. :(

Re: Modularized Django (Again)

On 7/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Just a small correction... multi-db is not a Summer of Code project, > just a regular old nobody's-paying-me-to-do-it project. :) Sorry about that. The scope and timing of it made me think it was. :-/

Re: Is MS SQL Server support coming anytime soon?

On 7/25/06, Ray <[EMAIL PROTECTED]> wrote: > > We're using Oracle and SQL Server at work--the lack of support for > those two is really a killer. > > What is involved in creating such a support for a DB--any doc/anything > to start? Maybe I can take a look at the SQL Server side. The short

Re: Consider releasing a .95 beta

On 7/27/06, Kevin Menard <[EMAIL PROTECTED]> wrote: > People run svn update at > different times and all that jazz. I know we've been burned once or > twice by people running different versions of django. Two-phase email? "I'd like to svn up, report back when ready." Or, if too large a team,

Re: Consider releasing a .95 beta

On 7/27/06, Matt the Destroyer <[EMAIL PROTECTED]> wrote: > Does Django improve if everyone's out for lunch? I think that depends on whether we're all friends here. I certainly think about Django over lunch often. --~--~-~--~~~---~--~~ You received this message

Re: Default escaping -- again!

On 7/27/06, Deryck Hodge <[EMAIL PROTECTED]> wrote: > > On 7/27/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > Make a setting to turn define the default, and if the setting's not > > there, auto-escape. > > Anyone that doesn't want it can just

Re: If there was massive security hole found in Django, are there plans in place to deal with it?

On 8/9/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > I'm not completely sure I agree with the way the Ruby team are handling > this release, but since I don't know the details yet, I can't really > work out what is happening; they may have very good justification for > the way they are

Admin lockout

In the admin, it's possible to disable all superuser accounts. It'd be good to not allow the last one, or to warn against it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to

Re: Admin lockout

On 8/10/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > I'm not so sure about this... It seems like protecting people from > themselves. Presumably the "real" superuser has access to Python code > and the database, so that person can make the change in the database, > or via the Python API, if

Re: A final post-0.91 release?

On 8/11/06, Deryck Hodge <[EMAIL PROTECTED]> wrote: > I know at NDN we're going to be pre-mr for the foreseeable future (and > probably all of Scripps, too). Even if not an actual release, just > compiling a set of patches known to be useful for those on pre-mr > releases would be nice. +1 from

Re: Security questions

On 8/13/06, Jakub Labath <[EMAIL PROTECTED]> wrote: > 2. Due to time/money reasons I am running a relatively old version of > django. I realise that by doing that I'm left on my own. However It > would be nice to be able to go to Trac or somewhere and see all > security related bugs/fixes so that

Re: django unicode-conversion, beginning

On 8/16/06, Bill de hÓra <[EMAIL PROTECTED]> wrote: > Now. Most (all?) browser UAs sniff the content to second guess the media > type. They don't much pay attention to Content-Type (I think maybe IE > ignores it altogether). The problem for this example is they might be > doing something similar

Re: django unicode-conversion, beginning

On 8/9/06, gabor <[EMAIL PROTECTED]> wrote: > hmmm.. are you sure that the situation with unicode-aware editors is so bad? > > could you name some non-unicode-aware editors? > for me it seems that from notepad through vim to eclipse everything does > unicode fine... On Windows, I used UltraEdit,

Re: django unicode-conversion, beginning

On 8/16/06, gabor <[EMAIL PROTECTED]> wrote: > 3. will assume the database is in DEFAULT_CHARSET > - maybe can we somehow ask the db for it's charset? I think you really have to allow for different charset in the DB-- legacy integration, remember.

Re: JavaScript and Changeset 3541

On 8/18/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > Sure, I'd be happy to explain -- my (very strong) preference is to > bundle *no* JavaScript toolkit. That's partially because we shouldn't > limit which toolkit developers use, and partially because it's > unnecessary bloat within the

BigIntegerField

I'd like an integer field larger than postgresql's integer (2^31). Any interest in a patch for BigIntegerField? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send

Rails has a Naked Objects tool (aka automagic gui)

I hadn't seen this mentioned on the lists. http://streamlined.relevancellc.com/articles/2006/08/02/screencast-available --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this

Re: Automatic-manipulator, very slow..... design-decision/bug/misunderstanding?

On 8/31/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > I mean when you're creating a manipulator you can list fields that you > don't want it to touch: > > manipulator = Owner.AddManipulator(follow={'thing': False}) Thanks; I don't see that documented. Probably because manipulators will go

Re: XSS comments from PHP Creator

On 8/22/06, Ahmad Alhashemi <[EMAIL PROTECTED]> wrote: > But if you keep poking holes in all the wrong places, then it is not > the frameworks fault. > > Autoescaping might be a nice DRY feature, but I don't think it has > anything to do with being secure by default. Usable security is about

Re: Re: A final post-0.91 release?

On 8/12/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > OK, I've set up a 0.91-bugfixes branch and given you commit access. Have at > it! > It looks like neither branch is particularly lively just now. I'm trying to decide whether to catch up to 0.90 or 0.91 from r1338. Of course 0.90 is

Re: Re: Re: A final post-0.91 release?

On 9/19/06, James Bennett <[EMAIL PROTECTED]> wrote: > > On 9/19/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > Of > > course 0.90 is easier to get to, but if more developers are coding on > > 0.91, then maybe I'll try to catch that. > > Well, if you

Re: Contrib context processor?

On 10/13/06, James Bennett <[EMAIL PROTECTED]> wrote: > > On 10/13/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > I'm adding it locally, but was wondering if you'd like a patch for one > > either to core or contrib? > > It came up in ticket 2532, and Adrian ve

Re: Q and the | operator (related to ticket #2253?)

On 10/13/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Ticket #2253 is in the process of being fixed as part of a larger > change, so micro tweaks as you are suggesting, whilst they may or may > not fix #2253 are going to be swallowed up in the changes (it's one of > the test cases for the

Re: Data for globalization

On 10/15/06, GinTon <[EMAIL PROTECTED]> wrote: > And here you have the files for add/integrate them to any Django > project: > http://satchmo.python-hosting.com/file/trunk/satchmo/G11n/ > http://satchmo.python-hosting.com/file/trunk/satchmo/load_G11n.py It may be too much work, or you may not be

Re: handlers.modpython.is_secure -- why not use self._req.is_https() ?

On 10/24/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > In other words, I hope I haven't talked you into breaking trunk. :-/ > Relevant (or so I thought) doc: http://www.modpython.org/live/current/doc-html/pyapi-mprequest-meth.html --~--~-~--~~~---~

Re: What's going on with all these branches?

On 10/31/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > This comes up every few weeks. > I've wikified this response here: http://code.djangoproject.com/wiki/ActiveBranches I linked to any branch detail pages I could find, relevant groups discussions, and added a suggestion to test one of

Re: State of MSSQL support

On 11/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Thanks. Any idea as to why adodb was used instead of native > interaction? > By that, you mean FreeTDS via pymssql? It was GPL at the time, and it's now LGPL. I think that's the only reason, though.

Re: Ticket spam

On 11/2/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: ... > Continuing the monologue... See: > > I, for one, am happy to see your efforts. --~--~-~--~~~---~--~~ You received this message because you

Re: Branch Merges?

On 11/6/06, Brian Beck <[EMAIL PROTECTED]> wrote: > > search-api has a wiki page here: > http://code.djangoproject.com/wiki/TextIndexingAbstractionLayer > > There is currently one supported indexer (Lucene) and a couple > experimental (Xapian). It needs polish. I blogged about the status a >

Session renewal: want a patch?

Currently, sessions are renewed only if 1) they're modified or 2) every request. There's a middle ground that's useful: renew the session and cookie if it's within X days of the session's current expiration. This keeps cookies for unmodified sessions from expiring while not sending out a cookie

0.91-bugfixes: response middleware applied even though request middleware returned a response

I just ran into a problem caused by response middleware getting called even though request middleware returned a response. The docs, even in 0.91, claim that all response processing stops if request middleware returns a response, but this was not the case, even on trunk, until [2358], while 0.91

Re: 0.91-bugfixes: response middleware applied even though request middleware returned a response

On 11/10/06, James Bennett <[EMAIL PROTECTED]> wrote: > Can you point me to the other requests? > Apparently, I exaggerated. I could only find one other request, at the end of this thread:

Re: Branch Merges?

On 11/15/06, Aidas Bendoraitis <[EMAIL PROTECTED]> wrote: > > I am just curious, what the status of per-object-permissions branch > is. Today I noticed that the most recent revision number of that > branch matches the revision number of trunk. Does that mean, that the > per-object-permissions

Re: New faster SelectBox.js

On 12/6/06, Graham King <[EMAIL PROTECTED]> wrote: > PS: > If you have lots of elements in your select box, and your object has a > FileField (meaning multipart encoding on your form), you might run into > an intermittent bug Saving, whereby in http.__init__ on this line: > > name_dict =

Re: New faster SelectBox.js

On 12/6/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote: > > nice gui widget, runs too slowly, and the browser will complain. > > if I had to use a multi-selection box with thousands of entries in it, > I'd probably run around and complain too. > The filter_interface makes it much less painful. :)

Re: Thinking out loud: move auth.Messages into the sessions app?

On 12/11/06, Zak Johnson <[EMAIL PROTECTED]> wrote: > > James Bennett wrote: > > Which leads me to wonder whether it wouldn't be better to just do that > > in Django itself, and move the Message model into > > django.contrib.sessions. > > +1. Associating messages with sessions is much more

Re: DjangoPoweredSites wiki article vandalised, please revert

On 12/11/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > Fixed; thanks for pointing it out. > It seems to be missing now... http://code.djangoproject.com/wiki/DjangoPoweredSites --~--~-~--~~~---~--~~ You received this message because you are subscribed to

Re: Re: Thinking out loud: move auth.Messages into the sessions app?

On 12/11/06, James Bennett <[EMAIL PROTECTED]> wrote: > > On 12/11/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > Doesn't this create a small chance that messages intended for one user > > would be given to another user this way? > > Not that I can tel

Re: New faster SelectBox.js

On 12/12/06, graham_king <[EMAIL PROTECTED]> wrote: > > Has anyone else had a chance to test this new SelectBox.js ? I've just started using it. We have about 15 people using admin most of the day. > I would > really appreciate if someone could drop this js into their app and take > a look -

Re: Thinking out loud: move auth.Messages into the sessions app?

On 12/12/06, Rob Hudson <[EMAIL PROTECTED]> wrote: > In one of those articles, he describes the "impersonation" scenario, > which is what I wonder if Jeremy is referring to: No, I was referring to the situation James outlined earlier. But I agree session hijacking is a concern, though totally

Re: Session security (was Re: Thinking out loud)

On 12/12/06, Benjamin Slavin <[EMAIL PROTECTED]> wrote: > Sessions are based on data passed from the client to the server. > Because this data can easily be forged, session impersonation is > possible. That's where picking hard-to-guess identifiers comes in. > If you have a secure random session

Re: Regarding the copy of forms -> oldforms

On 12/21/06, Rob Hudson <[EMAIL PROTECTED]> wrote: Would Michael Radziej's suggestion work better for those who develop against trunk but whose servers are running stable releases (ie: 0.95)? That's my case and I just ran up against this issue. If you're doing that in the expectation that

Schema evo (actual movement!)

For whatever reason, there's been a lot of rustling about schema evo on the dju list. I thought I'd draw attention to this thread: http://groups-beta.google.com/group/django-users/browse_thread/thread/bd1417a08e37774a/e157ea7b4a37b556 On dec 16, Victor Ng reported good progress towards a

Re: Has anyone looked at ticket #1476?

On 12/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I am new to Django and web development for that matter but I saw ticket #1476 posted about related objects being displayed as lists with a link to allow the user to edit. Yeah, that looks useful, but Joseph never submitted a patch

Re: Signed Cookies (ticket #3285)

On 1/12/07, Gulopine <[EMAIL PROTECTED]> wrote: ... > I should note, however, that security extends only so far as preventing > a user from tampering with the cookie. If the cookie itself is > compromised and removed from the computer by an attacker, it would > presumably still be considered

Re: Using Capistrano to Deploy/Maintain Django Applications

On 1/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Has anyone used Capistrano with Django? I have been looking for documentation, and the Cap manual uses RoR for its examples - it's not very approachable for someone doing application deployment outside of that framework. Maybe post of

<    1   2   3   4   5   6   >