On Mon, Aug 23, 2010 at 5:21 AM, Waldemar Kornewald
wrote:
> Hey Flavio,
>
> On Sun, Aug 22, 2010 at 12:40 PM, FlaPer87 wrote:
>> Hi Alex,
>>
>> I agree about leaving the backend outside django too (IMHO, all
>> backends should live outside django). Is there any link that points to
>> the apps yo
Hey Flavio,
On Sun, Aug 22, 2010 at 12:40 PM, FlaPer87 wrote:
> Hi Alex,
>
> I agree about leaving the backend outside django too (IMHO, all
> backends should live outside django). Is there any link that points to
> the apps you used for tests and to the mongodb backend?
>
> As you might know, We
Hi Alex,
I agree about leaving the backend outside django too (IMHO, all
backends should live outside django). Is there any link that points to
the apps you used for tests and to the mongodb backend?
As you might know, We've been working on a django_mongodb_engine that
uses django-nonrel and djan
Hi Alex,
On Aug 21, 9:01 am, Alex Gaynor wrote:
> However the largest open question is what of this work
> should be merged into trunk, and what should live external. My
> recommendation would be for any changes in Django itself to be merged,
> including the new form fields, but for the MongoDB
On Sat, Aug 21, 2010 at 2:01 AM, Alex Gaynor wrote:
> My
> recommendation would be for any changes in Django itself to be merged,
> including the new form fields, but for the MongoDB backend (and,
> indeed, any future backends) to live external to Django,
I agree. I'd like to see the first step t
Hey Alex,
Thanks for the great work on this! I haven't had a chance to check it out in
a while, but looking forward to diving back in when my schedule allows. I
did start looking into porting list fields to postgres, but haven't made
much progress yet.
Personally I think your recommendation re me
Hello all,
With this past week GSOC has officially come to it's close, and I'm
here to report on the status of the query-refactor. The original
purpose of this branch was to do refactorings to the internals of the
ORM, and produce a prototype backend for a non-relational database to
demonstrate t
On Fri, Jun 11, 2010 at 5:25 PM, Russell Keith-Magee
wrote:
> On Thu, Jun 10, 2010 at 10:18 PM, Waldemar Kornewald
> wrote:
>> That's right. We believe that the long-term advantages of having a
>> common AutoField for everyone outweigh the short-term disadvantage of
>> a few people having to migr
On Thu, Jun 10, 2010 at 10:18 PM, Waldemar Kornewald
wrote:
> On Thu, Jun 10, 2010 at 2:31 PM, Russell Keith-Magee
> wrote:
>> On Wed, Jun 9, 2010 at 4:25 AM, Waldemar Kornewald
>> wrote:
>>> By not supporting string-based primary keys the MongoDB and SimpleDB
>>> communities will have to maint
On Fri, Jun 11, 2010 at 12:22 AM, Waldemar Kornewald
wrote:
> On Thursday, June 10, 2010, Dj Gilcrease wrote:
>> Wouldnt an autofield like http://dpaste.com/hold/205665/ work where
>> connection.creation.auto_field_base_type is set to int by default in
>> django/db/backends/creation.py but could
On Thursday, June 10, 2010, Dj Gilcrease wrote:
> Wouldnt an autofield like http://dpaste.com/hold/205665/ work where
> connection.creation.auto_field_base_type is set to int by default in
> django/db/backends/creation.py but could be overridden by an
> individual backend to be str or unicode or w
Wouldnt an autofield like http://dpaste.com/hold/205665/ work where
connection.creation.auto_field_base_type is set to int by default in
django/db/backends/creation.py but could be overridden by an
individual backend to be str or unicode or whatever?
--
You received this message because you are s
On Thu, Jun 10, 2010 at 2:31 PM, Russell Keith-Magee
wrote:
> On Wed, Jun 9, 2010 at 4:25 AM, Waldemar Kornewald
> wrote:
>> By not supporting string-based primary keys the MongoDB and SimpleDB
>> communities will have to maintain their own version of all Django apps
>> which are already App Eng
On Wed, Jun 9, 2010 at 4:25 AM, Waldemar Kornewald wrote:
> On Tue, Jun 8, 2010 at 8:55 PM, Alex Gaynor wrote:
>> On Tue, Jun 8, 2010 at 12:11 PM, Waldemar Kornewald
>> wrote:
>>> On Tue, Jun 8, 2010 at 7:03 PM, Alex Gaynor wrote:
On Tue, Jun 8, 2010 at 2:37 AM, Waldemar Kornewald
w
On Tue, Jun 8, 2010 at 8:55 PM, Alex Gaynor wrote:
> On Tue, Jun 8, 2010 at 12:11 PM, Waldemar Kornewald
> wrote:
>> On Tue, Jun 8, 2010 at 7:03 PM, Alex Gaynor wrote:
>>> On Tue, Jun 8, 2010 at 2:37 AM, Waldemar Kornewald
>>> wrote:
Why did you revert the AutoField patch? BTW, in the Dja
On Tue, Jun 8, 2010 at 12:11 PM, Waldemar Kornewald
wrote:
> On Tue, Jun 8, 2010 at 7:03 PM, Alex Gaynor wrote:
>> On Tue, Jun 8, 2010 at 2:37 AM, Waldemar Kornewald
>> wrote:
>>> Why did you revert the AutoField patch? BTW, in the Django-nonrel
>>> patch you'll find a few other changes which w
On Tue, Jun 8, 2010 at 7:03 PM, Alex Gaynor wrote:
> On Tue, Jun 8, 2010 at 2:37 AM, Waldemar Kornewald
> wrote:
>> Why did you revert the AutoField patch? BTW, in the Django-nonrel
>> patch you'll find a few other changes which were related to AutoField:
>> ForeignKey needs to find out the actu
On Tue, Jun 8, 2010 at 2:37 AM, Waldemar Kornewald wrote:
> Hi Alex,
>
> On Jun 7, 9:35 pm, Alex Gaynor wrote:
>> As you can see the fruits of these efforts have already begun to land
>> in my branch, and I suspect that the multidb refactorings of last year
>> have left us in a better state than
Hi Alex,
On Jun 7, 9:35 pm, Alex Gaynor wrote:
> As you can see the fruits of these efforts have already begun to land
> in my branch, and I suspect that the multidb refactorings of last year
> have left us in a better state than I appreciated: while the concepts
> and data structures used in the
Hey all,
If you saw my email last week you know that my goal for the bulk of
the GSOC work was going to be refactoring the Query class to be less
SQL/relational db specific. After spending much of last week taking a
few different approach at this it's become clear to me that that
approach would r
On Tue, Sep 29, 2009 at 11:48 AM, Rob Madole wrote:
>
> Hmm. I just spent some time looking at #11828, and I don't think the
> "syncing one db at a time" will work. The first problem this causes
> is with anything that subscribes to the post sync signal. Content
> type does this, so it can cre
Hmm. I just spent some time looking at #11828, and I don't think the
"syncing one db at a time" will work. The first problem this causes
is with anything that subscribes to the post sync signal. Content
type does this, so it can create permissions. If we sync one db at a
time, I don't see how
On Mon, Sep 14, 2009 at 1:54 PM, Joseph Kocherhans
wrote:
>
>
> On Mon, Sep 14, 2009 at 12:16 PM, Alex Gaynor wrote:
>>
>> FWIW, Russ, Joseph Kocherhans, and I discussed this at the DjangoCon
>> sprints and our conclusion was to have syncdb only sync a single table
>> at a time, and to take a --
On Mon, Sep 14, 2009 at 12:16 PM, Alex Gaynor wrote:
>
> FWIW, Russ, Joseph Kocherhans, and I discussed this at the DjangoCon
> sprints and our conclusion was to have syncdb only sync a single table
> at a time, and to take a --exclude flag (or was it --include?) to
> specify what models should b
On Mon, Sep 14, 2009 at 12:49 PM, JL wrote:
>
> Russell Said:
>
> "I'm yet to be convinced that `Meta: using` is actually a good thing.
> IMHO, it's the very model of a setting that makes it impossible to
> re-use your application. The setting will probably survive into the
> final version, but I
Russell Said:
"I'm yet to be convinced that `Meta: using` is actually a good thing.
IMHO, it's the very model of a setting that makes it impossible to
re-use your application. The setting will probably survive into the
final version, but I suspect we need a much better mechanism than
`Meta: using
On Fri, Sep 4, 2009 at 8:56 AM, Craig Kimerer wrote:
>
>
> On Thu, Sep 3, 2009 at 5:00 PM, Russell Keith-Magee
> wrote:
>>
>> On Fri, Sep 4, 2009 at 7:14 AM, Craig Kimerer
>> wrote:
>> > I've spent a little time using this branch and looking at the
>> > possibility of
>> > using it with my projec
On Thu, Sep 3, 2009 at 5:00 PM, Russell Keith-Magee
wrote:
>
> On Fri, Sep 4, 2009 at 7:14 AM, Craig Kimerer
> wrote:
> > I've spent a little time using this branch and looking at the possibility
> of
> > using it with my project. Below is a short list of problems and ponies
> that
> > I have enc
On Fri, Sep 4, 2009 at 7:14 AM, Craig Kimerer wrote:
> I've spent a little time using this branch and looking at the possibility of
> using it with my project. Below is a short list of problems and ponies that
> I have encountered (or want).
>
> 1. It'd be awesome if we could mark certain databas
> it should attempt to look up relationships there first. The reverse
> > > API should also be available somehow so I can override where a foriegn
> > > key lookup is done (much like I can already do on reverse look ups
> > > with an extra 'where' clause
's behavior I'd want to figure out first. For example, let's say I
> have a model with Meta.using = 'db1' and a 2nd model with Meta.using =
> 'db2'. When I try to access a foreignkey relation from something on
> Model1 to Model2, which DB should it
_or_404 (you may have
> already done this).
>
I'd prefer not to alter get_object_or_404 (or similar helpers),
however don't forget, in addition to Models get_object_or_404 can take
a QuerySet, so you can do
get_object_or_404(MyModel.objects.using('db2'), pk=pk)
And it
tions too ... like get_object_or_404 (you may have
already done this).
Regardless of your current status with the branch, I fully intend to
keep on using this code. Luckily, we're all mysql based here so I
don't have to worry about the custom back end stuff :) Thanks again
for your
Hey all,
It seems GSOC has finally come to a close and so I'm giving my final
status update as a part of GSOC (but I'm not going anywhere!). When
we last left off I had just gotten Oracle support working, however
after reviewing with Russ we agreed that the solution was a good bit
On Aug 15, 3:19 am, ccahoon wrote:
> This is the case, yes, if the HTTP and GZip middleware are not used.
> We had to modify both of those to make sure they didn't consume the
> content generator to find the Content-Length. I imagine, IF we wanted
> to, setting the Content-Length header could be
I'm in agreement with Tai. Keeping them separate gives them consistent
behavior for view authors to expect.
"One thing I'm curious about here is the HTTP Content-Length header.
It's late and I'm tired and cranky, so I may have missed it, but
outside of the infrastructure for runserver I can't fin
I think I prefer keeping HttpResponse and HttpResponseStreaming
separate. Using the latter indicates explicitly that the user wants to
send a streaming response and disable any middleware that doesn't
explicitly support it. Using the former should always consume any
content passed to it so that mi
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
My last task before the GSoC hard pencils down date on Monday is an
attempt at a solution to ticket #7581. The essential issue is that a
lot of middleware requires access to the whole of
HttpResponse.content, but this prevents streaming responses (to
prevent timeouts).
To allow for streaming resp
This week was mostly administrative and very small changes. I finished
up 2131, 5241, 6527, 10190 pretty fully. Any further changes by the
end of GSoC should be pretty small. I have pushed a couple tickets
further back (particularly 9081 and related ideas), because they are
not strictly necessary
Thanks for you input Justin.
I just went on and tried using Django ORM natively on the application
it self (to stay under django) and Elixir on all master database
interactions.
After a little effort, the results were great and I did achieve the
behaviour I expected. I'm positively surprised with
On Tue, 28 Jul 2009, Ricardo Santos wrote:
> What is the current status of the multi version support? I mean will
> it be merged with trunk any time soon?
... snip ...
I think this is slated for the 1.2 timecycle. The GSoC istelf ends
sometime in late August, so that's likely the earliest tim
Hi Alex
What is the current status of the multi version support? I mean will
it be merged with trunk any time soon?
I ask you this because I am at a early stage of designing the
architecture of a new project, and this will have to support several
clients (separate databases) but connected by a m
Hey all,
I didn't get a ton of code written this week, however I have a very
clearly laid out plan for how to handle custom Query classes now.
It's my goal to get the code written and done this weekend while I'm
at PyOhio (if you're in the Columbus area please come on out, it
promises to be a gre
This week I tested HttpResponseSendFile with a boat load of server
configs. You can check out the compatible ones on my branch. It
(ticket #2131) looks to be pretty much complete on my branch. Let me
know what you think -- I have committed quite a few changes to docs
and the actual functional code
Hey all,
Sorry for the slightly delayed update. This past week I worked on
completing the work on my m2m-refactor branch. Specifically I worked though
the review notes from my mentor, as well as ensuring all changes are
completely backwards compatibly. In addition I put together a backwards
comp
Yes! Even if I don't make it to Djangocon, I'd still love to see the
info available.
---Peter Herndon
http://spookypony.com
On Jul 12, 2009, at 3:34 AM, Kevin Kubasik wrote:
> So I was traveling some this week and getting back into the swing of
> things back here in Utah. I didn't get to t
So I was traveling some this week and getting back into the swing of things
back here in Utah. I didn't get to the twill backend I wanted to write this
week, but I did start to write real documentation.
The other thing I wanted to measure responses on is submitting a talk on
windmill integration at
Greetings from Fort Collins, CO. I've been sampling from the New
Belgium Brewery here, and I am pretty upset that I will be missing it
on the east coast.
I've made significant updates to my "charset" improvements (spawned
from working on ticket #10190). This has required some changes to
HttpRespo
Hey all,
This week was fairly productive. I got a lot of good docs done this week,
as well as implementing the using option in the inner Meta class. For this
next week I'm writing up a detailed account of the last API changes that
multi-db will need. Specifically with resepect to get_db_prep_*,
Hey all,
This past week I mostly finished off the m2m-refactoring work this week as
well as fixing a few bugs Russ spotted in the multi-db code. For this next
week I think I'm going to be working almost exclusively on docs, as Russ's
wife just had a baby so I think spamming him with source code t
Hi everybody,
I was productive right after I sent the last update but then I got
stuck on the validators. I did, however created a few test validators
and tests for those (expect the number of django tests to go up thanks
to this since I generate them semiautomatically :) ).
What I did this week
Hey all,
This has been a productive week for multiple database support in Django.
Firstly I got all my original work into Django's SVN repository, in
more-or-less atomic commits (they weren't perfect, but unfortunately most of
the early work was anything but linear). Secondly all tests are now pa
Hey All,
Sorry about the delayed updated, I got busy on Friday and then I had the
dash through the weekend. During the last week I implemented multiple
database support for transactions (which was necessary to solve the postgres
DDL problems I mentioned last week). I got this ton and have gradua
Hi all,
I officially began work this week (for some value of officially that doesn't
include the official GSOC project starting :) ). I've had good success in
getting a lot of the ground work laid, specifically I got the connections
object in, updated a bunch of management commands for a --databa
Hi Alex,
On Fri, May 8, 2009 at 16:04, Alex Gaynor wrote:
> Hello All,
>
> I've spent the past week at EuroDjangocon, and as such I've had the
> opportunity to discuss multi-db stuff with a bunch of very smart people.
> Simon and I resolved the issue of DSNs vs. dicts (as long as Simon can
> dyn
Hello All,
I've spent the past week at EuroDjangocon, and as such I've had the
opportunity to discuss multi-db stuff with a bunch of very smart people.
Simon and I resolved the issue of DSNs vs. dicts (as long as Simon can
dynamically add a new DB he's happy). Otherwise nothing has changed.
Pers
On Fri, May 1, 2009 at 1:17 PM, Malcolm Tredinnick
wrote:
> Given that Summer of Code students will be given a subversion branch at
> djangoproject.com to commit to -- in order to provide maximum visibility
> for their work within the community -- it's probably worth just using
> git-svn and pull
On Fri, 2009-05-01 at 13:09 -0600, Brian Rosner wrote:
> On Fri, May 1, 2009 at 12:10 PM, ccahoon wrote:
> > I have also been looking in to how I want to do revision control
> > locally. After playing around with various systems, I think I've
> > settled on Git. Does anyone have any recommendatio
On Fri, May 1, 2009 at 12:10 PM, ccahoon wrote:
> I have also been looking in to how I want to do revision control
> locally. After playing around with various systems, I think I've
> settled on Git. Does anyone have any recommendations for local
> revision control? Is using anything other than S
Happy Friday everyone. This week has been pretty busy with school,
again, but interspersed with some useful bits.
I selected ticket 10834 for my interim bug fix. It is closely linked
with my proposal description and should be a good way to start hashing
out a work flow for working on Django.
I h
On Jul 15, 2008, at 10:50 PM, Brian Rosner wrote:
> The documentation is pretty much done. I would like for people to give
> it some attention and shake out any problems. Not a big deal and can
> be dealt with after a merge. The tutorial needs a bit of
> newforms-admin love. I haven't touched it
I'm almost positivie #7353 is no longer an issue. I was getting that
error with oldforms-admin, and once upgrading to newforms-admin it was
resolved.
On Jul 16, 12:16 am, "Joseph Kocherhans" <[EMAIL PROTECTED]>
wrote:
> On Tue, Jul 15, 2008 at 11:50 PM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
On Tue, Jul 15, 2008 at 11:50 PM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
> Hey all,
>
> I wanted to quickly update everyone on the status of the
> newforms-admin branch. It is quite literally a few tickets away! I
> have either fixed or triaged many tickets today so that the branch can
> get me
Hey all,
I wanted to quickly update everyone on the status of the
newforms-admin branch. It is quite literally a few tickets away! I
have either fixed or triaged many tickets today so that the branch can
get merged into trunk. The tickets triaged really shouldn't have been
made blocker tickets an
> The problem is that people pop up every couple weeks and ask precisely
> the sort of thing you're asking: in effect, "what's the status of
> this, and when will it land in trunk". The answers to these questions
> haven't changed in a very long time; what's needed is people writing
> code, not pe
On 11/17/07, ElegSub <[EMAIL PROTECTED]> wrote:
> We will disagree about the accuracy of that statement but your
> response is by far the most clear and succinct response to this
> question yet. Thank you.
The problem is that people pop up every couple weeks and ask precisely
the sort of thing yo
On Nov 17, 8:06 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> All you're doing is asking the same questions as in previous threads.
> How does that inject clarity?
We will disagree about the accuracy of that statement but your
response is by far the most clear and succinct response to th
On Fri, 2007-11-16 at 18:03 -0500, Elegantly Subtle wrote:
> There's no real decisive answer to this recurring question so
> hopefully this will inject some clarity into the discussion...
All you're doing is asking the same questions as in previous threads.
How does that inject clarity?
> Wha
There's no real decisive answer to this recurring question so
hopefully this will inject some clarity into the discussion...
What is the current status of Multiple Database support in Django?
What is the timeline for integration of Multiple Database support in
the trunk?
The current ticket
On Tue 21 Aug 2007, Andreas Stuhlmüller wrote:
> Hey Django developers,
>
> this is the last status update for my Summer of Code project [1]
> before (or while) the final evaluation takes place. After a few words
> on last week's changes, I would like to summarize what is
Hey Django developers,
this is the last status update for my Summer of Code project [1]
before (or while) the final evaluation takes place. After a few words
on last week's changes, I would like to summarize what is currently
possible using the REST interface, what is still left to do an
2007/8/19, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> On 8/17/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > Just one (latest?) thought, it's a bit hard to debug because
> > 400 errors are not really verbose, is it possible to find a
> > way to make debug easier? For the moment, I have: if
> >
On 8/17/07, David Larlet <[EMAIL PROTECTED]> wrote:
> Just one (latest?) thought, it's a bit hard to debug because
> 400 errors are not really verbose, is it possible to find a
> way to make debug easier? For the moment, I have: if
> settings.DEBUG: print i.errors but I'm sure it can be better.
I
2007/8/13, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
> I added code for forms to TemplateResponder (create_form,
> update_form), an example that shows how to use this code and another
> example that shows how to specify the data format at the end of your
> URLs.
I didn't know the curry function, v
2007/8/12, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> On 8/11/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > Here is my suggestion: the current forms from model or instance are
> > great but you often need a custom form, what about an extra-argument
> > to the collection (better because I alrea
This is the seventh status update for my Summer of Code project, the
Django REST interface [1].
Last week, I extracted code from the ModelResource class that is not
directly related to models but useful for resources in general, moved
it to Resource and made ModelResource inherit from Resource
On Sun, 2007-08-12 at 13:28 +0200, Andreas Stuhlmüller wrote:
[...]
> Once the SoC final evaluation is over (Mon, August 20th), it will be a
> lot easier (=possible) for me to work together with other people and
> to accept code contributions. This strikes me a little strange since
> SoC is suppos
On 8/11/07, David Larlet <[EMAIL PROTECTED]> wrote:
> Here is my suggestion: the current forms from model or instance are
> great but you often need a custom form, what about an extra-argument
> to the collection (better because I already need a form in the
> collection in order to return a creati
2007/8/10, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> On 8/6/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > * What about additional pages like: create form, update form, delete
> > confirmation and so on? I've just noticed the get_create_form at the
> > end of the TemplateResponder but how can
On 8/6/07, David Larlet <[EMAIL PROTECTED]> wrote:
> * What about additional pages like: create form, update form, delete
> confirmation and so on? I've just noticed the get_create_form at the
> end of the TemplateResponder but how can I redirect to this function?
> (I haven't seen how to do this
2007/8/5, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> I am currently reading "RESTful Web Services" by Leonard Richardson
> and Sam Ruby. See [3] for a summary of the main points from the
> chapter on best practices for REST-oriented architectures with short
> notes on where the REST interface st
2007/8/3, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> On 7/13/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > * About users, how can I handle django users' permissions? John
> > Sutherland had already done some work on django-crudapi [1] and it
> > could be interesting to allow this access contro
This is the sixth status update for my Summer of Code project. You can
find more information as well as an updated timetable at [1]. During
the last two weeks, I mainly worked on unit tests and on simplifying
the relationship between the REST interface and URLs.
I added manage.py, settings.py
On 7/13/07, David Larlet <[EMAIL PROTECTED]> wrote:
> * About users, how can I handle django users' permissions? John
> Sutherland had already done some work on django-crudapi [1] and it
> could be interesting to allow this access control.
Good question. I would subclass one of the authentication
2007/6/23, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> As always, criticism, ideas and suggestions are welcome!
>
Ok let's go :-)
First of all, thanks for your awesome work, I eventually take time to
review it and it sounds exactly what I expected. Here are some random
thoughts about the curren
On 7/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Would it be possible to, instead of passing in collection_url_pattern
> to the Collection, pass in the name of a named url pattern, which
> internally would get reverse()'d?
Yes. After talking to Malcolm about how URL customization could b
Hi list,
This week I continued to work on the "startapp" command of
django.core.management and changed its default behaviour to create a
standalone application (with skeleton files) when you run: "django-
admin.py startapp myapp". Current skeleton files are: release.py,
setup.py, MANIFEST.in, doc
Very nice! I'm going to try this out tonight with a pet project of
mine.
Also, since it seems like the API is in at least a little bit of
flux...I'd like to make a request:
Would it be possible to, instead of passing in collection_url_pattern
to the Collection, pass in the name of a named url pat
On 7/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I would love to try it out with one of my apps, but maybe a really
> quick HOWTO on how it's supposed to be set up with a project?
Thanks for the suggestion! I just added a short tutorial to the
project page [1]. The five steps contain onl
tions!
On Jul 2, 5:00 pm, "Andreas Stuhlmüller" <[EMAIL PROTECTED]>
wrote:
> This is the fifth weekly status update for my Summer of Code project
> [1]. Since it is the last update before I take two weeks off to study
> for my exams (as arranged with my mentor), this is p
This is the fifth weekly status update for my Summer of Code project
[1]. Since it is the last update before I take two weeks off to study
for my exams (as arranged with my mentor), this is probably a good
time to sum up the current status of the project and to talk about
what's left to do.
This is the fourth weekly status update for my Summer of Code project,
a generic REST interface for Django [1]. Issues I worked on this week:
1. Authentication. I added authentication hooks to the Collection
class, an implementation of HTTP Basic and Digest authentication
(stateless, header is
This is the third weekly status update for my Summer of Code project,
a generic REST interface for Django [1].
I spent the SoC-part of this week mostly thinking about automated URL
pattern generation, wrote some code and added a few tests that
demonstrate how to use this feature. Currently, you
This is the second weekly status update for my Summer of Code project,
a generic REST interface for Django [1].
This week, I was mostly working on improving the architecture of the
code, in particular by splitting ModelResource into two classes,
Collection (for querysets) and Entry (for
On 6/2/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> Django is a web development framework, and not model development. REST
> (XMLRPC/SOAP) API are created to expose webservices, which by definition
> could be anything, not just models. CRUD is myopic world view.
Thanks for your comment!
You ar
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
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@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
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@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
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@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
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@go
1 - 100 of 122 matches
Mail list logo
