Getting 500 error on ASO

2015-03-09 Thread mfox_chi
Hi Everyone, I've been working on learning Django the past few months and have been following the django tutorials here: https://docs.djangoproject.com/en/1.7/. I've followed the tutorial on my local machine in addition to on my A Small Orange account. A Small Orange has this tutorial:

Re: Sharing templates across multiple projects

2015-03-09 Thread JHeasly
Thanks for the feedback Simon & Ilya. I've done submodules in Git before, but I think I'll keep the templates in a separate repo and symbolic link to the repo ... -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group

Re: Django structure

2015-03-09 Thread Raphael Michel
Hi, I'll leave it to others to give recommendations on how you SHOULD organizer your project. However, I can help you with the technical question. Am Sun, 8 Mar 2015 11:53:09 -0700 (PDT) schrieb Gabriel Klein : > My question is how to shared models across apps? You

Re: [Choose Database based on geolocalization]

2015-03-09 Thread xina towner
I'm in process of thinking whether its worth or not... Russell's solution was one of the first solutions that I thought of but it has it's flaws, although obviously is one of the options that it's on the table as it's not as painful as another solution would be. I could try to convince them

Django-taggit : How to delete unused tags ?

2015-03-09 Thread Christine Bale
Hey I have a problem with django-taggit , I want to know how can I delete unused tags In django ? (python 2.7.9 and Django 1.7.4) heres is my code: *models.py* from django.db import models from updown.fields import RatingField from taggit.managers import

Re: How to modify and then recombine json response data without breaking json formatting

2015-03-09 Thread Henry Versemann
OK here goes. The logic in the routine which I actually doing the modification to each individual JSON response looks like this: if str(objctTyp) == 'user': rspnsdata['name'] = lstobjct['name'] rspnsdata['id'] = lstobjct['id'] The routine which is doing this

Re: How to modify and then recombine json response data without breaking json formatting

2015-03-09 Thread Henry Versemann
OK here goes. The logic in the routine which is actually doing the modification to each individual JSON response looks like this: if str(objctTyp) == 'user': rspnsdata['name'] = lstobjct['name'] rspnsdata['id'] = lstobjct['id'] The routine which is doing this is

Re: How to modify and then recombine json response data without breaking json formatting

2015-03-09 Thread Bill Freeman
If it's not the basics, then you haven't provided enough information to allow someone to spot the problem. If you post the code that is performing the modification, someone may be able to spot the issue. On Mon, Mar 9, 2015 at 1:50 PM, Henry Versemann wrote: > Yes Id did

Re: How to modify and then recombine json response data without breaking json formatting

2015-03-09 Thread Henry Versemann
Yes Id did do that. The problems I seem to be having only seem to happen whenever I modify the data before sending it. For many other requests that I'm sending and not modifying the data, before I send them back to the client I have no problems and everything is apparently parsed out ok by the

Re: How to modify and then recombine json response data without breaking json formatting

2015-03-09 Thread Bill Freeman
Did you remember to set the content type of your response to application/json? On Mon, Mar 9, 2015 at 1:18 PM, Henry Versemann wrote: > First to be clear up front let me say that I'm using Django1.7, Python > 2.7.8, and the requests (Requests: HTTP for Humans >

How to modify and then recombine json response data without breaking json formatting

2015-03-09 Thread Henry Versemann
First to be clear up front let me say that I'm using Django1.7, Python 2.7.8, and the requests (Requests: HTTP for Humans ) library version2.4.3 to build the application mentioned below. I have an application which needs to

Re: [ANNOUNCE] Security releases and advisory issued (1.7.6 and 1.8b2)

2015-03-09 Thread Markus Holtermann
Hey Francis, with respect to the ModelAdmin.readonly_fields: no, the vulnerability was introduced in 1.7 with respect to the advisory: yes, all projects that make use the template filters in Python code and rely on Django 1.0 to 1.8b1 (including) are vulnerable. Best, /Markus On Monday,

Re: [ANNOUNCE] Security releases and advisory issued (1.7.6 and 1.8b2)

2015-03-09 Thread Francis Devereux
Hi, On 9 Mar 2015, at 16:01, Tim Graham wrote: > > Today the Django team issued multiple releases -- Django 1.7.6 and 1.8b2 -- > as part of our security process. These releases address a publicly reported > security issue, and we encourage all users to upgrade as soon as

[ANNOUNCE] Security releases and advisory issued (1.7.6 and 1.8b2)

2015-03-09 Thread Tim Graham
Today the Django team issued multiple releases -- Django 1.7.6 and 1.8b2 -- as part of our security process. These releases address a publicly reported security issue, and we encourage all users to upgrade as soon as possible. More details can be found on our blog:

Re: FORM: How to specify current user as value for a form ForeignKey referencing logged on user

2015-03-09 Thread felix
El 08/03/15 14:40, Ryan Alexander escribió: Hey there, This seems like something that should be simple to do but I'm having a heck of a time with it and google searches don't reference anything that's helping me out. I have a form that a user fills out, and it creates a db row based on the

Re: Django structure

2015-03-09 Thread Gabriel Klein
Thank you Ilya, What you said make a lot of senses. On Sunday, March 8, 2015 at 10:36:27 PM UTC-3, Ilya Kazakevich wrote: > > There are 2 types of Apps in Django: > 1) reusable one with clear, documented interface > 2) not reusable one, because it depends on current project heavily. > >

Re: [Choose Database based on geolocalization]

2015-03-09 Thread James Schneider
Perhaps you can investigate more into the 'why' portion of the requirement (which is what I was interested in)? You may be able to convince them to abandon/modify their requirement if you lay out the technical issues and complication they are introducing, and for what gain? I suspect the feature

Re: [Choose Database based on geolocalization]

2015-03-09 Thread xina towner
It's a requirements of a client. I'm not happy to do this...but as I couldn't find any nice solution, maybe because of my limited knowledge, I've asked the mail list. But it seems that a nice solution does not exists so..it's going to be funny. Thanks for the tentative solutions by the way. --

Re: [Choose Database based on geolocalization]

2015-03-09 Thread James Schneider
To me, the question needs more explanation. If a request is made of a server in the US, how does it make any sense to send a database query from that server in the US over to Luxembourg if that is in the proximity of where the user is located? Efficiency? No, that would actually cause double the

Re: [Choose Database based on geolocalization]

2015-03-09 Thread 'Petros Moisiadis' via Django users
On 03/09/2015 01:58 AM, Russell Keith-Magee wrote: > Yes, DB Routers support hints. How are you planning to inject those > hints into the router? Router arguments aren't exposed to the end user > when you do a query - they're automatically generated by the query, > and only include details about

Re: Fixing a poorly written Django website (no unit tests)

2015-03-09 Thread Kevin Ndung'u
On Sunday, March 8, 2015 at 12:16:43 AM UTC+3, Some Developer wrote: > > On 06/03/15 16:23, Ilya Kazakevich wrote: > > You may start from highest level testing: > > 1) create "usage scenarios" for your website. Like "customer opens page > > 'foo', and should see 'bar'". You use such scenarios

Tests failing after adding django-bower app

2015-03-09 Thread Kevin Ndung'u
I have a peculiar case where after adding the django-bower app to my Django project, all of a sudden my tests are failing on the CI server but they are passing when I run them locally. I have posted the details on Stackoverflow. Any help would be greatly appreciated.