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
> whil
What problems have you had with schema evolution?
We're pretty commited to using Django over at my company - and I need
schema evolution badly - so I'll be starting to kick the s-o branch
starting tomorrow afternoon to see if it's stable enough for us.
If necessary, I can apply patches myself as
Gábor Farkas wrote:
> - search-api
> - i could not find any documentation about it
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 blog
I've been using it as well, no problems so far.
--~--~-~--~~~---~--~~
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
On 07/11/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
>
> Jay Parlar wrote:
> > On 11/6/06, David Blewett <[EMAIL PROTECTED]> wrote:
> >> I would like to suggest that the branches that are felt to be complete
> >> sans testing be merged into a single branch. I am anxiously awaiting
> >> several dif
On 11/7/06, Ramiro Morales <[EMAIL PROTECTED]> wrote:
>
> The message also contained a couple of patches to fix some
> brokeness I found in the code. I don't dare to submit a patch for a branch to
> the main Django Trac, (btw, what's the policy in this respect?) but I could
> post the patch here.
On 11/6/06 6:28 PM, orestis wrote:
> In IRC, Jacob KM told me that he is using psycopg2 everywhere now, so I
> think that this should be done.
Indeed I am; it works just fine.
For now, I'd just suggest using the "postgresql_psycopg2" backend. At some
point, we should probably rename that one "
On 11/7/06, Gary Doades <[EMAIL PROTECTED]> wrote:
>
> I notice that the documentation is still recommending psycopg1 and not
> psycopg2 for PostgreSQL. Psycopg2 has been in release status for quite
> a while now. The psycopg site is now firmly recommending psycopg2 and
> noting that psycopg1 is e
In IRC, Jacob KM told me that he is using psycopg2 everywhere now, so I
think that this should be done.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email t
I notice that the documentation is still recommending psycopg1 and not
psycopg2 for PostgreSQL. Psycopg2 has been in release status for quite
a while now. The psycopg site is now firmly recommending psycopg2 and
noting that psycopg1 is effectively obsolete.
It may be better for the documentation,
On 11/6/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 11/6/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> > so, in short, the only testable branches seems to be fullHistory and
> > rowLevelPermissions, and even there it's not clear if they are now
> > considered done, or still in progress.
>
Hey Brian --
Welcome to the community :)
You'll probably get a must better response if you post this to django-users;
django-dev is used for discussion of developing Django itself, not discussions
of using Django.
Oh, and I myself have had great luck hiring people after posts on django-users
Hi,
New to the group. I just took over the website for a smaller, weekly
newspaper in NYC, and I am looking at completely rebuilding the system
with a Django framework. Do you have any suggestions how I can find a
good lead Django developer in NYC. Are there job boards etc, besides
this I shou
On 11/6/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> so, in short, the only testable branches seems to be fullHistory and
> rowLevelPermissions, and even there it's not clear if they are now
> considered done, or still in progress.
Yeah, it's a bit confusing. Could we get status reports from bra
On 11/6/06, David Blewett <[EMAIL PROTECTED]> wrote:
>
> Sounds good to me. What do we need to do here? I'd like to help out
> with the FullHistory branch. It looks like it hasn't had trunk merged
> to it in a while.
>
Find below a message I sent to Uros Trebec, the owner of the branch,
a couple
Jay Parlar wrote:
> On 11/6/06, David Blewett <[EMAIL PROTECTED]> wrote:
>> I would like to suggest that the branches that are felt to be complete
>> sans testing be merged into a single branch. I am anxiously awaiting
>> several different branch merges to core but do not have time to check
>> eac
James Bennett wrote:
> So let me reiterate the call for anyone who wants to bang on a branch
> to step up; we'll set you up with access to commit code and let you
> bang away on it to your heart's content :)
Sounds good to me. What do we need to do here? I'd like to help out
with the FullHistor
On 11/6/06, David Blewett <[EMAIL PROTECTED]> wrote:
> I would like to suggest that the branches that are felt to be complete
> sans testing be merged into a single branch. I am anxiously awaiting
> several different branch merges to core but do not have time to check
> each individual one out to
On 11/6/06, David Blewett <[EMAIL PROTECTED]> wrote:
>
> I would like to suggest that the branches that are felt to be complete
> sans testing be merged into a single branch. I am anxiously awaiting
> several different branch merges to core but do not have time to check
> each individual one out t
I would like to suggest that the branches that are felt to be complete
sans testing be merged into a single branch. I am anxiously awaiting
several different branch merges to core but do not have time to check
each individual one out to test them. Maybe it's time to begin a larger
effort, similar
On 11/6/06 11:57 AM, Christopher Lenz wrote:
> About template breakage: we generally recommend that you make as few
> changes/overrides to the templates as absolutely necessary, for
> exactly the reason that such changes make upgrades harder. You can do
> a lot using only the site_css, site_
Am 06.11.2006 um 18:43 schrieb Jacob Kaplan-Moss:
> I know that a few things on the code site are still broken or
> looking ugly;
> I'm stupid when it comes to upgrading Trac and I always seem to break
> templates. I'll be working on that throughout the day.
Great to see you've upgraded :-)
Ab
Hey again --
Duh, I forgot the most important part: if you've entered a valid name and
email on the "settings" page (http://code.djangoproject.com/settings), the new
spam filter will treat you much nicer. So if you get something legitimate
rejected, try entering a name and email.
Thanks!
Ja
Hi folks --
In an attempt to better deal with the spam problems we've been having, I've
upgraded Django's Trac installation to a newer version. More importantly,
I've upgraded the spam filter plugin so, with luck, we'll be able to reject
more spam and have fewer false-positives.
Many, many t
I'd like to try to fix the bug for ticket #2522 and #2470
(both are apparently the same).
I'm studying the code and trying to understand the possible reason
for ther error. Although new to Django, I have a reasonable
knowledge of Python. However, I'd like some help from someone more
experienced w
Actually, I am using django.contrib.auth "backends" style
login/validation. This makes it so I do not have to implement the
actual login request processing, only provide a backend class that
offers authenticate() and get_user() methods.
perhaps a third function can be optional: add_to_session(d
Great. A patch it is.
Askimet is refusing everything I enter into a new ticket, every single
paragraph from my post individually, and even the standard Lorem Ipsum
paragraph - something isn't right, so please accept my ticket here:
---
Title: Adding Message-ID header in core/mail.py
Body:
A
* medhat wrote, On 01.11.2006 00:13:
> Hi,
> I was trying to create a thumbnail from an ImageField when the object
> is saved. I tried different things but none of them worked the way I
> wanted. Then I thought of using the post_save signal to do it only to
> discover that this signal is sent aft
On 11/6/06, patrickk <[EMAIL PROTECTED]> wrote:
>
> thanks - it´s been difficult enough.
> we´re doing the latest setup right now (permissions and stuff), then
> updating to the latest version.
> it should be done within the next 2 days or so - I´ll post the URL
> here ...
>
> patrick
>
Excellent
thanks - it´s been difficult enough.
we´re doing the latest setup right now (permissions and stuff), then
updating to the latest version.
it should be done within the next 2 days or so - I´ll post the URL
here ...
patrick
Am 06.11.2006 um 11:28 schrieb Aidas Bendoraitis:
>
> Congratulations
Congratulations about setting up the FileBrowser under svn! By the
way, if the FileBrowser project is open to public, what is the URL for
the latest and greatest revision?
Regards,
Aidas Bendoraitis
On 11/5/06, patrickk <[EMAIL PROTECTED]> wrote:
>
> thanks.
>
> Am 05.11.2006 um 20:34 schrieb
Interesting. Shouldn't the debug view make absolutely sure that no
exceptions/error are raised uncaught ?
Or if there is now way to do something meaningful with the exception,
at least present it in a meaningful way.
I wonder what the devs have to say on this. I'd file an enhancement
ticket, tho
orestis wrote:
> I wonder why does a cursor has to be involved for the debug page to be
> shown... I'll look into it.
Debug page shows repr()'s for many local objects for each level of the
call stack. And repr()'s of models often do some queries to show
readable representation.
--~--~-
33 matches
Mail list logo
