Re: How to send emails using django rest framework from front end angular 7

Hi! I think you've found the wrong mailing list for this post. This mailing list is for the development of Django itself, not for support using Django. This means the discussions of bugs and features in Django itself, rather than in your code using it. People on this list are unlikely to answer

How to send emails using django rest framework from front end angular 7

Dear members, Can anyone help me send emails from django backend with angular 7 frontend , it's very urgent please let me if any one has done it before Regards P. Sai Aravind -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to

Re: Django Rest Framework inside of a Django Project

version > of my app. So I was wondering if I could make a website with Django Rest > Framework or if I have create a Django project for my website and a Django > Rest Framwork for my API > > -- > You received this message because you are subscribed to the Google Groups > "D

Django Rest Framework inside of a Django Project

Hi, I am building a mobile application and I need a Rest API and a web version of my app. So I was wondering if I could make a website with Django Rest Framework or if I have create a Django project for my website and a Django Rest Framwork for my API -- You received this message because you

Re: django + rest

Ed Summers wrote: > In my > case I'm implementing an AtomPub interface for a data repository at > the Library of Congress instead of wanting to stream XML, but the > mechanics are the same. Yes. It's expected to look something like this: if request.META['Content-type'] ==

Re: django + rest

On Dec 30, 8:15 am, Ivan Sagalaev wrote: > BTW, Malcolm's series have inspired me to implement (along with some > refactoring) a file-like interface for HttpRequest[1]. With this you can > actually pass request as a source to, say, a SAX parser and not have to > load

Re: django + rest

Thanks Waylan. I posted to django-users as well (still waiting, but it is the holidays). Those blog posts of Malcolm's were very useful-- although covered ground I was already familiar with. I actually did consider posting on django-users instead of on here, but in the end posted here because I

Re: django + rest

Waylan Limberg wrote: > For a start, you may want to take a look as Malcolm's recent > multi-part series on the subject. Note the third one with regard to > content-types. > > http://www.pointy-stick.com/blog/2008/12/09/implementing-http-services-django/ >

Re: django + rest

Hi Ed. This seems more like a question for the django-users list. django-dev is for the development *of* Django, not development *with* Django. Ask there, and I'm sure you'll get pointers to a lot of helpful resources. For a start, you may want to take a look as Malcolm's recent multi-part

django + rest

I was wondering if anyone else on the list has layered a RESTful service into their django applications. I'm adding an atompub interface to an existing django project, and I'd like to offer the ability to POST and PUT to URIs. Part of my problem is that this service needs to handle large (many

Re: Changes to request_response have broken django-rest-interface

2007/12/3, Malcolm Tredinnick <[EMAIL PROTECTED]>: > On Mon, 2007-12-03 at 13:09 -0800, David Cramer wrote: > > For the most part I'm just doing if request.POST to validate. > > This isn't completely sufficient because it's possible to submit a form > via POST with no data (e.g. a form with

Re: Changes to request_response have broken django-rest-interface

On Mon, 2007-12-03 at 13:09 -0800, David Cramer wrote: > For the most part I'm just doing if request.POST to validate. This isn't completely sufficient because it's possible to submit a form via POST with no data (e.g. a form with checkboxes and maybe some fields that aren't filled in). That's

Re: Changes to request_response have broken django-rest-interface

On 12/3/07, David Cramer <[EMAIL PROTECTED]> wrote: > For the most part I'm just doing if request.POST to validate. The request.method attribute exists precisely for this purpose, so that you can find out what the HTTP request method was ;) -- "Bureaucrat Conrad, you are technically correct --

Re: Changes to request_response have broken django-rest-interface

For the most part I'm just doing if request.POST to validate. On Dec 3, 11:16 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Mon, 2007-12-03 at 11:00 -0800, David Cramer wrote: > > Just my 2 cents... > > > If you drop request.POST, request.GET, and replace them all with > > request.DATA

Re: Changes to request_response have broken django-rest-interface

