I am pretty sure django is leaking a file descriptor, and the closest
thing I could come to was was ticket #6482.
localhost:~ jikanter$ curl http://test/
curl: (52) Empty reply from server
localhost:~ jikanter$ ps auxw |grep httpd
root 16497 0.0 -0.142560 2864 ?? Ss6:44PM
Some background: After following along with that whole discussion
about aggregate support, the idea struck me that the same types of
discussions were had before with schema evolution, and nobody could
really agree on much. Now that management commands are possible,
schema evolution is able to be
I'll throw in my 2 cents too:
I think machine based translation is iffy at best. I'm not the most
up-to-date on py3k, but I have experience with other such projects (I
wrote a Perl 5 to Perl 6 translator for Summer of Code 2006). This is
just my opinion, but I think it would be best for Django
Ben, I'd like to hijack, I hope you don't mind
I'm also trying to get a good GSoC project to submit. If I understand
right, even though a lot of commonly-used modules like registration
and search have third-party apps out there, a few of them might still
be fair game to try to implement in
SmileyChris pointed me here. I wrote up a rant today about newforms
and what I've done to keep it easy (quick) for building forms.
http://www.davidcramer.net/code/111/making-django-newforms-useful.html
Maybe some of those ideas will be of help. Keep in mind, I use Jinja,
so it's got a lot more
Hi,
I think that the pure process of porting Django is a good testcase for
python 3 and for 2to3. So, even if the resulting code could not be used,
the result would still be valuable to python. And that is also good for Django!
Just my 2c,
Michael
On 27 Mar 2008, at 19:46, Jacob Kaplan-Moss wrote:
> Still, the last
> 20% is enough work that a project making AuditTrail into a bonafide
> extension might be good.
Sorry, skipped over your last sentence before I sent the last message!
I will investigate AuditTrail some more...
Ben
On 27 Mar 2008, at 19:46, Jacob Kaplan-Moss wrote:
>
> Starting from those branches? No. The state-of-the-art has moved on,
> and we've gotten wiser about how we maintain open projects. Search,
> for example, has a couple of third-party apps out there; working on
> any of 'em would make a good
On Thu, Mar 27, 2008 at 4:18 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Please note that psycopg2's cursor.execute() doesn't really respect
> DB-API either, in the sense that .fetchone does actually fetch the
> entire resultset into the python process unless the cursor is named,
> i.e.
On Thu, Mar 27, 2008 at 10:19 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Mar 27, 2008 at 9:30 AM, Michael Radziej <[EMAIL PROTECTED]> wrote:
> > I see one possible problem: I observe that mysql always slurps in the
> > whole result set from the database when you only issue
> The specific issues I've run into so far:
>
> * Exception-catching syntax (i.e. ``except Whatever as e`` vs.
> ``except Whatever, e``).
2to3 fixes these, and transparently transforms "the except clauses.
> * Unicode literals (u'...').
Likewise, 2to3 removes the u"" prefix.
So leave the
> > You can (probably) support Python 2.x and Python 3.x out of a single
> > source tree.
>
> From what I've read, this is true as long as the X after 2 is >= 6.
> That's a problem with Django's stated intent to support Python 2.3 on
> Django's release 1.0.
>
> Please correct me if I'm wrong
On Thu, Mar 27, 2008 at 3:19 PM, Daryl Spitzer <[EMAIL PROTECTED]> wrote:
> Do you maintain them side-by-side, or do you just reject patches that
> require new features introduced in 2.4 and 2.5? (I just assumed that
> you maintain 2.3 compatibility by testing on 2.3.)
Exactly. It's not like
On Thu, Mar 27, 2008 at 4:21 PM, Martin v. Löwis
<[EMAIL PROTECTED]> wrote:
> No hurt feelings, no. However, I would find it useful if you could
> add specific reservations and doubts to that. What aspects of Django
> (that I perhaps haven't touch yet) do you consider unmaintainable
> under
> Please see my recent report: 0 years, 0 months, 0 days, 0 seconds.
> You can (probably) support Python 2.x and Python 3.x out of a single
> source tree.
>From what I've read, this is true as long as the X after 2 is >= 6.
That's a problem with Django's stated intent to support Python 2.3 on
On Fri, Mar 21, 2008 at 8:27 AM, Malcolm Tredinnick <
[EMAIL PROTECTED]> wrote:
>
> Ticket #6605 is causing me some grief. Actually, I know exactly what I
> want to do with it (invalid/wontfix), but I suspect there will be
> complaints, so I'd like to see what the consensus is. Originally, I
>
> I hope you won't take it the wrong way when I say I have an extremely
> difficult time believing that.
No hurt feelings, no. However, I would find it useful if you could
add specific reservations and doubts to that. What aspects of Django
(that I perhaps haven't touch yet) do you consider
On Thu, Mar 27, 2008 at 3:56 PM, Martin v. Löwis
<[EMAIL PROTECTED]> wrote:
> Please see my recent report: 0 years, 0 months, 0 days, 0 seconds.
> You can (probably) support Python 2.x and Python 3.x out of a single
> source tree.
I hope you won't take it the wrong way when I say I have an
> Except if Django has a Python 3.0 version, say, this fall, that means
> how many years of supporting two parallel versions of Django and
> merging features and fixes back and forth between them?
Please see my recent report: 0 years, 0 months, 0 days, 0 seconds.
You can (probably) support
> I'm still a bit worried about the fact that, aside from Django being a
> moving target and Python 3.0 being a moving target, WSGI for Python
> 3.0 is *also* a moving target; there still seems to be a fair bit that
> hasn't been settled on how things ought to work.
That is the reason why I
Jacob writes:
> It's hard enough maintaining 2.3, 2.4, and 2.5 side-by-side...
Do you maintain them side-by-side, or do you just reject patches that
require new features introduced in 2.4 and 2.5? (I just assumed that
you maintain 2.3 compatibility by testing on 2.3.)
--
Daryl
On Thu, Mar
On Thu, Mar 27, 2008 at 2:35 PM, Rodrigo Bernardo Pimentel
<[EMAIL PROTECTED]> wrote:
> I'd argue that Python 3.0 is not that much of a moving target either. Of
> course, such a porting project would require following development of 2to3.
Then you need to read the Py3k PEPs more closely. PEP
On Thu, Mar 27, 2008 at 9:46 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> > Do you think they would be good GSoC projects?
> Starting from those branches? No. The state-of-the-art has moved on,
> and we've gotten wiser about how we maintain open projects. Search,
> for example, has a
On Thu, Mar 27, 2008 at 2:26 PM, Ben Firshman <[EMAIL PROTECTED]> wrote:
> What's the status on both of them? Do they still need to be finished?
They are both defunct.
> Do you think they would be good GSoC projects?
Starting from those branches? No. The state-of-the-art has moved on,
and
On Thu, Mar 27, 2008 at 2:30 PM, Rodrigo Bernardo Pimentel
<[EMAIL PROTECTED]> wrote:
> Thanks again for your feedback, James! I'd love to hear more from other
> developers on this matter.
I have to say I agree with James on this one. SoC projects out to be
stuff that can *finished* in a
On Thu, Mar 27, 2008 at 2:30 PM, Rodrigo Bernardo Pimentel
<[EMAIL PROTECTED]> wrote:
> Besides, people are already experimenting with porting their code to py3k,
> so I'm getting the feeling it won't take so long for libraries to get
> ported. Requests from Django developers who are already
On Thu, Mar 27 2008 at 06:25:52AM BRT, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Mar 27, 7:17 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > I'm still a bit worried about the fact that, aside from Django being a
> > moving target and Python 3.0 being a moving target, WSGI for Python
http://code.djangoproject.com/wiki/TextIndexingAbstractionLayer
http://code.djangoproject.com/wiki/FullHistory
I see both were on the GSoC list for last year, but neither have been
touched in a year. On this list, the last mentions of both branches
were a while back too, and nothing
Simon Litchfield schrieb:
> I tend to think there needs to be a documented, 'clean' way of adding
> non_field_errors (and even field errors too) to forms, *outside* the
> clean() methods.
>
>
I had this idea some time ago, too. There is a patch
with documentation and unittest:
On Thu, Mar 27, 2008 at 9:30 AM, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I see one possible problem: I observe that mysql always slurps in the
> whole result set from the database when you only issue a select
> (cursor.query(...))
*Sigh*.
> Theoretically, it's probably possible to
Hi,
I've recently read Malcolm's blog entry about __iter__ and __len__ in the
refactored QuerySets. Interesting!
In the refactored QuerySet, if you do e.g.
if models.Something.objects.all():
...
then QuerySet.__nonzero__ will execute the query and try to fetch the first
result.
I
On Mar 27, 7:07 am, Thejaswi Puthraya <[EMAIL PROTECTED]>
wrote:
> On Mar 26, 10:04 pm, "Sage La Torra" <[EMAIL PROTECTED]> wrote:
>
> > Thanks for the proposal!
>
> > For what it's worth, I'm not a Django mentor, but I am a two-time
> > Summer of Coder. I just wanted to know if you had a
Preparation of First Day at School
Prepare for going back to school this summer. Clean out your room,
your study, your computer (all those cobweb files of lost school
reports) and that way you won't have to be continuously searching for
things throughout the year.
For more information just log on
On Mar 27, 9:36 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Mar 27, 8:25 pm, Graham Dumpleton <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > On Mar 27, 7:17 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
>
> > > On Thu, Mar 27, 2008 at 12:56 AM, Graham Dumpleton
>
> > > <[EMAIL PROTECTED]>
On Mar 27, 8:25 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Mar 27, 7:17 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Mar 27, 2008 at 12:56 AM, Graham Dumpleton
>
> > <[EMAIL PROTECTED]> wrote:
> > > Actually, I already have a copy of mod_wsgi mostly working on Python
>
On Fri, Mar 21, 2008 at 9:27 PM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
Apologies for taking so long to get back to you on this one - it's
been sitting in my "I really must look into that" pile over Easter.
> My opinion is that if your database stores numbers and you always want
> them
On Mar 27, 7:17 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 27, 2008 at 12:56 AM, Graham Dumpleton
>
> <[EMAIL PROTECTED]> wrote:
> > Actually, I already have a copy of mod_wsgi mostly working on Python
> > 3.0, just sorting out areas where now need to handle both unicode and
>
On Thu, Mar 27, 2008 at 12:56 AM, Graham Dumpleton
<[EMAIL PROTECTED]> wrote:
> Actually, I already have a copy of mod_wsgi mostly working on Python
> 3.0, just sorting out areas where now need to handle both unicode and
> bytes, where before only used to have to deal with bytes (old string
>
Earn!! à 5000 US Dollars per month without Investment. monthaly payout
check|.
By working only one hour per day from the cyber café or PC
Guaranteed Earnings for Lifetime!!
100% Legal
100% No Investment
100% No Scam
100% Free Training Support
100% No Door to Door Selling Products
search this site
39 matches
Mail list logo
