#django

Why this is not working in my URLconf: photos/(category|categories)/

Isam_: define "not working"

OK, here's the full line: url(r'^photos/(category|categories)/(?P<id>\d+)/(?P<slug>\w+)/$', 'photos.views.category'),

I want category and categories to lead to the same view

This is working: url(r'^photos/(category)/(?P<id>\d+)/(?P<slug>\w+)/$', 'photos.views.category'),

@Isam: in my case sth like that works: url(r'^auctions/(?P<type>solutions|knowledge)/$', 'auction_list',

mlavin: how do you mean?

its directly under the static dir

amr: is that static directory in one of the applications or included in the STATICFILES_DIRS setting?

Hi all. been googling for days and not finding a resolution...have python 2.7 and django 1.4.2 setup and python is working fine. I do the >>import django and that's fine. I do >>print(django.get_version()) and get 1.4.2 back.

anyone familiar with south have an idea how I can convert a column to a new data type and the data that it contains?

I then try to run django-admin.py startproject mysite and get a syntax error

Help!!

Why would I be getting that syntax error?

luxgeek: how do you try?

(following the instructions from: https://docs.djangoproject.com/en/dev/intro/tut...)

paste the console session on dpaste

From a python command prompt.

Stand by

that's incorrect

do it from a terminal

not from a python shell

the new class based view documentation doesnt seem to have any support (like the function based views did) for sending a specific mimetype… is this right, or is the documentation just missing this??

Here is the dpaste: http://dpaste.com/820936/

bahamas: I WAS in a terminal, at the prompt, I type python and press enter to get into an interactive python env as the instructions say

-.-

er...

django-admin.py startproject myapp

from terminal not python as bahamas said

luxgeek: I'm looking at the instructions about creating a project and it doesn't say anything about entering the python shell

luxgeek: firstly, you should be using https://docs.djangoproject.com/en/1.4/intro/tut...

SmileyChris: yeah, he just linked that, but he's confused

no he didn't

he linked to /dev/

ah, I missed the difference

but yes, the bigger issue is that luxgeek doesn't seem to actually be following the tutorial :P

okrutny: So far it hasn't mattered what project name I've used, I get the same error

luxgeek: we're still waiting to see what the error is

luxgeek: as has been said already, you don't run it from a python interpreter - just your standard command line

ah, i see where it says about entering the interpreter

I've often thought it would be better to default to the most recent stable version rather than dev of the django docs. Make it an explicit choice to see the dev docs. Too many issues seem to arise related to that… ;)

but yeah, exit that once you have verified django is installed

exit

jaddison: it does

jaddison: but i don't think the bottom right is anywhere near the right place to put the version switching

SmileyChris: Only if you go directly to docs.djangoproject.com

jaddison: or if you click "documentation" in the header from any page of dp.com

if you google for "template tags django", it will take you to the dev docs.

jaddison: so do some kind of cookie test? sounds messy

I didn't say it would be pretty… ;)

But it would lead to less confusion.

the new class based view documentation doesnt seem to have any support (like the function based views did) for sending a specific mimetype… is this right, or is the documentation just missing this??

Just prevent search engines from indexing dev docs?

perhaps if it says "?from=olddocs" redirect

hehe

mlavin: pardon?

oh, no

i'm not sure why google is so crazy about that

its in the same place as the media dir is

lol, it's been like that for about 5 years

olddocs. They just get better with age.

amr: well that's not a good place for them

i have manage.py in /x/ and static is under /x/static

and /x/media

is that an unsuitable location?

well no, that's fine

but how does django know about /x/static?

STATIC_ROOT and MEDIA_ROOT

nope

anything ending in _ROOT is an end-point -- not somewhere where you should put files directly

you want STATICFILES_DIRS

oh, interesting

bugger.

what's the purpose of STATIC_ROOT then?

collection point for your static files

OH

across apps & project

this is not #matplotlib, but there may be more matplotlibbers around than in #matplotlib right now; i try to animate a scatter plot (multiple clusters in one scatter plot; each cluster is represented as a group of points with the same color); this is my current, disfunctional, approach: http://bpaste.net/show/EAMrkHckxhH3FFb9Lzfr/ it tries to animate just *one* cluster for now; but extending it to animate multiple subplots should be trivi

ahh, that makes sense

what on earth

amr: runserver doesn't need it though

but it gives your real web server somewhere to serve static files from

wron channel, very sorry!

*wrong

SmileyChris: that makes sense

thanks :)

amr: no probs - it's a common confusion point

is there a way to send data to the page from a view, w/o refreshing?

Comet?

exit2: Pulling from the client with ajax is somewhat simpler, but it's possible.

mattmcc: I'm making a tic tac toe game and it's currently sending over the which box is clicked by the player and I want to be able to send back over a move from the AI. I think it would pretty elite if it didn't refresh :\

maybe socket.io

ah bugger SmileyChris, im seeing the same issue

404 on /static/app.css

amr: i actually came in in the middle of your discussion - could you summarize your issue again please?

How can I access mydict.key if key is mymodel.somefield ? mydict.mymodel.somefield does not work; mydict[mymmodel.somefield] does not work...

im getting a 404 on static files i know to be there

this is my setup:

ah, hang on i see an error

:)

hurrah!

i had site_root in staticfiles_dirs

thanks for the help :)

is there a reason why isinstance wouldn't work in django 1.4?

Considering it's a Python builtin, no.

i snuck in "isinstance = lambda *x: False" in a recent commit just to confuse you :D

mattmcc: thanks!

SmileyChris: this is an issue adopting some code from 1.1...

brainwarped: could you give some details regarding your issue?