On Mon, 2007-12-03 at 11:00 -0800, David Cramer wrote: > Just my 2 cents... > > If you drop request.POST, request.GET, and replace them all with > request.DATA -- we're going to again be branching away from Django > trunk. > > For our uses -- POST and GET are completely different things -- >

Re: Changes to request_response have broken django-rest-interface

every potential HTTP > > verb (note that the set isn't restricted to just PUT, POST, GET and > > DELETE) and helps write common code for processing the data -- > > request.method tells you the verb, request.DATA gives you the entity > > body. > > > My second favourite p

Re: Changes to request_response have broken django-rest-interface

t; verb (note that the set isn't restricted to just PUT, POST, GET and > DELETE) and helps write common code for processing the data -- > request.method tells you the verb, request.DATA gives you the entity > body. > > My second favourite preference is to add request.PUT, as > djan

Re: Changes to request_response have broken django-rest-interface

On 10/17/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > However, neither decision is binding until at least one other core > maintainer steps in with some agreement [...] Here's my 2¢: use ``request.DATA``, and keep ``request.POST`` around forever. I quite like the way ``request.GET`` and

Re: Changes to request_response have broken django-rest-interface

ATA gives you the entity body. My second favourite preference is to add request.PUT, as django-rest-interface does at the moment. However, neither decision is binding until at least one other core maintainer steps in with some agreement or sufficient time passes that I'm convinced they r

Re: Changes to request_response have broken django-rest-interface

2007/10/10, David Larlet <[EMAIL PROTECTED]>: > > BTW, no more thought about the way of handling PUT? I've just added a > patch against test.client which add .put() and .delete(), I'm waiting > for (a) reaction(s) to add tests and documentation. > Sorry for insisting on that point but this is

Re: Changes to request_response have broken django-rest-interface

2007/10/8, Peter Nixon <[EMAIL PROTECTED]>: > > Hi David > > Thanks for doing this. I have written a patch for mod_python and added it to > the ticket. I have tested it and deployed it with a patched rest api in > production ;-) > Ok, can you add your patch against django.http.__init__.py too,

Re: django-rest-api use [was Re: Changes to request_response have broken django-rest-interface]

2007/10/7, Malcolm Tredinnick <[EMAIL PROTECTED]>: > > The Resource class is quite as independent from everything as we would > have liked. I say "we" here because towards the end of the SoC period, > Andreas and I spent quite a long time trying to loosen a few of the > couplings between output

Re: Changes to request_response have broken django-rest-interface

xon wrote: > > > > > I tried to open the following ticket but it thinks my IP is a > > > > > spammer, so I am sending to the list: > > > > > > > > > > http://django-rest-interface.googlecode.com/svn/trunk/django_resta > > >

Re: Changes to request_response have broken django-rest-interface

y happy with the work Andreas did. However, some perspective is > necesary. My point *is* to say that there are uses for PUT and POST > beyond django-rest-api and there are plenty of situations where I would > directly implement the handling, rather than using the django-rest-api > classes.

Re: Changes to request_response have broken django-rest-interface

for this? I even thought they would be the more common application django-rest-interface since you can automatically map models to resources only in simple cases. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Gro

Re: Changes to request_response have broken django-rest-interface

ect > it's not really solvable. I just know somebody's going to say "yes it is", so I'll clarify: all REST problems are relatively simple to implement. But trying to force all cases into a framework such as django-rest-api is the part that I think isn't neatly solvable. The nice solutio

Re: Changes to request_response have broken django-rest-interface

-brainer and I'm beginning to think my original suggestion > > (and what Andreas implemented in django-rest-interface) might not be the > > easiest for end users (third-party programmers like yourselves). A > > couple of possibilities spring to mind: > > > > (1) We alway

Re: Changes to request_response have broken django-rest-interface

On 05-Oct-07, at 1:23 PM, Peter Nixon wrote: >> On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote: >>> I tried to open the following ticket but it thinks my IP is a >>> spammer, >>> so I am sending to the list: >> >> If you create an account in Trac, it won't apply spam filtering to >> you.

Re: Changes to request_response have broken django-rest-interface

u're still populating > self.POST as a side-effect. We should neaten this up a bit. > > When I started to think about this and how we would use it, it's not a > complete no-brainer and I'm beginning to think my original suggestion > (and what Andreas implemented in django-rest-interface

Re: Changes to request_response have broken django-rest-interface

On Sat, 2007-10-06 at 18:49 +0200, David Larlet wrote: [..] > I use django-rest-interface too and I have this bug which need to be > quickly fixed so I submitted a patch which need review on #5682, let > me know if I need to do something else. I will add a patch for > modpython too w

Re: Changes to request_response have broken django-rest-interface

ticket but it thinks my IP is a spammer, > > > > so I am sending to the list: > > > > > > > > http://django-rest-interface.googlecode.com/svn/trunk/django_restapi/res > > > >ource.py tries to set "request.method = 'POST'" in order to run PU

Re: Changes to request_response have broken django-rest-interface

) does not currently seem to support PUT. This used > > > to work, however current django SVN seems to have broken it. This > > > breakage seems to be by design as the HttpRequest doc says "All > > > attributes except session should be considered read-

