Re: Good news for Django devs - labbler.com code has been released to public

[Mario Osorio]

I'm sure we all here appreciate examples of commercial products built on 
top of Django, but I'm afraid some translation is in order ... google's 
translate confused me even more...

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2eef970e-ff2a-4b25-bdf8-f6a864e3fe9d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Which Real Time Communications Protocol

[Mario Osorio]

Thanks to everyone contributing to my question ... I will be evaluating all 
options soon!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5e9c7cf0-3bfb-4612-8886-2d6cb2f9c3f3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Which Real Time Communications Protocol

[Mario Osorio]

My app will have to communicate different customers (Linux devices, Windoze 
devices, iOS devices and Android devices at least).

Overall, any of these customer devices will start one of many processes and 
some of the other devices are required to respond by letting their users 
know about the just initialized event. The original event might in turn 
start related events with more or less the same behavior.

I will be using email and SMS as 'secondary weapons', but I need some sort 
of real time communications protocol as primary so whatever devices that 
are connected and need, will be notified immediately. (I'm not sure I'm 
making much sense at this point)

What communications protocol can I use so that it:

   - offers real time response
   - is as simple as possible
   - works in as many different customers as possible

Thanks a lot in advanced!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/17ffdba6-041f-49b8-b688-aa5cdb4a7130%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Need some advise on how to use a RESTful API

[Mario Osorio]

I need to work on a django app that will eventually benefit from a RESTful 
API so it can be used from any web browser as well a from apps writtens for 
iOS and Android.

Being so new to django development I don't even have any ideas on how to 
use a RESTful API, for example,


   1. Should I begin the development use a RESTful API, or should I add ir 
   when needed? ( it IS going to be used anyways)
   2. Of course I understand I'm adding another layer of work to the final 
   product but, can someone please explain how bad deep and how complicated 
   this layer might be?
   3. I've found a couple of online tutorials and I'll soon be working on 
   them, but I honestly think there is nothing quite like reading the opinions 
   of different people as to what the workflow with a RESTful API in django 
   implies. I think a simple overview of the general workflow will answer most 
   of the questions I have in mind right now.

Thanks a lot in advanced!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/cc10edc2-e978-461e-986f-43dd73eea63e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django Tutorials

[Mario Osorio]

Incredible!

Thank you very much for your effort. This is looks incredibly better than 
before.

Now, and  I don't mean to be picky.

Remember I'm a noob. I do however, have a lot of experience in failing when 
following tutorials.

I understand the tutorials are on django, and you've made a very nice job 
at keeping the sections small, clear, concise and to the point, but I  
think the use of virtualenv should be PUSHED into the minds of those noobs 
like me wanting to work with django. 

I also understand virtualenv is just desirable or recommended, but if you: 
1) are just learning the basics and/or 2) want to succeed deploying; 
virtualenv is a must, if not mandatory.

I've seen this omission in other tutorials and I don't mean each tutorial 
to make a whole chapter on virtualenv; but at least a few words describing 
what it is and why is it important are in order.

just my two cents ...

In any case; congrats, great job!!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1ddb4840-abdf-499b-bfaf-a92623ab3d0f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django Tutorials

[Mario Osorio]

>From a noob:
I did not have a chance to read a lot, but I must agree with Pepsodent 
Cola: typography IS TERRIBLE to say the least, then again that might be the 
reason I could not read a lot ...

OTOH ... why not use a decent CMS to talk about django? How about starting 
your blog on django using pythonanywhere.com's free service, for example?

You seem to have some good articles, but you should at the very least 
revise your typography.

