The code I wrote is the one on
https://github.com/stefanfoulis/django-sendsms which is:
settings.py
SENDSMS_BACKEND = 'sendsms.backends.console.SmsBackend'
view.py
from sendsms import api
def home(request):
api.send_sms(body='I can haz txt', from_phone='0768903661',
to=['0768903661'])
Hi,
Unfortunately, this appears to be a problem with (yet another) service
provider not playing nice with mailing lists. Someone has subscribed
to Django Users, and their mail provider (China Mobile in this case)
has decided to reply to the original author, instead of the "reply to"
address.
On 15/09/2012 2:56am, refreegrata wrote:
Hello list.
Obviously, I come here with a question. I have a web application
developed with Django. It's working Ok. The app is just for internal use
and the access to every view is only avaliable for authenticated users
with permissions over the section
I dont know, how to handle an xml response with django.
dhtmlx returns someting like that.
?gr_id=*6*=*abc*=*dsdsd*=*6*=*1234*=*this%20is%20Sparta!*
gr_id = 6
c0= abc
c1 = dsdsd
c2= 6
and so on ...
These fields corresponds a field in my django model and I dont have an idea
how to handle it. I
Hi,
Let me give you a code sample that would be hopefully a push in the right
direction.
Simply follow these steps:
1. Create your model. Its the code interface to your data source
(database)
2. Create your form. Forms are used for processing input data
(validation, error reporting
On Fri, Sep 14, 2012 at 11:40 AM, Lunga Baliwe wrote:
> I am writting a website that sends sms to a cell phone. I am using
> django-sendsms-0.2.2. I followed the README.rst doc and the output does
> appear on the console. How do I make it to actually send the sms?
You might
Good day,
I am writting a website that sends sms to a cell phone. I am
using django-sendsms-0.2.2. I followed the README.rst doc and the output
does appear on the console. How do I make it to actually send the sms?
Your help will appreciated.
Kind regards,
Lunga
--
You received this message
Is there any kind of workaround for this? I'm worried that rows are not
making it into the db because of this problem which I'm also having.
On Wednesday, February 8, 2012 4:44:12 PM UTC-5, akaariai wrote:
>
> Quickly looking through the code it seems this is a bug in Django. The
> full_path
On 9/14/12 10:07 AM, Bob Aalsma wrote:
Well, I have tried your suggestion in all places I could think of and
none of those helped: the createsuperuser kept returning the same
error message. I posted this as a reply some 24 hours ago.
Yes, with no details of what "all the places I could think
Well, I have tried your suggestion in all places I could think of and none
of those helped: the createsuperuser kept returning the same error message.
I posted this as a reply some 24 hours ago.
Op donderdag 13 september 2012 16:58:11 UTC+2 schreef Bob Aalsma het
volgende:
>
> I'm a newbie
Hello list.
Obviously, I come here with a question. I have a web application developed
with Django. It's working Ok. The app is just for internal use and the
access to every view is only avaliable for authenticated users with
permissions over the section (except for the view log-in)
Now
On 9/14/12 3:47 AM, Bob Aalsma wrote:
SOLVED by Tom Evans:
insert
unset LC_CTYPE ; export LANG="nl_NL.UTF-8"
into .bash_profile
That is a solution, but depends on who is running and whether it is a
login shell.
I strongly recommend adding the lines I mentioned earlier to the top of
your
On Fri, 14 Sep 2012 17:24:21 +0300, Tomas Neme
wrote:
I haven't done this, so I might be wrong, but...
queryset.extra(
where=['unaccent("table_name"."column_name"::text) LIKE
unaccent(%s)'],
params=['%%%s%%' % value]
)
first, wouldn't just
It seems to me that I get one of these emails for every post I make,
about one day later. That includes replies to this very thread. I think
they come from the same email address, so they'd be easy to block on an
individual level. But my guess is that everyone posting to django-users
is receiving
I haven't done this, so I might be wrong, but...
> queryset.extra(
> where=['unaccent("table_name"."column_name"::text) LIKE
> unaccent(%s)'],
> params=['%%%s%%' % value]
> )
first, wouldn't just setting params=[value] work? furthermore, isn't
that the whole point of the
http://invisibleroads.com/tutorials/geodjango-googlemaps-build.html
Like that?
Marcos
On Fri, Sep 14, 2012 at 6:30 AM, Coulson Thabo Kgathi wrote:
> can i place markers on geodjango maps, cant figure out how to do that
>
> --
> You received this message because you are
On Fri, Sep 14, 2012 at 10:26 AM, Bob Aalsma
wrote:
> macpro1:~ bobaalsma$ locale
> LANG=
> LC_COLLATE="C"
> LC_CTYPE="UTF-8"
> LC_MESSAGES="C"
> LC_MONETARY="C"
> LC_NUMERIC="C"
> LC_TIME="C"
> LC_ALL=
> macpro1:~ bobaalsma$ python -c 'import locale; print
>
SOLVED by Tom Evans:
insert
unset LC_CTYPE ; export LANG="nl_NL.UTF-8"
into .bash_profile
Op donderdag 13 september 2012 16:58:11 UTC+2 schreef Bob Aalsma het
volgende:
>
> I'm a newbie following the tutorial. In this, creating a superuser is
> described, using
>
> manage.py createsuperuser
can i place markers on geodjango maps, cant figure out how to do that
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/PA5XOTjKhsIJ.
To post to this group,
macpro1:~ bobaalsma$ locale
LANG=
LC_COLLATE="C"
LC_CTYPE="UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=
macpro1:~ bobaalsma$ python -c 'import locale; print
locale.getdefaultlocale()'
Traceback (most recent call last):
File "", line 1, in
File
On Fri, Sep 14, 2012 at 8:52 AM, Bob Aalsma wrote:
> The command & error from createsuperuser:
> macpro1:dripFeedSite bobaalsma$ python manage.py createsuperuser
> …
Can I ask you to try some things, just to see how your environment is
setup. All of these commands
On Fri, Sep 14, 2012 at 12:12 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
> On Thu, Sep 13, 2012 at 12:58 AM, Cal Leeming [Simplicity Media Ltd]
> wrote:
> > Hi all,
> >
> > There is a lot of debate on whether there is a real future for the
kirjoitti:
I have used many condition in my templates, in order to filter my
results. My template file uses this code :
{% for clients in client %}
{% for amounts in amount %}
{% for suspences in suspence %}
{% for tadas in tada %}
{% for transports in transport %}
I have used many condition in my templates, in order to filter my
results. My template file uses this code :
{% for clients in client %}
{% for amounts in amount %}
{% for suspences in suspence %}
{% for tadas in tada %}
{% for transports in transport %}
{% if
The command & error from createsuperuser:
macpro1:dripFeedSite bobaalsma$ python manage.py createsuperuser
Traceback (most recent call last):
File "manage.py", line 19, in
execute_from_command_line(sys.argv)
File
"/Library/Python/2.7/site-packages/django/core/management/__init__.py",
25 matches
Mail list logo