Re: Changes to request_response have broken django-rest-interface

On Thu 04 Oct 2007, Malcolm Tredinnick wrote: > On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote: > > I tried to open the following ticket but it thinks my IP is a spammer, > > so I am sending to the list: > > > > http://django-rest-interface.googlecode.com/s

Re: Changes to request_response have broken django-rest-interface

On 10/5/07, Peter Nixon <[EMAIL PROTECTED]> wrote: > Thanks. I have signed up now, but I still cannot for the life of me find a > link to that page from anywhere. Shouldn't it be a little more prominent? Yeah, it should; I'll add a couple of links when I get a moment. Jacob

Re: Changes to request_response have broken django-rest-interface

On Fri 05 Oct 2007, Tomas Kopecek wrote: > Peter Nixon napsal(a): > > On Thu 04 Oct 2007, James Bennett wrote: > >> On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote: > >>> I tried to open the following ticket but it thinks my IP is a spammer, > >>> so I am sending to the list: > >> > >> If you

Re: Changes to request_response have broken django-rest-interface

Peter Nixon napsal(a): > On Thu 04 Oct 2007, James Bennett wrote: >> On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote: >>> I tried to open the following ticket but it thinks my IP is a spammer, >>> so I am sending to the list: >> If you create an account in Trac, it won't apply spam filtering to

Re: Changes to request_response have broken django-rest-interface

On Thu 04 Oct 2007, James Bennett wrote: > On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote: > > I tried to open the following ticket but it thinks my IP is a spammer, > > so I am sending to the list: > > If you create an account in Trac, it won't apply spam filtering to you. And how does one

Re: Changes to request_response have broken django-rest-interface

On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote: > I tried to open the following ticket but it thinks my IP is a spammer, so I > am sending to the list: If you create an account in Trac, it won't apply spam filtering to you. -- "Bureaucrat Conrad, you are technically correct -- the best

Re: Changes to request_response have broken django-rest-interface

On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote: > I tried to open the following ticket but it thinks my IP is a spammer, so I > am sending to the list: > > http://django-rest-interface.googlecode.com/svn/trunk/django_restapi/resource.py > > tries to set "

Changes to request_response have broken django-rest-interface

I tried to open the following ticket but it thinks my IP is a spammer, so I am sending to the list: http://django-rest-interface.googlecode.com/svn/trunk/django_restapi/resource.py tries to set "request.method = 'POST'" in order to run PUTs through request._load_post_and_files(

Re: GSoC 2007 Status Update VIII: Django REST interface

ntly > possible using the REST interface, what is still left to do and why > the REST interface needs your help. Hi Andreas I cant find a dedicated mailing list for django-rest-interface so I am posting here for the time being. I am not quite sure if I am doing something wrong or not,

