Re: django-voting
I see. Thanks for the response. I appreciate it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Different behaviour for url parameter in dev run versus test run
are u using windows? On Nov 18, 2007 12:41 AM, Manoj Govindan <[EMAIL PROTECTED]> wrote: > > My application has a view that accepts a string parameter and filters > a model based on that parameter. In the development environment the > view works well when passed a string with a space in it, say 'hello > world'. The portion of the url representing the parameter shows up as > 'hello%20world'. > > I then wrote a test for the view using Django's test client. I used > the utility reverse() method to pass the path to Client().get(). The > test failed (the query set was empty) for the very same string. > > Puzzled, I added a print statement inside the view to print the > parameter. When accessed in the development environment the parameter > showed up as 'hello world'. However on running the test it showed up > as 'hello%20world'. The latter caused the database lookup to return > empty. > > Can anyone explain why there is such a difference in behaviour? > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Training/Projects on Bioinformatics, Biotechnology And SAS Programming at Global Institute of Biotechnology
SAS FOR LIFE SCIENCES SAS (statistical analysis systems) is business intelligence software used for data analysis by more than 40,000 customers worldwide. SAS provides many solutions for life sciences including: * Optimization of the flow of Scientific Data * Integration of molecular information with clinical outcomes * Building a centralized, searchable repository of all research information * Compliance with regulatory requirements * Assessment of safety and effectiveness of new therapies * Management of Data from various sources like Electronic Data Captures (EDC), In House Clinical Data Management System (CDMS) and Contract Research Organizations (CROs) * Generation of Presentation-Ready Statistical Summaries of Clinical Trial and other Biomedical Research Data. The Data Analysis and Reporting Tools of SAS are already the Defacto Standards among Pharma Companies and other Life Science Industries. USFDA Cosiders SAS Validation as an important Component of Quality Assurance, Reliability and Accuracy of Information for the Approval of New Drugs. This Course will mainly focus on Statistics, Quantitative analysis, Research Design, and Data management, Data Analysis relating to Life Sciences. SAS is considered as the "gold standard" in many fields, particularly in Medical Research and Drug Development. Many find that SAS has a significant learning curve and is perhaps best learned as part of a course or through interactive lessons rather than through self-study. With SAS, we can dramatically improve your data analysis capabilities and processes, of ready-to-use statistical analysis procedures and rich, built-in graphical functionality to reveal relationships and correlations not readily apparent in spreadsheet applications. It saves time and expenses associated with data manipulation. This Course also introduces the concept of SAS in life sciences and also covers Live Projects on Techno-Functional and Functional Modules. This Course Aims at Creating Man Power in this Hi-Tech ever growing and much needed area, who can play a professional role at National and International level. These Professionals can also enjoy an unique, Challenging and Profitable Job Profiles. Personal Trained in this Field will be involved in: * Statistical Analysis of Clinical and Research Data using SAS SoftWare. * Prepare Custom derived SAS Data Sets. * Help ion Programming for New Drug Applications(NDAs). * Preparing repots for Drug Development (Phases I - IV). SAS9.1.3 CONTENTS DURATION: THREE MONTHS Module:1 BASE /SAS �� INTRODUCTION TO SAS PROGRAMMING �� IMPORTANCE OF SAS FOR LIFE SCIENCES �� CREATING SAS/LIBRARIES AND DATASETS �� READING DATA TO DATASETS �� CREATING PERMANANT LIBRARIES IN SAS ENVIRONMENT �� READING EXTERNAL SOURCE DATA TO SAS DATASETS �� WRITING SAS DATATO EXTERNAL SOURCES �� IMPORTING AND EXPORTING OF DATA �� FORMATS AND INFORMATS �� CONDITIONAL STATEMENTS �� AUTOMATIC VARIABLES �� POINTERS �� READING RAW DATA �� CLEANING OF DATA �� SAS/ODS �� DDE �� ARRAYS BASE SAS PROCEDURES: �� PROC PRINT �� PROC OPTIONS �� PROC SORT �� PROC APPEND �� PROC TRANSPOSE �� PROC FORMS �� PROC REPORT �� PROC TABULATATE �� PROC IMPORT �� PROC EXPORT �� PROC INFORMATS �� PROC FORMATS �� PROC PRINTTO �� PROC GCHART �� PROC CHART Module:2 SAS/MACROS �� INTRODUCTION TO MACROS �� STATEMENTS IN MACROS �� % PUT, % LET �� % SYMBOLGEN �� % MPRINT �� % MEND �� NESTED MACROS Module:3 SAS/CONNECT Module:4 SAS/ACCESS Module:5 SAS/SQL: (PASS THROUGH FECILITY) �� ORACLE �� CREATING DATASETS BY USING SAS/SQL �� UPDATE �� MERGE �� DELETION �� MODIFYING THE DATASETS Module:6 SAS/STAT �� INTRODUCTION TO STATISTICS �� IMPORTANCE OF STATS TO LIFE SCIENCES �� IN SAS/STAT/PROCEDURE �� PROC FREQ �� PROC RANK �� PROC CORR �� PROC Z-TEST �� PROC MEAN �� PROC REGRESSION �� PROC T-TEST �� PROC ANOVA �� PROC GLM Module:7 SAS/QC �� CLEANING OF CLINICAL TRIAL DATA �� INTRODUCTION TO CLINICAL TRALS �� DOCUMENTATION �� SAP INTRODUTION �� IMPORTANCE OF BIOSTATISTICS �� ICH AND GCP GUIDELINES �� IMPORTANCE OF SAS FOR REGULATORY AFFAIRS �� ANALYSIS OF CLINICAL TRIALS RESULTS Module: 8 SAS/ETL �� CONNECTING TO WARAHOUS ADMINISTRATORS �� CONNECTING TO DRACLE DATABASE Module:9 SAS/GENETICS Address: Global Institute of Biotechnology, 3-6-276/2, Above Mahesh Bank, Himayat Nagar, Hyderabad-29. WWW.globalbiotek.net [EMAIL PROTECTED] Contact No: Ph: 040-66621528 093910 05048 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users"
Re: Custom commands on win32 vs. BSD
On 11/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > A bit of digging revealed that the project's parent directory is > getting removed from sys.path, so the import of myproj.core.management > fails (INSTALLED_APPS has "myproj.core" in it). > > I had to add ".." to sys.path at the top of manage.py to get it to > work correctly. > > Did I do something wrong? While including the project name as part of an INSTALLED_APPS entry is legal, it isn't recommended. Malcolm recently did a good job explaining why in his blog: http://www.pointy-stick.com/blog/2007/11/09/django-tip-developing-without-projects/ If you refactor your code so that you install 'core', rather than 'myapp.core', you should find that this problem goes away. Yours, Russ Magee %-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Apache mod_python config problem
On Nov 18, 2:24 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Thanks for the help. I didn't think about checking permissions. I > have the site working now and I think it was a combination of > permissions and file paths. Here's the httpd.conf file that works: > > > ServerName music.sensiblestaffing.com > DocumentRoot/home/published/www/django/ > SetHandler python-program > PythonHandler django.core.handlers.modpython > PythonDebug On > PythonPath "['/home/published/www/django', '/home/ > published/www/django/musicshare', '/usr/lib/python2.5'] + sys.path" > SetEnv DJANGO_SETTINGS_MODULE musicshare.settings > > > In PythonPath, removing the trailing slash seemed to correct the last > issue I had. I also noticed that www-data must be the owner of the > files with 755 permissions. It also helped to remove all of the .pyc > files before restarting apache. A trailing slash on entries in PythonPath shouldn't really have made a difference. A concern though is why you have /usr/lib/python2.5 listed in PythonPath as it shouldn't be required and could cause problems if that isn't actually the version of Python that mod_python was compiled for. Also, www-data doesn't need to be the owner of any files provided that files were readable to other (o+r) and directories were readable and searchable to others (o+rx). The only time that www-data would need to be owner is where it might need to modify files. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Apache mod_python config problem
Thanks for the help. I didn't think about checking permissions. I have the site working now and I think it was a combination of permissions and file paths. Here's the httpd.conf file that works: ServerName music.sensiblestaffing.com DocumentRoot/home/published/www/django/ SetHandler python-program PythonHandler django.core.handlers.modpython PythonDebug On PythonPath "['/home/published/www/django', '/home/ published/www/django/musicshare', '/usr/lib/python2.5'] + sys.path" SetEnv DJANGO_SETTINGS_MODULE musicshare.settings In PythonPath, removing the trailing slash seemed to correct the last issue I had. I also noticed that www-data must be the owner of the files with 755 permissions. It also helped to remove all of the .pyc files before restarting apache. Maybe this will help someone else in the future... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: more info when serializing
> You could use a objects.values(...) which return a dictionary if I > remember > correctly, and then simplejson.dumps... I'll play with this and see how it works out tomorrow Thanks --B --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: more info when serializing
> The serializer doesn't support this. It would take a bit of design work > to figure out how to specify such an extension easily. You might like > put some thought into that, though. For my specific case, I wrote a custom serializer, extending the current json one, that added the additional info I want from User. It won't deserialize properly, but I don't care for this application. I put a bit of thought into it this afternoon, and I may play around with seeing if any of them would actually work. What I have is good enough for me in this particular case, but again it's little more than a hack, and certainly not something that should be merged in anywhere 8) Thanks --B --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: more info when serializing
You could use a objects.values(...) which return a dictionary if I remember
correctly, and then simplejson.dumps...
Ben
On 18/11/2007, Bryan L. Fordham <[EMAIL PROTECTED]> wrote:
>
>
> So, say I have a model something like this:
>
> class Bar(models.Model):
> user = models.ForeignKey(User)
> name = models.CharField(maxlength=50)
> description = models.TextField()
>
> where user is tied to a django.contrib.auth.models.User entity. When I
> serialize this to json, I get:
> [{"pk": "1", "model": "foo.bar", "fields": {"description": "", "user":
> 1, "name": "Phone"}}]
>
> Which is fine, but I need both the username and user id on the front
> end. Is there a simple way to get this info all in one shot that I'm
> just missing?
>
> Ideally, it would return something like: ..."user":
> {"username":"bfordham", "pk":1}...
>
> I'm using the django-rest-interface, if that makes a difference one way
> or the other.
>
> Thanks
> --B
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+6281317958862
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: more info when serializing
On Sat, 2007-11-17 at 16:21 -0500, Bryan L. Fordham wrote:
> So, say I have a model something like this:
>
> class Bar(models.Model):
> user = models.ForeignKey(User)
> name = models.CharField(maxlength=50)
> description = models.TextField()
>
> where user is tied to a django.contrib.auth.models.User entity. When I
> serialize this to json, I get:
> [{"pk": "1", "model": "foo.bar", "fields": {"description": "", "user":
> 1, "name": "Phone"}}]
>
> Which is fine, but I need both the username and user id on the front
> end. Is there a simple way to get this info all in one shot that I'm
> just missing?
>
> Ideally, it would return something like: ..."user":
> {"username":"bfordham", "pk":1}...
The serializer doesn't support this. It would take a bit of design work
to figure out how to specify such an extension easily. You might like
put some thought into that, though.
Things that immediately spring to mind as requiring addressing:
- what should the format look like for many-to-many objects (and
making sure we can deserialise as well)
- once you add one level of indirection, it will take
approximately 8 seconds for somebody to want to go two levels
and more. So it should be extensible beyond just "the immediate
foreign key relative".
- reverse relations
- deserialisation, if possible.
- is it easy to say "all the normal fields plus these extra
ones".
- could passing a ValuesQuerySet to the serializer, together
with #5768 be a solution in some fashion (as a way of specifying
these extra fields)?
I don't know how easy this would all be or how genuinely useful. Could
be worth a bit of thinking, though.
Malcolm
--
I just got lost in thought. It was unfamiliar territory.
http://www.pointy-stick.com/blog/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
How to handle differing timezones?
I'm curious how others handle the ever-annoying issue of timezones. Our Django app, running Django trunk/MySQL 5.0 on FreeBSD, has to handle multiple time zones. Each user has his/her own time zone set. Currently, I have middleware that sets os.environ["TZ"] to their time zone, followed by a call to time.tzset(). Models are defined with DateTimeField defaults set to datetime.utcnow. The problem is that it doesn't seem to be working as I had hoped. Some datetimes display correctly, some don't, and some get inserted funny. I have a feeling it may be due to Django or MySQL's handling, but I'm not entirely sure. The only thing I think might fix this is re-casting every datetime as it is displayed using a custom template filter that pulls the variable from the environment, or using a template tag to get the TZ from the RequestContext, but that seems like a lot of overhead that is duplicating handling that seems to already be there. Any tips? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Understanding autoescape-aware filters
On Sat, 2007-11-17 at 20:49 +0300, Ivan Sagalaev wrote:
> Hello!
>
> I'm about to convert my apps to play well with recently introduced
> autoescaping but I have to confess that I don't get mark_safe, is_safe
> and needs_autoescaping.
>
> First, I don't get why .is_safe attribute is needed at all. If my filter
> returns any HTML I should escape it and mark_safe the result, no?
The is_safe attribute is a large time-saver when you're writing filters.
Normally, you'll just want auto-escaping behaviour to be applied
automatically and when writing a filter that doesn't add raw HTML markup
you should be able to just write the code without having to worry about
escaping. The only difficulty is when you pass a safe string into the
filter. It's very easy to end up with a result that isn't a SafeData
instance after a few string manipulations, so this isn't a trivial
issue. For many filters, the actions they perform won't remove that
safe-ness in effect, but they won't be a SafeData isntance. So Django
notes that the input was a SafeData and the function is marked is_safe
and, thus, it calls mark_safe() on the result so that you don't have to
in your filter (all other input is automatically escaped at the right
moment, since it isn't safe from further escaping).
Thus, is_safe: if True, you are are guaranteeing a safe input string
will always generate an output string that can be marked as safe (and
Django will automatically do that for you). If not True, it is up to you
to either mark the output safe manually or have it auto-escaped when
auto-escaping is in effect.
> Then, looking at default filters I see that .is_safe is set to False for
> all filters returning non-string values. Though these values are pretty
> safe for HTML when they would be converted into strings in the end.
For filters returning non-strings, is_safe is a no-op, so I just picked
a value. The reason False is better than True is because you don't even
have to bother adding is_safe to those types of filters ("absent"
defaults to False). Adding it won't harm anything, though.
> And 'needs_autoescape' escapes me absolutely... If I'm dealing with user
> content and HTML why, again, can't I escape it inside my filter's code
> and mark_safe it?
Because you wouldn't be able to write a filter that worked correctly in
both auto-escaping and non-auto-escaping environments, which is a
compulsory requirement in most cases. You don't want to escape inside
the filter if the current context doesn't have auto-escaping in effect.
The needs_autoescape attribute tells Django that your function needs to
be passed a parameter called "autoescape" that is the value of the
current auto-escaping effect (True or False).
Yes, you can ignore needs_autoescape if you're going to restrict your
filters to only working in an auto-escaping environment, but that's
highly non-portable (and certainly not an option in Django's core, for
example). Anybody distributing an application, for example, that was
designed to work with other peoples' templates and didn't allow for
auto-escaping to be either True or False at render time would have a bug
in their code.
> Anyway... Malcolm (as the main implementer), sorry, but the docs are
> written in Linux how-to style: "make these magic passes and hope for the
> best and don't try to understand the thing since you never will".
A little bit hyperbolic, even for somebody who's frustrated. It is never
the intention to say "you'll never understand this" and the current
documentation does not even come close to saying that. When writing
feedback, as welcome as it is, try to have some respect for the insane
number of hours that have gone into developing this and the amount of
nonsense it's generated. Consider, also, that documentation written by
the person doing the design and implementation offer does sometimes miss
some of the easier things because they're too easy by the time it's at a
state where the documentation is written and that person is too close to
things. This is just part of the ironing out problems phase.
Given the types of things people complain about not understanding in the
documentation (we always get requests to add things that are effectively
"warning: Python will behave as it normally does and gravity has an
effect on this planet."), if we go into all the fine details of how
things work, the effect gets lost in the implementation. So there's a
limit. Apparently you feel I've fallen short here, but it's going to be
very difficult to find the middle ground.
I'll have one more pass at it and after that I look forwards to reading
your patch to improve things.
> For example. I'm writing a filter that gets a string and wraps it's
> first letter in a I'm going to split the first letter,
> conditional_escape the letter and the rest, wrap a letter in ...,
> concatenate and mark_safe. Now, should I stick .is_safe?
If you're always returning a safe string, then adding is_safe is a
no-op. The is_safe
Re: Understanding autoescape-aware filters
On 11/17/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > > Hello! > > I'm about to convert my apps to play well with recently introduced > autoescaping but I have to confess that I don't get mark_safe, is_safe > and needs_autoescaping. I'm also just getting started on learning this, but feel like I've got a reasonably good understanding from the docs and a bit of looking at the code, so I'll take a stab at answering. First, I don't get why .is_safe attribute is needed at all. If my filter > returns any HTML I should escape it and mark_safe the result, no? >From reading the doc, I got the impression that is_safe is for filters that don't mark_safe their output, but that also do not do anything to introduce anything "unsafe" in their output. Therefore, if they are given a safe string on input, their output will be automatically marked safe. Setting is_safe to True for a filter that always mark_safe's its output appears to be a no-op -- the framework will call mark_safe a 2nd time on something that has already been marked safe, which is harmless. However, there are a few filters in defaultfilters.py that do in fact always return mark_safe'd output but also have is_safe set to True. I don't understand what that accomplishes so perhaps I am missing something here. Then, looking at default filters I see that .is_safe is set to False for > all filters returning non-string values. Though these values are pretty > safe for HTML when they would be converted into strings in the end. But they are not returning strings, they are returning ints (or lists, or whatever). If is_safe was set to True for these filters, then their output would automatically be marked safe whenever they were called with safe input, meaning whatever they were returning would be turned into a (safe) string, changing the type of their output. is_safe=True is for filters that return strings, not numbers or whatever else. And 'needs_autoescape' escapes me absolutely... If I'm dealing with user > content and HTML why, again, can't I escape it inside my filter's code > and mark_safe it? You said "dealing with user content", so you have in your mind that input your filter is given must be escaped. What if you were writing a filter that could operate on either user-generated (untrusted) input that does need to be escaped or trusted input that may contain HTML and should not be escaped? That's what needs_autoescape is for. It's for filters that are going to mark_safe their output but need to know whether or not their input should be escaped as they process it. They're producing something that will be exempt from further escaping, so they need to know the current autoescape setting in order to determine whether their input should be escaped as it is incorporated into their output, because this is that last chance for getting it escaped. > [snip] > > For example. I'm writing a filter that gets a string and wraps it's > first letter in a I'm going to split the first letter, > conditional_escape the letter and the rest, wrap a letter in ..., > concatenate and mark_safe. Now, should I stick .is_safe? Because yes, I > think it will return safe output given a safe string. What will break if > I didn't (my experiments so far show that nothing breaks). Should I also > ask for autoescape parameter and how am I supposed to use it? As I mentioned above, I don't believe it is necessary to set is_safe to True for a filter that mark_safe's it output, but I might be missing something there. As for whether you need to ask for autoescape -- is there any use case for your filter where its input could contain HTML that should not be escaped? If so, then you should ask for autoescape and only escape the input you are given if autoescape is on. Anyway, that's my take on it. Malcolm can correct where I've gotten things wrong. Cheers, Karen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Does Hostmonster support Django?
here is hostmonster's response about mod_python and django: >We don't have mod_python installed, nor will we install it for anyone. >We don't officially support django, but we've had many customers run/install >it successfully using fastcgi. On Nov 12, 6:57 pm, Evgeny <[EMAIL PROTECTED]> wrote: > hostmonsterallows ssh access, so you should be able to install django > by yourself. > I have not verified whether they have mod_python, but there is python > installation. > > when I asked them to install python Imaging library - they refused. > Told me that their policy is not to install extra libraries, but you > should be able to do that in your user space. > Evgeny. > > On Nov 11, 5:50 pm, Hannus <[EMAIL PROTECTED]> wrote: > > > Hi guys, > > I am going to buy the host services in host monster,does it support > > Django? If not, plz advice me some other hosting companies. > > Thank you very much > > > Kind regards, > > Hannus --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: GeoDjango: Can't find libraries and geos errors
> On OS X, using MacPorts, ctypes doesn't look in /opt/local/lib unless > you set LD_LIBRARY_PATH. On Ubuntu Feisty, the gdal package uses a > weird naming convention and isn't found. Is it possible to specify > these library locations in settings.py or somewhere? There are no explicit settings for the location of the library -- however that is a good idea, and I'll look into implementing it. I usually set the LD_LIBRARY_PATH in circumstances where the library is in a nonstandard location, so this strategy should work on Ubuntu as well. An interim solution would be to hard-code the library location by changing the variable `lib_name` in django/contrib/gis/geos/libgeos.py (similarly, GDAL's library name is in gdal/libgdal.py). > Also, on both OS X and Ubuntu, I get symbol not found errors for > GEOSCoordSeq_getOrdinate when trying to import the geos tests (see > below). You are using GEOS 2.2.x, and GeoDjango requires GEOS 3.0 and above. I know this because there's an improper forward function declaration for GEOSCoordSeq_getOrdinate in the 2.2.x versions, and the routine does not get exposed in the shared library. I'm not sure if there are binary packages available on Linux and/or OSX for 3.0 -- your best bet for these platforms is to compile GEOS from source. For maximum compatibility please follow the installation instructions on the trac wiki: http://code.djangoproject.com/wiki/GeoDjangoInstall I have a hunch that compiling GEOS and GDAL from source and installing in /usr/local may eliminate the need for modifying the source files as discussed above. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Forget about burning CDs and using expensive overnight courier.
Forget about burning CDs and using expensive overnight courier. Send, Track and Receive files with YouSendIt. Start Your FREE Trial! Get Free Code: Limited Time Only! http://www.tkqlhce.com/click-2667396-10501907 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
more info when serializing
So, say I have a model something like this:
class Bar(models.Model):
user = models.ForeignKey(User)
name = models.CharField(maxlength=50)
description = models.TextField()
where user is tied to a django.contrib.auth.models.User entity. When I
serialize this to json, I get:
[{"pk": "1", "model": "foo.bar", "fields": {"description": "", "user":
1, "name": "Phone"}}]
Which is fine, but I need both the username and user id on the front
end. Is there a simple way to get this info all in one shot that I'm
just missing?
Ideally, it would return something like: ..."user":
{"username":"bfordham", "pk":1}...
I'm using the django-rest-interface, if that makes a difference one way
or the other.
Thanks
--B
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: advice on template shortcomings
You don't need the development version. You should be able to do
something like:
{% for item in mydict.items %}
the key: {{ item.0 }}
the value: {{ item.1 }}
{% for subitem in item.1 %}
{{ subitem }}
{% endfor %}
{% endfor %}
While not as pretty as the development version of dictionary
iteration, it's still useful.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: advice on template shortcomings
>
> Note I am using 0.96, the production distro.
The ability to iterate through dictionaries is only available in the
*development* version.
Documentation URL:
http://www.djangoproject.com/documentation/templates/#for
>From the django site:
This can also be useful if you need to access the items in a
dictionary. For example, if your context contained a dictionary data,
the following would display the keys and values of the dictionary:
{% for key, value in data.items %}
{{ key }}: {{ value }}
{% endfor %}
Hope this helps.
Manoj
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: advice on template shortcomings
Great! I hope you can tell me what I'm doing wrong. Here's the
template:
{% for k, v in thedict.iteritems %}
{{ k }}, {{ v }}
{% endfor %}
{% for a1, a2 in thelist %}
{{ a1 }}, {{ a2 }}
{% endfor %}
and the views' index function
def index(request):
thedict = {'a': '1', 'b': '2' }
thelist = [ '1', '2', '3', '4' ]
c = Context({'thedict': thedict, 'thelist': thelist })
return HttpResponse(t.render(c))
the error I get is
"'for' statements with five words should end in 'reversed': for k, v
in thedict.iteritems"
If I remove the space after the comma between k and v, I dont get the
error message but all I see are commas on the rendered page. This is
the simple case. I was hoping to do
[ a, [ a1, a2, ...], b, [b1, ...], ... ]
where each object is a form. The a form has a list of a# forms, the b
form has a list of b# forms, and so on; the number being dynamic.
Note I am using 0.96, the production distro.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Understanding autoescape-aware filters
SmileyChris wrote: > It's explained here: > http://www.djangoproject.com/documentation/templates_python/#filters-and-auto-escaping Yes, I've asked the group after I've read those docs, twice :-). First time I thought that I was just slow but the second time I didn't understand again and asked for help... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Understanding autoescape-aware filters
On Nov 18, 6:49 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > the docs are > written in Linux how-to style: "make these magic passes and hope for the > best and don't try to understand the thing since you never will". Could > you please clarify why are those things needed and what exact effect > they are intended to cause? It's explained here: http://www.djangoproject.com/documentation/templates_python/#filters-and-auto-escaping Probably could be clearer, it's still an area that makes my head spin for a few minutes when I read it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: advice on template shortcomings
Ken wrote: > For instance, I > cant pass a dict or a list of lists to the template. Actually it's not true, you can perfectly pass and access dicts and lists and whatever in templates. Can you describe your specific case that didn't work? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
advice on template shortcomings
I'm using 0.96 and find django's templates very frustrating. While I find the ability to pass Python objects to the template and accessing object attributes or methods to be really nice, this feature does not extend to basic python objects like lists and dicts. For instance, I cant pass a dict or a list of lists to the template. Basically, I have to flatten everything out before passing them to the template. And, this is next to impossible if I have a dynamic number of objects to pass. I've resorted to rendering the entire page in Python. I'd like to hear other strategies people use to get around problems like this. You have all this powerful Python machinery only to be stymied by django's templates because it doesn't reflect the kinds of complex structures one can construct with Python. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Different behaviour for url parameter in dev run versus test run
My application has a view that accepts a string parameter and filters a model based on that parameter. In the development environment the view works well when passed a string with a space in it, say 'hello world'. The portion of the url representing the parameter shows up as 'hello%20world'. I then wrote a test for the view using Django's test client. I used the utility reverse() method to pass the path to Client().get(). The test failed (the query set was empty) for the very same string. Puzzled, I added a print statement inside the view to print the parameter. When accessed in the development environment the parameter showed up as 'hello world'. However on running the test it showed up as 'hello%20world'. The latter caused the database lookup to return empty. Can anyone explain why there is such a difference in behaviour? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Understanding autoescape-aware filters
Hello! I'm about to convert my apps to play well with recently introduced autoescaping but I have to confess that I don't get mark_safe, is_safe and needs_autoescaping. First, I don't get why .is_safe attribute is needed at all. If my filter returns any HTML I should escape it and mark_safe the result, no? Then, looking at default filters I see that .is_safe is set to False for all filters returning non-string values. Though these values are pretty safe for HTML when they would be converted into strings in the end. And 'needs_autoescape' escapes me absolutely... If I'm dealing with user content and HTML why, again, can't I escape it inside my filter's code and mark_safe it? Anyway... Malcolm (as the main implementer), sorry, but the docs are written in Linux how-to style: "make these magic passes and hope for the best and don't try to understand the thing since you never will". Could you please clarify why are those things needed and what exact effect they are intended to cause? For example. I'm writing a filter that gets a string and wraps it's first letter in a I'm going to split the first letter, conditional_escape the letter and the rest, wrap a letter in ..., concatenate and mark_safe. Now, should I stick .is_safe? Because yes, I think it will return safe output given a safe string. What will break if I didn't (my experiments so far show that nothing breaks). Should I also ask for autoescape parameter and how am I supposed to use it? Ok, this was a bit messy but I honestly thought it should be easier :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: URL/Request Question
On Nov 17, 4:33 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Fri, 2007-11-16 at 19:19 -0800, [EMAIL PROTECTED] wrote: > > > On Nov 17, 4:15 am, Malcolm Tredinnick <[EMAIL PROTECTED]> > > wrote: > > > On Fri, 2007-11-16 at 19:04 -0800, [EMAIL PROTECTED] wrote: > > > > [...] > > > > > Is there a way to have access to exactly the url used for the request? > > > > Seehttp://www.djangoproject.com/documentation/request_response/#methods > > > > Looking at the documentation for the "request" object would seem to be > > > an obvious first place to look here. And, sure enough, get_full_path() > > > is documented there. > > > > Malcolm > > > > -- > > > Honk if you love peace and quiet.http://www.pointy-stick.com/blog/ > > > That's where I started but if I do a request for > >www.example.com/test/? > > the get_full_path() returns > >www.example.com/test/ > > which isn't what we are needing in this situation, I am looking for > > exactly what was requested through the url. > > Ah, I see. Then you're doomed. The interface to the web server might not > be passing through enough information for this to be determined. So any > way to do this is going to be very dependent on how you are interacting > with the web server. > > Try poking around inside request._req if you're using mod_python or > request.environ if you're using the WSGI handler and maybe you'll get > lucky, but I doubt it (particularly with WSGI, you're not going to be > able to tell the difference between an empty query string and an omitted > query string). > > Malcolm > > -- > Atheism is a non-prophet organization.http://www.pointy-stick.com/blog/ Your right that it doesn't look promising with the WSGI handler, I do think that there is a possibility with the mod_python handler, we will see what happens. Thanks for your help. Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
HOTTEST PHOTO-SHOOTS OF THE SEXIEST MODELS N CELEBRITIES. GET THEM HERE
THE BEST SITES FOR THE NEWEST WALLPAPERS N GOSSIP N ALL THE OTHER HAPPENINGS IN BOLLYWOOD HOLLYWOOD N IN THE GLAMOROUS WORLD:- http://bollywood-dhamaal.blogspot.com/ http://comingup-bollywood.blogspot.com/ http://nasty-hollywood.blogspot.com/ http://fun-at-its-best.blogspot.com/ wanna earn money on any other kinda info abt how it works im jus a mail away!!! mail me at: [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Accessing request.user inside a model methods
http://lucumr.pocoo.org/blogarchive/why-i-cant-stand-threadlocal-and-others On Nov 17, 10:20 am, DanB <[EMAIL PROTECTED]> wrote: > Thxs Alex, > > really helpful info. > > Cheers, > DanB > > On Nov 16, 7:04 pm, Alex Koshelev <[EMAIL PROTECTED]> wrote: > > >http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser > > > On 16 нояб, 20:07, "Dan-Cristian Bogos" <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > Can anyone tell me if it is possible to access logged user instance > > > inside a model method, like save() is? > > > > I need to rewrite save() method, so I should have some automatic > > > triggers on model.save(), and use information inside > > > user.groups.all(). > > > > Ta, > > > DanB --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Sharding with Django
python orm sqlalchemy allows sharding. I would like to me sqlalchemy integrated into django. I am python noob, so I can't go around hacking the framework. I like django, but the whole framework is not decoupleable. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
HOTTEST PHOTO-SHOOTS OF THE SEXIEST MODELS N CELEBRITIES. GET THEM HERE
THE BEST SITES FOR THE NEWEST WALLPAPERS N GOSSIP N ALL THE OTHER HAPPENINGS IN BOLLYWOOD HOLLYWOOD N IN THE GLAMOROUS WORLD:- http://bollywood-dhamaal.blogspot.com/ http://comingup-bollywood.blogspot.com/ http://nasty-hollywood.blogspot.com/ http://fun-at-its-best.blogspot.com/ wanna earn money on any other kinda info abt how it works im jus a mail away!!! mail me at: [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: django-voting
On Nov 17, 2007 3:42 AM, tanukichan <[EMAIL PROTECTED]> wrote: > > When looking at the example given in the overview.txt file for django- > voting (http://django-voting.googlecode.com/svn/trunk/docs/ > overview.txt), they give the following: > > "Votes are recorded using the ``record_vote`` helper function:: > > >>> from django.contrib.auth.models import User > >>> from shop.apps.products.models import Widget > >>> from voting.models import Vote > >>> user = User.objects.get(pk=1) > >>> widget = Widget.objects.get(pk=1) > >>> Vote.objects.record_vote(widget, user, +1)" > > Where is the Widget class supposed to be imported from? I see the > path that they are defining, but the model doesn't seem to be > installed with django-voting or django itself. Is that a model and > class that I need to create myself? If so, can someone offer an > example of how to do this. > Widget here is just the example model they are recording votes for. Replace it with whatever model you want to record votes for. Karen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Accessing request.user inside a model methods
Thxs Alex, really helpful info. Cheers, DanB On Nov 16, 7:04 pm, Alex Koshelev <[EMAIL PROTECTED]> wrote: > http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser > > On 16 нояб, 20:07, "Dan-Cristian Bogos" <[EMAIL PROTECTED]> wrote: > > > Hello, > > > Can anyone tell me if it is possible to access logged user instance > > inside a model method, like save() is? > > > I need to rewrite save() method, so I should have some automatic > > triggers on model.save(), and use information inside > > user.groups.all(). > > > Ta, > > DanB --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Dynamically load objects
On 17 nov, 01:28, "Ramiro Morales" <[EMAIL PROTECTED]> wrote:
> On Nov 16, 2007 8:18 PM, Grupo Django <[EMAIL PROTECTED]> wrote:
>
>
>
> > Thanks a lot! get _model works.
> > Only one thing, I've been reading the code in te file django/db/models/
> > loading.py and I don't understand how it works, and now I need to know
> > or I won't sleep :-)
>
> > What should I do to reference stuff?
>
> > app = __import__('app_name',{},{},['models'])
> > mods = getattr(app,'models')
> > module = getattr(mods,'ModuleIWant')
>
> > This actually works, but I'm not sure if it's the right way or the
> > "python way".
>
> Do you want to reimplement or do you want to use
> get_model()?. If the answer is the latter you might
> find this article helpful:
>
> http://www.b-list.org/weblog/2007/nov/03/working-models/
>
> Regards,
>
> --
> Ramiro Morales
I'm using get_model, I just wanted to learn how it works. and if the
code I wrote was ok.
Thank you.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
django-voting
When looking at the example given in the overview.txt file for django- voting (http://django-voting.googlecode.com/svn/trunk/docs/ overview.txt), they give the following: "Votes are recorded using the ``record_vote`` helper function:: >>> from django.contrib.auth.models import User >>> from shop.apps.products.models import Widget >>> from voting.models import Vote >>> user = User.objects.get(pk=1) >>> widget = Widget.objects.get(pk=1) >>> Vote.objects.record_vote(widget, user, +1)" Where is the Widget class supposed to be imported from? I see the path that they are defining, but the model doesn't seem to be installed with django-voting or django itself. Is that a model and class that I need to create myself? If so, can someone offer an example of how to do this. -t --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