On Saturday, October 26, 2013 9:05:13 AM UTC-4, Jasvir Singh wrote:
>
> I have started a series of Django tutorial for beginners. I am making 
> them in such a way that a user get knowledge for working on Django in 
> quick and efficient way. 
> Till now, I have completed only introduction phase. 
>
> I'll also make video tutorials for the same exercises. 
>
> Here is link of my tutorials 
> http://goo.gl/3jPaf7 
>
> Please review it. I need your suggestions to make them more efficient. 
>
> -- 
> Jasvir Singh Grewal 
> Blog: jasvirsinghgrewal91.wordpress.com 
>
> : 
> [ GNU/Linux One Stanza Tip (LOST) ]### 
>   
> Sub : To randomly play mp3 songs from a directoryLOST #243 
>
> mpg123 -z /path/to/mp3s/*.mp3 
> This will randomly play mp3 songs from the specified folder. 
>   
> [ajitabhpandey (at) users.sourceforge.net] 
> : 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/13c0a384-5da6-402e-94a1-ccc9b56b732b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: PythonAnywhere->TemplateSyntaxError: 'blog_extras' is not a valid tag library: ImportError raised loading nrpccms.newsroom.templatetags.blog_extras: No module named settings

[Mario Osorio]

 

Fixed: I had to add my projects folder to sys.path in my wsgi script. This 
is my new wsgi script:

activate_this = 
'/home/nimbiotics/.virtualenvs/nrpccms/bin/activate_this.py'execfile(activate_this,
 dict(__file__=activate_this))
import osimport sys
path = '/home/nimbiotics/projects'if path not in sys.path:
sys.path.append(path)
###nrpccms_path = 
'/home/nimbiotics/projects/nrpccms'if nrpccms_path not in sys.path:

sys.path.append(nrpccms_path)###
os.environ['DJANGO_SETTINGS_MODULE'] = 'nrpccms.settings'
import django.core.handlers.wsgiapplication = 
django.core.handlers.wsgi.WSGIHandler()

 

On Friday, October 18, 2013 9:56:55 PM UTC-4, Mario Osorio wrote:
>
> Trying to deploy my very first app in PythonAnywhere (or at 
> AnywhereAnywhere for that matter) I'm currently getting
>
> TemplateSyntaxError: 'blog_extras' is not a valid tag library: 
> ImportError raised loading nrpccms.newsroom.templatetags.blog_extras: No 
> module named settings
>
> (full error log)[http://dpaste.com/1421863/]
> (see error live)[http://nimbiotics.pythonanywhere.com/]
>
> The app newsroom is the very first one in INSTALLED_APPS:
>
> #! python
> # ...
> INSTALLED_APPS = (
> "nrpccms.newsroom",
> "django.contrib.admin",
> # ...
>
> Also, blog_extras.py is at MY_PROJECT/MY_APP/templates, and there IS a 
> __init__.py at MY_PROJECT/mY_APP
>
> Please help me pinpoint my mistakes as I don't know where else to look: 
> This are my first baby steps in the arts of webapps/django
>
> Thanks a lot in advanced!
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c0d6e6ff-7183-4036-b2e9-2259fab4a534%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

PythonAnywhere->TemplateSyntaxError: 'blog_extras' is not a valid tag library: ImportError raised loading nrpccms.newsroom.templatetags.blog_extras: No module named settings

[Mario Osorio]

Trying to deploy my very first app in PythonAnywhere (or at 
AnywhereAnywhere for that matter) I'm currently getting

TemplateSyntaxError: 'blog_extras' is not a valid tag library: 
ImportError raised loading nrpccms.newsroom.templatetags.blog_extras: No 
module named settings

(full error log)[http://dpaste.com/1421863/]
(see error live)[http://nimbiotics.pythonanywhere.com/]

The app newsroom is the very first one in INSTALLED_APPS:

#! python
# ...
INSTALLED_APPS = (
"nrpccms.newsroom",
"django.contrib.admin",
# ...

Also, blog_extras.py is at MY_PROJECT/MY_APP/templates, and there IS a 
__init__.py at MY_PROJECT/mY_APP

Please help me pinpoint my mistakes as I don't know where else to look: 
This are my first baby steps in the arts of webapps/django

Thanks a lot in advanced!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5fff932a-07b7-4919-bc57-f67228088b84%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: View not working / how can I test it in the shell?

[Mario Osorio]

You are right, I fixed that after posting as someone else point it out to 
me, but this is not working out for me nonetheless


On Friday, October 11, 2013 6:11:54 PM UTC-4, donarb wrote:
>
> On Friday, October 11, 2013 2:48:13 PM UTC-7, Mario Osorio wrote:
>>
>> Hello all, working with mezzanine, I created in an app (newsroom) folder, 
>> a views.py http://dpaste.com/1413587/. This view is an addition to the 
>> blog app in site-packages. I then I put a section in my blog_post_list.html 
>> template file to (supposedly) show the data from that view 
>> http://dpaste.net/show/6cHStytzI5cqfICpFVAT/<http://bpaste.net/show/6cHStytzI5cqfICpFVAT/>,
>>  
>> but I cannot see this data. blog_post_list.html is my home. Will someone 
>> please point my mistake here? How can I test this view in the shell.TIA!
>>
>
> What is featured_post_list? You assign it in the context, but it doesn't 
> appear anywhere (except as the name of the view method). Perhaps you meant 
> to pass "blog_posts" instead?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/446c4ea4-9ee4-4bad-822a-f001c08666e2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

View not working / how can I test it in the shell?

[Mario Osorio]

Hello all, working with mezzanine, I created in an app (newsroom) folder, a 
views.py http://dpaste.com/1413587/. This view is an addition to the blog 
app in site-packages. I then I put a section in my blog_post_list.html 
template file to (supposedly) show the data from that view 
http://dpaste.net/show/6cHStytzI5cqfICpFVAT/,
 
but I cannot see this data. blog_post_list.html is my home. Will someone 
please point my mistake here? How can I test this view in the shell.TIA!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/0e003915-e41b-4940-93c8-0d2185b31b6d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

What is the right location for my django translation files?

[Mario Osorio]

Hi,

I'm giving my first steps with python/django/mezzanine so please bear with 
me.

I modified a translation file of the mezzanine's blog application and 
compiled it OK. Mind you: I literally only modified a couple of words and 
left the rest intact.

The only place I found out I could place them in order to test was at the 
blog app's locale folder 
(~/MY_VIRTUAL_ENV/lib/python2.7/site-packages/mezzanine/blog/locale/es/LC_MESSAGES).

It worked fine, but my guts tell me there has to be a better way so I can 
have this file(s) in some other location WITHIN my own mezzanine 
application so:

   1. I can easily maintain them and
   2. I don't have to keep my whole virtual environment in my SCM's 
   repository.in order to keep track of this single file with just a couple or 
   words modified and that will hardly ever get modified again.

I understand I shouldn't keep my environment in the SCM, but that was the 
only (arguable) way I could keep my translation files in sync.

I also tried placing them at MY_PROJECT/blog/locale/es/LC_MESSAGES and 
MY_PROJECT/locale/es/LC_MESSAGES and none worked.

I just found out about LOCALE_PATHS and have not had a chance to test this 
but my concern with this solution however, is whether or not I'll have to 
translate everything (django, mezzanine and all apps) when I'm just 
literally changing a couple of words found in one application.

Any and all comments are very welcome.

Thanks a lot in advanced

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2db52e61-6b52-4326-bf49-0876f6a3c52a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.