GSoC 2007 Status Update VIII: Django REST interface

and, of course, to the community of Django developers in general. I hope you like and use the Django REST interface. Cheers, Andreas Stuhlmüller [1] http://code.google.com/p/django-rest-interface/ [2] http://www.aiplayground.org/artikel/improving-django/ [3] http://django-rest-interface.googlecode.com/svn

Re: GSoC 2007 Status Update VII: Django REST interface

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 > >

Re: GSoC 2007 Status Update VII: Django REST interface

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.

Re: GSoC 2007 Status Update VII: Django REST interface

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,

Re: GSoC 2007 Status Update VI: Django REST interface

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

GSoC 2007 Status Update VII: Django REST interface

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

Re: GSoC 2007 Status Update VI: Django REST interface

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

Re: GSoC 2007 Status Update VI: Django REST interface

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

Re: GSoC 2007 Status Update VI: Django REST interface

ait at least until Fri, August 24th before using the REST interface in any kind of production environment. By then I hope to have done more thorough testing. If you stumble upon a bug, please let me know. Thanks for your feedback. Regards, Andreas Stuhlmüller [1] http://django-rest-inte

Re: GSoC 2007 Status Update VI: Django REST interface

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

Re: GSoC 2007 Status Update IV: Django REST interface

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

GSoC 2007 Status Update VI: Django REST interface

er on best practices for REST-oriented architectures with short notes on where the REST interface still needs improvement. If you feel that there are important issues I am missing, please write me or just open a ticket [4]. Regards, Andreas Stuhlmüller [1] http://code.google.com/p/django-rest-int

Re: GSoC 2007 Status Update IV: Django REST interface

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

Re: GSoC 2007 Status Update IV: Django REST interface

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

Re: GSoC 2007 Status Update V: Django REST interface

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

Re: GSoC 2007 Status Update V: Django REST interface

ghts we gain from the work on the non-model-based part of the project. I will remember your point when I write the documentation on how to use the API. Regards, Andreas [1] http://code.google.com/p/django-rest-interface/ --~--~-~--~~~---~--~~ You received this message

Re: GSoC 2007 Status Update V: Django REST interface

ST APIs that don't correspond 1:1 to models. If I > wanted to implement the Atom Publishing Protocol in Django, what would > I do? Is there code that needs to be written for almost every REST app > in some way or the other and that we can take care of? > > Expect the next update

GSoC 2007 Status Update V: Django REST interface

or the other and that we can take care of? Expect the next update around July 20th. Regards, Andreas Stuhlmüller [1] http://code.google.com/p/django-rest-interface/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

GSoC 2007 Status Update IV: Django REST interface

/django-rest-interface/ --~--~-~--~~~---~--~~ 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 this group,

GSoC 2007 Status Update III: Django REST interface

week is to think about the relationship between the REST interface and authentication. It should be possible to have different levels of access for authenticated and unauthenticated users. Criticism, ideas and suggestions are welcome! Regards, Andreas [1] http://code.google.com/p/django-rest

GSoC 2007 Status Update II: Django REST interface

with such a REST API or if you have specific comments on the code, please let me know. Regards, Andreas [1] http://code.google.com/p/django-rest-interface/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers&q

Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: Re: Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: Re: GSoC 2007 Status Update: Django REST interface

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

Re: GSoC 2007 Status Update: Django REST interface

On 6/1/07, Andreas Stuhlmüller <[EMAIL PROTECTED]> wrote: > > This week, I have started checking in code. I am always happy about > feedback. Add a few lines to your (non-production!) urls.py [1], make > your models available in XML or JSON format and tell me what works for > you and what doesn't.

GSoC 2007 Status Update: Django REST interface

This is the first weekly status update for my Summer of Code project, a generic REST interface for Django. If you haven't seen it, take a look at http://code.google.com/p/django-rest-interface/. This week, I have started checking in code. I am always happy about feedback. Add a few lines to your