Re: Ecommerce & Django

[bruno desthuilliers]

James Bennett wrote:
> On 4/13/06, Chris Moffitt <[EMAIL PROTECTED]> wrote:
> 
>>I like it.  However, it's probably a little limiting for future use.  One
>>question I have around the name Django.  I noticed on the website that
>>it's copyrighted so we probably couldn't use it in the name. Is that true?
> 
> 
> Minor nitpick: it's a trademark, not a copyright. In the United
> States, at least, names can't be copyrighted.
> 
> Also, in personal projects I tend to pick names of other jazz artists,
> following the trend of "Django" and "Ellington"... for example, I've
> got a project right now called "Coltrane".
> 

May I suggest 'Emmet' ? (Emmet Ray was a great guitarist and a huge fan
of Django)

My 2 cents...
-- 
bruno desthuilliers
développeur
[EMAIL PROTECTED]
http://www.modulix.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[olive]

+1 for python-hosting

My possible contributions:
- on-the-fly PDF invoice creation using ReportLab (or another PDF lib
?)
- Advertising management
- links with others Web Services (Amazon ...)
- The Shop as Web Service ...
...


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Understanding FloatFields

[Nebojsa Djordjevic]

DavidA wrote:
> Is the convention to just use float() or Decimal()
> whenever I need to use it as a number?

I'm not sure what is the final decision, but in my first try in implementing 
validate and to_python methods (in MR) I
use Decimal as return type for the FloatField.

OTOH, maybe we can use float return type for the FloatField (and maybe in db) 
and add DecimalField which will use
Decimal as base type. It will be less surprising.

-- 
Nebojša Đorđević - nesh
Studio Quattro - Niš - SCG
http://studioquattro.biz/
http://djnesh.blogspot.com/  |  http://djnesh-django.blogspot.com/ |  
http://djangoutils.python-hosting.com/
Registered Linux User 282159 [http://counter.li.org]

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Nebojsa Djordjevic]

Chris Moffitt wrote:
> There are certain problems with OsCommerce which are going to be
> non-issues with a Django site:

PHP-style of i18n handling, really a show stopper for me.

Django i18n rocks, but we must add l10n stuff also (money/number formatting, 
currency support, etc).

> Is there interest or any activity in this area?  I'm willing to hack
> through by myself but I think if there's anyone that is an expert, we
> could move through this a lot more quickly.

I'm willing to help, although I don't have lot's of experience in the 
e-commerce applications.

I have (a typical) on-line shop project in the near future so count me in.

Maybe we can create django-ecommerce mailing list for this?

-- 
Nebojša Đorđević - nesh
Studio Quattro - Niš - SCG
http://studioquattro.biz/
http://djnesh.blogspot.com/  |  http://djnesh-django.blogspot.com/ |  
http://djangoutils.python-hosting.com/
Registered Linux User 282159 [http://counter.li.org]

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[Kenneth Gonsalves]

On Thursday 13 Apr 2006 6:54 pm, Adrian Holovaty wrote:
> Depending on demand, we may release a final pre-magic-removal
> release of Django -- maybe 0.91.1 or something. Or maybe it'll be
> 0.92 and magic-removal will be 0.95, to signify it's a big leap.
> Thoughts?

next release *must* be magic removal - no point doing any interim 
releases - one drastic piece of surgery and then 1.0 ... interim 
releases would just prolong the agony

-- 
regards
kg

http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Kenneth Gonsalves]

On Thursday 13 Apr 2006 11:12 pm, Jeremy Jones wrote:
> What is it with wives and websites?  Anybody out there (who's a
> male married to a female) not building a website for his wife?

i build websites for me in my wife's name ;-)

-- 
regards
kg

http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Kenneth Gonsalves]

On Friday 14 Apr 2006 12:29 pm, James Bennett wrote:
> Also, in personal projects I tend to pick names of other jazz
> artists, following the trend of "Django" and "Ellington"... for
> example, I've got a project right now called "Coltrane".

jazz - django is a female western gunslinger - wonder if angelina 
jolie's image is copyrighted? (lara croft)

-- 
regards
kg

http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Michael]

http://dshop.mine.nu/shopworking now to setup trac
Michael



--~--~-~--~~~---~--~~
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  -~--~~~~--~~--~--~---

Re: What is the right order of LocaleMiddleware and CacheMiddleware?

[Beegee]

# CacheMiddleware settings
CACHE_BACKEND = "locmem:///"
CACHE_MIDDLEWARE_KEY_PREFIX = 'beegee'
CACHE_MIDDLEWARE_SECONDS = 60 * 5

MIDDLEWARE_CLASSES = (
"django.middleware.sessions.SessionMiddleware",
"django.middleware.locale.LocaleMiddleware",
"django.middleware.cache.CacheMiddleware",
"django.middleware.common.CommonMiddleware",
)

What ever the order of the middleware the CacheMiddleware does not
seems to work correctly with the LocaleMiddleware. I keep flipping
between different languages when switching between pages, while I did
not push any language buttons. Also, when I switched languages it more
than once does not switch at all.

Does anybody have any experience in enabling cache on a multi lingual
Django website?

Thanks!

Berry


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: possible to filter ManyToMany results?

[nkeric]

Ivan Sagalaev wrote:
> You might want to look into magic-removal branch where things like this
> are made possible with ORM.

Really? That's cool!

Our site (http://www.ifaxian.com - a Chinese Digg-like site) built upon
the svn trunk version, we're planning to migrate to the m-r branch
soon, I guess it's time for me to take a deeper look into the m-r
branch :)

Thanks a lot Ivan, you've been a great help ;)

- Eric


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: possible to filter ManyToMany results?

[Luke Plant]

On Wednesday 12 April 2006 07:03, nkeric wrote:
> hi all,
>
> I've done some search, however, I guess I should ask for your helps
> here:
>
> I have the following models: (pseudo code)
>
> class ArticleType:
> name = ...
>
> class Article:
> title = ...
> article_type = meta.ForeignKey(ArticleType)
>
> class Game:
> name = ...
> articles = meta.ManyToManyField(Article)
>
> how can I retrive the articles of a certain article type of a given
> game?
>
> >>> g = games.get_object(pk=1)
> >>> g.get_article_list(article_type_id__exact=1)
>
> doesn't work, though I knew how to do this in raw sql...

As I understand it, Django should be able to do this query no problem.  
I think there may be a mistake in what you posted though - IIRC, I 
would have expected the method name to be 'get_articles_list' not 
'get_article_list', since you defined it as 'articles = 
meta.ManyToManyField(Article)'.  If you post the entire code for your 
models we may be able to find the problem.  Magic-removal branch 
doesn't really change what is possible here, it just changes the 
syntax.

Luke

-- 
"Humiliation: The harder you try, the dumber you look." (despair.com)

Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: possible to filter ManyToMany results?

[Ivan Sagalaev]

nkeric wrote:

>Really? That's cool!
>  
>
Yes. One of the great new features of m-r branch is that relation 
queries work similary for M-M and 1-M relations and in both directions:

game.articles.filter(article_type__pk=1) # all articles for one game 
of one type
article.game_set.all() # all games from one article

and even

article.game_set.filter(article__article_type__pk=1)

... which gives all games mentioned in the article that was mentioned in 
other articles of certain type (though it's not very practicle :-) )

>Our site (http://www.ifaxian.com - a Chinese Digg-like site) built upon
>the svn trunk version, we're planning to migrate to the m-r branch
>soon, I guess it's time for me to take a deeper look into the m-r
>branch :)
>  
>
My advice is to making it sooner than later. I just killed the whole day 
yesterday refactoring my project (medium sized mp3 exchange service with 
wishlists, catalog, search and a blog) to magic removal. The most time I 
spent converting old SQL queries to new ORM calls. So the more old stuff 
you have the more you will have to convert.

If you fancy an example... To track downloads I have a DownloadLog table 
that basically just references Users and Albums with foreign keys. There 
was one query that selects "albums downloaded by users that have 
downloaded this album". In trunk version there was an SQL of two nested 
selects that looked pretty scary. Now it's just one line:


Album.objects.filter(downloadlog__user__downloadlog__album__pk=self.id).exclude(pk=self.id).distinct()

... which almost can be read in English ("albums in logs with users in 
logs with this album").

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

PostgreSQL Schemas.

[Ed Epstein]

Hi. I searched the archives and could find no real mention of this, so
I thought I'd post.

Can I specify specific Postgres schemas (e.g. database.schema.table) in
Django? Can I specify specific schemas when using the inspectdb
feature?

I'll poke around in the code and see if I can figure out where these
sorts of calls are made, but this will be the first time that I've
looked at the Django source, so I thought I'd just ask in case I can
get an answer here sooner.

--Ed


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: possible to filter ManyToMany results?

[Ivan Sagalaev]

Luke Plant wrote:

>As I understand it, Django should be able to do this query no problem.  
>  
>
I also thought so :-). I created a test project with this model and 
tried to get this query to work. "get_article_list" is indeed there but 
it doesn't like 'article_type__id__exact' as an argument.

I think this is a limitation of current trunk (may be a bug) that you 
can't have additional joins in selects from M-M relations.

But still, may be I just didn't search good enough...

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Importing external modules/classes

[DavidA]

Hi Cary,

What I did to avoid all the PYTHONPATH stuff was to just 'install' my
python library using distutils. I set up a trivial setup.py script and
then I just run 'python setup.py install' for my library whenever I
make changes.

from distutils.core import setup

setup(name='pf',
  version='0.1',
  packages=['pf', 'pf.utils', 'pf.task'],
)

While forgetting to install changes has tripped me up once or twice,
I've done this enought that its "wired" into my fingers now. While this
might seem a bit of overkill, using distutils is so simple that I don't
mind it.
-Dave


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Jeremy Jones]

On Fri, 14 Apr 2006 15:00:03 +0530
Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:

> 
> On Thursday 13 Apr 2006 11:12 pm, Jeremy Jones wrote:
> > What is it with wives and websites?  Anybody out there (who's a
> > male married to a female) not building a website for his wife?
> 
> i build websites for me in my wife's name ;-)
> 

Dude.  That was just wrong.  You're giving away geek trade secrets.  As
long as they don't know that we're building the sites for ourselves, we
score brownie points for the effort.  You'd better hope none of our
wives are reading, or we're done for.

- jmj

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Jeremy Jones]

On Thu, 13 Apr 2006 18:14:35 -0700
"ZebZiggle" <[EMAIL PROTECTED]> wrote:

> 
> How about "Reinhardt"?
> 
> Django's last name.
> 
+1 on reinhardt

- jmj

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Jeremy Jones]

On Fri, 14 Apr 2006 22:15:31 +1200
Michael <[EMAIL PROTECTED]> wrote:

> http://dshop.mine.nu/shop
> 
> working now to setup trac
> 
> 
> > Michael
> >

Looking forward to working on this.  Here's a rough sketch of what I
was planning on building (and have actually begun work on).  I don't
know if this will be palatable to any of the rest of you, or not.  My
main purpose for building this app was (and is) to provide cheap hosting
for an easy-to-use ecommerce site.  If what I'm working on can be of
use to the project we're talking about, I'm happy to contribute.

- User: I've started using Django's builtin User stuff to manage
users.  A user is a someone who manages one or more stores.

- Multi-store.  This is pretty self-evident.  Stores can have products,
product have a names, price, images, descriptions.  Probably ought to
have product categories in here on a per-store basis.

- Flexible product attribute management.  The base attributes that a
product should have are name and price.  But it would be nice to allow
store managers to create products with varying attributes.  For
example, a shirt could use a "size" attribute with a drop-down list of
"small", "medium", "large" whereas a coffee cup doesn't need that.

- per-store store management interface.  (Yes, I intended to put two
"stores" adjacent to one another.)  Right now, the Django admin
interface is not suitable for allowing multiple users to manage only
the stuff that belongs to them. This multi-user, multi-store site needs
an admin interface that will keep users from mucking with other users'
stores.

- Integration with a payment system.  I already have my wife's site
working with PayPal.  That was a snap.  I think it'd be great to come
up with a plugin system to allow integration with any payment system.

- Integration with shipping providers.

- Catalog upload.  It'd be cool to allow someone to upload a csv of
their products.  However, with "flexible product attribute management",
this may not really be that feasible.

- Tax calculation module.  Users should be able to create certain rules
for what rate to tax which items.  In the States, the rule would be
mostly determined by which state the order is coming from.

- Coupon system.  Users should be able to create coupon codes with an
expiration date, percent or absolute price discount, expire after N
number of uses.


I don't really need this, but it may be kind of cool:

- Inventory management.  Either totally manage inventory online, or
provide some mechanism for integrating with some inventory systems.


That's all I can think of for now.

- jmj

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Chris Moffitt]

> http://dshop.mine.nu/shop
>
> working now to setup trac
>

Michael -

Looks like a great start.  Do you want me to setup a mailing list?  We're
getting enough interest that I think it would make sense.  Give me the ok
& I can do it & send out an announcement to this list.

-Chris

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Chris Moffitt]

> I don't really need this, but it may be kind of cool:
>
> - Inventory management.  Either totally manage inventory online, or
> provide some mechanism for integrating with some inventory systems.
>
>
I agree with all the features/ideas you mentioned.  I have access to
Authorize.net so I can work to get a module setup there.  I also like your
idea of an inventory mgmt system.  If we can extend the inventory
capabilities to a little more than just tracking what was sold, I think
that could be a really nice advantage.  Obviously we need to make sure
this doesn't turn into a full-blown ERP system.

Hopefully we can get something setup here pretty soon & start channeling
this energy towards structuring the project.

-Chris

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Brice Carpentier]

On 4/13/06, arthur debert <[EMAIL PROTECTED]> wrote:
>
> "Setup a free python project on python-hosting.com"
>
> +1 on this one. when getting started we better focus on the coding
> right away, and python hosting's capabilities (svn + trac ) setup with
> no fuss will be very helpfull (it seems).
>
> " Any brilliant ideas?" not really...
>
wasn't there any Jazz artist that was known to be "too commercial" ?
I think that would suit the project just fine, wouldn't it ?

--
Brice Carpentier aka Br|ce

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Jeremy Jones]

On Fri, 14 Apr 2006 15:26:49 +0200
"Brice Carpentier" <[EMAIL PROTECTED]> wrote:

> 
> On 4/13/06, arthur debert <[EMAIL PROTECTED]> wrote:
> wasn't there any Jazz artist that was known to be "too commercial" ?
> I think that would suit the project just fine, wouldn't it ?
> 

Googling for '"too commercial" jazz' turns this up:

http://www.redhotjazz.com/louie.html

It's Louie "Satchmo" Armstrong.  I could go for Armstrong, but I think
"Satchmo" is cooler.

- jmj

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: PostgreSQL Schemas.

[Adrian Holovaty]

On 4/14/06, Ed Epstein <[EMAIL PROTECTED]> wrote:
> Can I specify specific Postgres schemas (e.g. database.schema.table) in
> Django? Can I specify specific schemas when using the inspectdb
> feature?

Postgres schemas aren't supported at the moment. (Not that we have
anything against them, just that we've never found a use for them.)
That said, we'd be happy to accept patches that add schema support!

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Wilson]

Call it "Brubeck"


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Jeremy Jones]

On Fri, 14 Apr 2006 22:15:31 +1200
Michael <[EMAIL PROTECTED]> wrote:

> http://dshop.mine.nu/shop
> 
> working now to setup trac
> 
> 
> > Michael
> >
> 
> 

I just put up what I've coded so far on
http://jeremy.pitterpatprints.com/

I just created that subdomain, so it's not in the DNS for work yet, but
it is from home.  I don't have a shopping cart built in there yet.
Another question is whether to allow products from multiple stores to
populate the same shopping cart instance.  I'd think not.

Anyway, this site is butt-ugly.  Nothing like the one Michael has put
up, but I hope it gets across some of my intentions.

- jmj


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[Jeroen Ruigrok van der Werven]

On 4/14/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> next release *must* be magic removal - no point doing any interim
> releases - one drastic piece of surgery and then 1.0 ... interim
> releases would just prolong the agony

I have to agree with Kenneth here.

Any day you prolong the non-MR use is going to come back later for
people who need to convert from one system to another.

Better to bite the bullet and get this over with.

The better question might be: is the current magic removal branch that
what you intend for a 1.0 version?

--
Jeroen Ruigrok van der Werven

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: PostgreSQL Schemas.

[Ed Epstein]

Well I managed to get introspectdb working with schemas, but I don't
know if it's the right solution. What I'm doing right now is modifying
the schema search path.

If you think it's a good idea, I'd probably suggest looking at adding a
per project per app setting that specifies a schema. It would need to
add the create schema statement during the initsql process. For
subsequent accesses, we would set the default search path for the life
of connection to match the schema specifed in the settings. Is this
worth pursuing?


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[arthur debert]

another thing that would be nice is a "downloadable type" of product
where the order relates to a download. of course, this could get pretty
complex if you add in things like serial numbers, versions, etc...but
we can start simple.I (personally) would like this, and I guess quite a
few of the early adopetrs migh want to sell software / digital goods (I
don't know, maybe their wife are selling e-books or something)


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[David S .]

Jeroen Ruigrok van der Werven  gmail.com> writes:

> On 4/14/06, Kenneth Gonsalves  thenilgiris.com> wrote:
> > next release *must* be magic removal - no point doing any interim
...
> Better to bite the bullet and get this over with.
...

I was thinking simultaneous release.  Really just for the sake of a label for
the pre-magic removal stuff.  This is not about "biting the bullet" or any of
that.  I am talking about projects that are complete and for which it would be
mighty convenient to have the last and best code to run on.  When it comes time
for rev 2, we'll be happy to move to 1.x or whatever Django is at.

Of course, it can always be fetched from SVN, it just feels better to have a
nice EGG for your disaster recovery stack.




--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Trunk and docs

[benchline]

Hi All,

Does anyone know if the docs in trunk are updated for all the changes
in the trunk since .91?

Thanks


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Jeremy Jones]

On Fri, 14 Apr 2006 15:22:53 -
"arthur debert" <[EMAIL PROTECTED]> wrote:

> 
> another thing that would be nice is a "downloadable type" of product
> where the order relates to a download. of course, this could get
> pretty complex if you add in things like serial numbers, versions,
> etc...but we can start simple.I (personally) would like this, and I
> guess quite a few of the early adopetrs migh want to sell software /
> digital goods (I don't know, maybe their wife are selling e-books or
> something)
> 

{% block run_for_your_life %}
So which DRM mechanism should we use?
{% endblock %}

Just kidding.  I think this is a great idea.  This could be handled
a couple of ways.  If you want immediate download upon completion of
payment, it'd have to be a there'd have to be a product type column so
and we'd need a way to distinguish what needs to happen with different
product types.  Something I had thought about but failed to mention in
my ideas is a checkout sequence.  I think it'd be nice to be able to
specify on a per-product basis what order of pages the buyer should
traverse when they checkout.  This could just tie directly into that.
Maybe have some canned product types and have them associated with a
their own checkout sequences.

Another way this could be handled is through a shipping/order
fulfillment plugin.  When all the payment stuff has been gotten out of
the way, a "ship event" could be triggered.  The triggered event
could do something useful like pushing data to your shipping
provider (I really don't know how this part works at all), or
preparing print labels.  In this case, it could email the customer
with a URL of the download.

Then there's the issue of how many times to allow someone to download
the same file?  Or whether to require that the downloader's cookie
match the buyer's cookie?

Regardless, great idea.

- jmj

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Announcement of creation of Django-Ecommerce

[Chris Moffitt]

Given all the great responses to my question about ecommerce and Django,
I've created a separate google group dedicated to this topic.

If you participated in the thread & seemed interested I sent you an
invitation.  If you do not want to join, please just decline.  If you
would like to join, accept the invitation or check it out here -

http://groups.google.com/group/django-ecommerce

Thanks!

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

RE: Fate of 0.91 projects

[Leeuw van der, Tim]

I fully agree with this: a 0.92 made of trunk, with all fixes collected
on trunk. Perhaps patches applied for concurrency/threading issues and
memory leaks -- that would be great for stability, esp. on windows.
Then instantly switch trunk to m-r, and if m-r is good enough, make a
release of it.

Cheers,

--Tim

-Original Message-
From: django-users@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of David S.
Sent: vrijdag 14 april 2006 17:23
To: django-users@googlegroups.com
Subject: Re: Fate of 0.91 projects


Jeroen Ruigrok van der Werven  gmail.com> writes:

> On 4/14/06, Kenneth Gonsalves  thenilgiris.com> wrote:
> > next release *must* be magic removal - no point doing any interim
...
> Better to bite the bullet and get this over with.
...

I was thinking simultaneous release.  Really just for the sake of a
label for
the pre-magic removal stuff.  This is not about "biting the bullet" or
any of
that.  I am talking about projects that are complete and for which it
would be
mighty convenient to have the last and best code to run on.  When it
comes time
for rev 2, we'll be happy to move to 1.x or whatever Django is at.

Of course, it can always be fetched from SVN, it just feels better to
have a
nice EGG for your disaster recovery stack.






--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Django users meetup in Palo Alto on April 27th

[Jacob Kaplan-Moss]

On Apr 13, 2006, at 7:26 PM, Eric Walstad wrote:
> I'll be there IF it's on Thursday, April 27 (as mentioned in your  
> mail to the
> django-users list). If it's on Wednesday (as mentioned on your web  
> page), I
> won't be able to make it.  Please clarify this.

Thanks for catching that; I did have the date wrong on the web page!   
I've updated the page to correctly have the Thursday, April 27th date.

Thanks again,

Jacob

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[arthur debert]

I like th idea of usign  jazz musicians' names:

"monk"!


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Clint Ecker]

Here's basically what I have... the thing with t-shirts is that you can have a base product, the design... and it's got several subproducts  Medium Black shirts, Large black shirts, Meidum blue.  And they've all got different prices attributed to them, like an XXL shirt would be a little more expensive than a XL shirt.  For shipping and such, each shirt (or item) needs a weight associated with it.  Since I used shirts and they typically come in different, generic, reusable types like Jerseys 50/50 Heavyweight, I abstracted that away... anyway, here's a very basic idea of what my model system looks like, its what I came up with doing this site in PHP for a few years and I cleaned it up a lot for Django, it works suprisingly well and is pretty generic, although I can see how it might need some extra stuff depending on what's being sold.
Item-- short_name(slug)-- long_name(char)-- active(bool)Sub_Item-- Item(foriegn)-- Color(foriegn)-- Size (foriegn)-- Type (foriegn) # what kind of shirt is it?-- unit_price (float)
-- num_in_stock (int)Color-- name (char)  # something like "Black"-- html_equivilant (char)  # something like #00Size -- short_name # like "S"-- long_name # like "Small"
Type-- name # like "Jerseys 100% Cotton Large"-- weight (float) # I use it in pounds.  so it's usually something like 0.23I also have Image and Coupon models along with some helpful methods in the Image models for doing thumbnails and stuff that I needed to develope when doing my templates.  Anyway, I've got a basic shopping cart about 60% of the way done and my shirt_detail views and stuff, showing stock matrices and stuff.
I'd be happy to share anything I've come up with to help this project out!On 4/14/06, Jeremy Jones <
[EMAIL PROTECTED]> wrote:On Fri, 14 Apr 2006 22:15:31 +1200Michael <
[EMAIL PROTECTED]> wrote:> http://dshop.mine.nu/shop>> working now to setup trac>>
> > Michael> >>>I just put up what I've coded so far onhttp://jeremy.pitterpatprints.com/I just created that subdomain, so it's not in the DNS for work yet, but
it is from home.  I don't have a shopping cart built in there yet.Another question is whether to allow products from multiple stores topopulate the same shopping cart instance.  I'd think not.Anyway, this site is butt-ugly.  Nothing like the one Michael has put
up, but I hope it gets across some of my intentions.- jmj-- ---Clint Ecker[EMAIL PROTECTED]http://phaedo.cx

--~--~-~--~~~---~--~~
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  -~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Glenn Tenney]

A group with which I volunteer is a Cold Fusion shop.  One of the
other volunteers used EZ-Cart for a few ecommerce sites and loved it.

You might want to see the features it has...  See
http://www.cf-ezcart.com/

-- 
Glenn

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[bruno desthuilliers]

Jeremy Jones wrote:
> 
> Looking forward to working on this.  Here's a rough sketch of what I
> was planning on building (and have actually begun work on).  I don't
> know if this will be palatable to any of the rest of you, or not.  My
> main purpose for building this app was (and is) to provide cheap hosting
> for an easy-to-use ecommerce site.  If what I'm working on can be of
> use to the project we're talking about, I'm happy to contribute.
> 
> - User: I've started using Django's builtin User stuff to manage
> users.  A user is a someone who manages one or more stores.

We also need to manage customers, and there must be some login and
permission stuff about them...

> - Multi-store.  This is pretty self-evident.  

Can be nice, but not a necessity for me. -0 on this.

> Stores can have products,
> product have a names, price, images, descriptions.  Probably ought to
> have product categories in here

Anything about manufacturer ?

> on a per-store basis.
> 
> - Flexible product attribute management.  The base attributes that a
> product should have are name and price.  But it would be nice to allow
> store managers to create products with varying attributes.  For
> example, a shirt could use a "size" attribute with a drop-down list of
> "small", "medium", "large" whereas a coffee cup doesn't need that.

Must also have pricing according to attributes (or attributes
combination), and shipping costs etc,...

> - per-store store management interface.  (Yes, I intended to put two
> "stores" adjacent to one another.)  Right now, the Django admin
> interface is not suitable for allowing multiple users to manage only
> the stuff that belongs to them.  This multi-user, multi-store site needs
> an admin interface that will keep users from mucking with other users'
> stores.

Django-admin would not be enough to have a usable system anyway (I mean:
usable by a normal human being !-).

> - Integration with a payment system.  I already have my wife's site
> working with PayPal.  That was a snap.  I think it'd be great to come
> up with a plugin system to allow integration with any payment system.

s/great/mandatory/


-- 
bruno desthuilliers
développeur
[EMAIL PROTECTED]
http://www.modulix.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Django vs Rails

[Glenn Tenney]

On Thu, Apr 13, 2006 at 07:17:16PM -0700, [EMAIL PROTECTED] wrote:
> There is only one Rails book that is in print at the moment(non pdf).
> There are several others that are going to be released very soon
> though.  

http://www.robsanheim.com/2006/03/23/ruby-and-ruby-on-rails-book-roundup/
is a blog showing something like 16 Ruby and Rails books out now or out "real
soon now".

Searching on Amazon for "ruby rails" gives quite a few books (I
counted NINE Ruby on Rails books) due out within about the next six
months -- who knows if they'll slip or not.

Solid reliable up-to-date accurate complete documentation (without
having to rely on reading through the code itself and/or code
examples) is critical!

To some, that means multiple books being available (not always worth
anything, but some people just want to see books available on
Amazon... period); to others, it doesn't matter if it's one book, half
a dozen books, or downloadable files... so long as it IS available.

--
Glenn

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Michael]

OK, OK, OK finally got working trachttp://dshop.mine.nu/tracsoon will put sources in svn
On 4/15/06, Chris Moffitt <[EMAIL PROTECTED]
> wrote:
> http://dshop.mine.nu/shop>> working now to setup trac>Michael -
Looks like a great start.  Do you want me to setup a mailing list?  We're
getting enough interest that I think it would make sense.  Give me the ok& I can do it & send out an announcement to this list.-Chris

--~--~-~--~~~---~--~~
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  -~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Jeremy Jones]

On Sat, 15 Apr 2006 05:45:20 +1200
Michael <[EMAIL PROTECTED]> wrote:

> OK, OK, OK
> 
> finally got working trac
> http://dshop.mine.nu/trac 
> 
> soon will put sources in svn
> 


I setup a table of the requirements I batted around earlier.  I put in
a "manditoriness" column".  If you think a feature is just not
important, please note it.  If we want to drill down deeper, we can
change the feature column to a WikiCamelCase and let it create a page
for each feature.

http://dshop.mine.nu/trac/wiki/RequirementsDoc

- jmj

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[Bill de hÓra]

> On Thursday 13 Apr 2006 6:54 pm, Adrian Holovaty wrote:
>> Depending on demand, we may release a final pre-magic-removal
>> release of Django -- maybe 0.91.1 or something. Or maybe it'll be
>> 0.92 and magic-removal will be 0.95, to signify it's a big leap.
>> Thoughts?

I think your next release should be an alpha based on magic-removal not 
an upgrade of .92. Cut your losses. Fwiw, as a bystander, magic-removal 
has been too long on the branch and looking at the commit history it 
seems to be your true development trunk (ie there's a lot more than 
magic removal going on). It needs to get merged back or killed.

Simulataneous releases will confuse people and enhance any perception 
that Django is unstable not ready for production work. Parallel branch 
management has really hurt the Zope community for example; there are 
lots of other examples out there.

cheers
Bill


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

"choices" field option - how to make dynamic?

[frank h.]

Hello all,
one field in my model is a "directory" field. I present the user with a
choice of directories on the local filesystem in the admin app.
Basically

infolder = meta.CharField('Video infolder', maxlength=250,
choices=getDirs())

with a custom getDirs method that uses python os module and returns a
list of 2 tuples of the desired directories.

My problem is that whenever I create a new directory on the local
filesystem, I have to restart apache to make the new directory appear
in the choices (I am using mod_python).

How can I get rid of that necessity? any ideas?
thanks a lot
-frank


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[Jeroen Ruigrok van der Werven]

On 4/14/06, Leeuw van der, Tim <[EMAIL PROTECTED]> wrote:
> I fully agree with this: a 0.92 made of trunk, with all fixes collected
> on trunk. Perhaps patches applied for concurrency/threading issues and
> memory leaks -- that would be great for stability, esp. on windows.
> Then instantly switch trunk to m-r, and if m-r is good enough, make a
> release of it.

I can definitely live with this course of action and would throw my
vote in for this.

--
Jeroen Ruigrok van der Werven

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Michael]

OK now sources in trunkget the sources:svn co http://dshop.mine.nu/svn/dshop/trunkI've put there the whole project -just change your db entries and MEDIA_ROOT
On 4/15/06, Michael <[EMAIL PROTECTED]> wrote:
OK, OK, OK finally got working trachttp://dshop.mine.nu/tracsoon will put sources in svn

On 4/15/06, Chris Moffitt <[EMAIL PROTECTED]
> wrote:
> http://dshop.mine.nu/shop>> working now to setup trac>Michael -

Looks like a great start.  Do you want me to setup a mailing list?  We're
getting enough interest that I think it would make sense.  Give me the ok& I can do it & send out an announcement to this list.-Chris



--~--~-~--~~~---~--~~
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  -~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[Jeroen Ruigrok van der Werven]

On 4/14/06, Bill de hÓra <[EMAIL PROTECTED]> wrote:
> I think your next release should be an alpha based on magic-removal not
> an upgrade of .92. Cut your losses.

There has been some commits to the trunk and given how some hosting
parties will not install non-released versions I think it might be
fair for those people depending on that to release a 0.92 or something
like that prior to cut everything in MR over to trunk.

> Fwiw, as a bystander, magic-removal
> has been too long on the branch and looking at the commit history it
> seems to be your true development trunk (ie there's a lot more than
> magic removal going on). It needs to get merged back or killed.

Branches are indeed meant for testing and such without disrupting the
main development line. But given how the main development line will be
the MR code it needs to be moved back to trunk.

> Simulataneous releases will confuse people and enhance any perception
> that Django is unstable not ready for production work. Parallel branch
> management has really hurt the Zope community for example; there are
> lots of other examples out there.

I have to agree to that sentiment too though. The less confusion the better.

--
Jeroen Ruigrok van der Werven

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[James Bennett]

On 4/14/06, Bill de hÓra <[EMAIL PROTECTED]> wrote:
> Simulataneous releases will confuse people and enhance any perception
> that Django is unstable not ready for production work. Parallel branch
> management has really hurt the Zope community for example; there are
> lots of other examples out there.

+1.

--
"May the forces of evil become confused on the way to your house."
  -- George Carlin

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: "choices" field option - how to make dynamic?

[Adrian Holovaty]

On 4/14/06, frank h. <[EMAIL PROTECTED]> wrote:
> one field in my model is a "directory" field. I present the user with a
> choice of directories on the local filesystem in the admin app.
> Basically
>
> infolder = meta.CharField('Video infolder', maxlength=250,
> choices=getDirs())
>
> with a custom getDirs method that uses python os module and returns a
> list of 2 tuples of the desired directories.

Hey Frank,

The FilePathField solves that exact problem. The docs are here:

http://www.djangoproject.com/documentation/model_api/#field-types

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Trunk and docs

[Adrian Holovaty]

On 4/14/06, benchline <[EMAIL PROTECTED]> wrote:
> Does anyone know if the docs in trunk are updated for all the changes
> in the trunk since .91?

Hi benchline,

Yes, the docs in trunk are updated for all changes in trunk since .91.
Major changes are marked as "**New in Django development version**".

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: PostgreSQL Schemas.

[Adrian Holovaty]

On 4/14/06, Ed Epstein <[EMAIL PROTECTED]> wrote:
> If you think it's a good idea, I'd probably suggest looking at adding a
> per project per app setting that specifies a schema. It would need to
> add the create schema statement during the initsql process. For
> subsequent accesses, we would set the default search path for the life
> of connection to match the schema specifed in the settings. Is this
> worth pursuing?

That's the big question -- should the schema be specified in the
settings file or in the model? (Well, I've never used schemas, so
maybe it's not as big of a question as I'm making it out to be. Maybe
it doesn't make sense to put the schema in the model?)

I forgot to mention this ticket, which has a patch for adding schema support:

http://code.djangoproject.com/ticket/1051

That's on an older version of Django but may give you some ideas.

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: [newbie] foreign key dereference issue

[Adrian Holovaty]

On 4/11/06, Scott Finnie <[EMAIL PROTECTED]> wrote:
> class Vendor(meta.Model):
>  class META:
>  admin=meta.Admin()
>  name = meta.CharField("Name", maxlength=100, core=True)
>
>  def __repr__(self):
>  return (self.name)
>
> class ServerModel(meta.Model):
>  class META:
>  admin=meta.Admin()
>
>  vendor = meta.ForeignKey(Vendor)
>  model  = meta.CharField(maxlength=200, core=True)
>
>  def __repr__(self):
>  return (self.vendor.name + " " + self.model)
> --
>
> When I run this, everything's fine with Vendors.  However the
> ServerModel list shows (None) for each entry created instead of the
> expected  .  Also if I click on an entry to edit I
> get a traceback error listing.  I also tried replacing self.vendor.name
> with self.vendor.get_name() but with the same results.

Hey Scott,

Change the __repr__() of ServerModel to this:

return (self.get_vendor().name + " " + self.model)

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Fate of 0.91 projects

[aaloy]

2006/4/14, James Bennett <[EMAIL PROTECTED]>:
>
> On 4/14/06, Bill de hÓra <[EMAIL PROTECTED]> wrote:
> > Simulataneous releases will confuse people and enhance any perception
> > that Django is unstable not ready for production work. Parallel branch
> > management has really hurt the Zope community for example; there are
> > lots of other examples out there.
>
> +1.
My vote is also for converting the M-R branch into trunk and perhaps
put the actual trunk as a branch just to mantain security issues with
that affect the 0.91 version.

I'll prefer to deal with an alpha M-R version knowing that this is the
main trunk than inverting my effort in developing applications that I
positivelly know I should remake in order to adapt to the near future
development.

The M-R should also involve a documentation and examples re-write, as
the quality of the documentation is one of the most important factors
that diferentiates Django.



--

Antoni Aloy López
Binissalem - Mallorca
Soci de Bulma

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[ZebZiggle]

I have no interest in the shopping cart, shipping, etc. ... just the
checkout and credit card processing. I'll happily do the SkipJack
driver. 

-Z


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: "choices" field option - how to make dynamic?

[frank h.]

Thanks Adrian for your quick answer,
I should have mentioned that I was aware of the FilePathField and have
played around with it. the reason I cannot use it is that I want to
display a list of _directories_ and not _files_

unfortunately I wasnt able to make FilePathField give me a list of
directories... but your reply suggest that this might be possible with
some kind of match regexp. if thats the case, I would appreciate some
hints on how the matchstring should look like

many thanks,
-frank


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Ecommerce & Django

[Viktor]

Just a suggestion.

Why not integrate this ecommerce system with TinyErp 
http://tinyerp.org/. i.e. use django as a web interface for TinyErp.

TinyErp is written in python, well tested and for a long time used in 
production.
It has his own ORM, not as sophisticated as Django's, but has very 
similar table naming convention (so it won't be very hard to integrate 
these two applications).

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

How to extend Django template objects?

[Bryan Chow]

Is there a "correct" way to extend a Django template that doesn't exist
on the filesystem? I couldn't find any mention of this in the
documentation.

I'm creating template objects programmatically, and I want one of these
objects to extend another, just as a template on the filesystem can {%
extends %}
another file.

I'm using magic-removal from svn. Any help would be appreciated.

Bryan


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

pictorial representation of models?

[Glenn Tenney]

In my reading up on Ruby on Rails, I found a link to a page on the RoR
wiki that shows a pictorial representation of a schema (model) along
with documentation etc.

See http://wiki.rubyonrails.org/rails/pages/AccessControlListExample/versions/25

Does anything like that exist to take a Django model and automatically
generate a picture of that schema???   I think it would be a BIG help...

-- 
Glenn

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: PostgreSQL Schemas.

[Ed Epstein]

Adrian Holovaty wrote:

> That's the big question -- should the schema be specified in the
> settings file or in the model? (Well, I've never used schemas, so
> maybe it's not as big of a question as I'm making it out to be. Maybe
> it doesn't make sense to put the schema in the model?)

Well here's the thing: I've not been using Django for very long, but
I've found the project / app dichotomy both useful and confusing. One
of the more confusing aspects of it is how the model table names are
constructed with the app name as a prefix. What you often end up with
(and I think this is in the tutorial) is something like "poll_polls"
and whatnot as table names. This doesn't seem very user-friendly to me.
What's worse, you can imagine a large project with several apps such
that in the public schema you have a huge number of tables with
convoluted names that are difficult to keep track of. If a user is
using Django with a database that needs to be accessed from more than
one type of service, this is not very pleasant to work with as well.

So...

It strikes me that one option for this, at least when using Postgres as
the database, (and really, why would you use anything else ;) might be
to have the actual postgres database hold the entire project, while
putting individual apps into their own schema. This alleviates the need
to use the app name as a prefix for table names because each app gets
its own namespace. Not only would this simplify table names, but it
would allow for more freedom in customisation within the database, if
you wanted to use stored procedures in a per-app way for example. It
would help delineate further the difference betweem apps and projects,
as well as provide a more robust logical separation of apps from each
other. It seems like it would provide more flexibility overall. What do
you think?

If the database isn't Postgres, I don't know if the other supported
database backends support a similar feature, but if they do it might
make sense to implement the same thing for those backends. However for
now I'd imagine if I go ahead and make these changes, the behaviour for
the other databases should probably stay the same for now. I haven't
looked at the code enough to see if this could be done easily without
breaking cross-database app support (ie migrating an  app from one
backend to another without any fancy dancing).

Does this seem like a plausible change? If I were to do this, it would
be in the magic-removal branch I think? I'll keep familiarising myself
with the codebase.

>
> I forgot to mention this ticket, which has a patch for adding schema support:
>
> http://code.djangoproject.com/ticket/1051
>
> That's on an older version of Django but may give you some ideas.

It did give me some ideas, but I really think that schemas should be a
per-app setting (which I suppose is more accurately called a per-model
setting), not a per-project setting.

--Ed


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Bug in django/contrib/admin/templatetags/admin_list.py

[DavidA]

If you use a FloatField in the admin list_display, you get an error
rendering the template from line 160 in admin_list.py (TypeError, float
argument required)

158.elif isinstance(f, models.FloatField):
159.if field_val is not None:
160.result_repr = ('%%.%sf' % f.decimal_places) %
field_val
161.else:
162.result_repr = EMPTY_CHANGELIST_VALUE

This comes back to a previous post I had about FloatFields - they are
stored as strings so you can't use it directly in a %f format. I think
the line should be:

160.result_repr = ('%%.%df' % f.decimal_places) %
float(field_val)

But I'm not sure if that should be float() or Decimal().

I'm not sure what the process is to report things like this - and I'm
not a member of django-developers so I just posted it here.

Thanks,
-Dave


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: PostgreSQL Schemas.

[Don Arbow]

On Apr 14, 2006, at 6:54 PM, Ed Epstein wrote:

>
> Adrian Holovaty wrote:
>
>> That's the big question -- should the schema be specified in the
>> settings file or in the model? (Well, I've never used schemas, so
>> maybe it's not as big of a question as I'm making it out to be. Maybe
>> it doesn't make sense to put the schema in the model?)
>
> Well here's the thing: I've not been using Django for very long, but
> I've found the project / app dichotomy both useful and confusing. One
> of the more confusing aspects of it is how the model table names are
> constructed with the app name as a prefix. What you often end up with
> (and I think this is in the tutorial) is something like "poll_polls"
> and whatnot as table names. This doesn't seem very user-friendly to  
> me.
>

I've been using Postgres for a few years now and I've not felt the  
need to use schemas.

I also didn't like the names that Django gave to my tables. But of  
course you can name them anything you'd like using the db_table field  
of the META inner class. A little more effort, but this comes in  
handy when using legacy databases.

Don

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: pictorial representation of models?

[Russell Keith-Magee]

On 4/15/06, Glenn Tenney <[EMAIL PROTECTED]> wrote:

> Does anything like that exist to take a Django model and automatically
> generate a picture of that schema???   I think it would be a BIG help...

1) I don't think the Rails guys have an automated tool, either :-) The
Rails diagram you reference looks suspiciously like it might have been
hand drawn using the Core Data designer from XCode (not unlikely given
that the 37Signals guys - or at least DHH - use Macs).

2) The best graph autolayout tool I know of is GraphViz
(http://www.graphviz.org/)- it's open source, and works off a well
documented input format. I haven't looked into it extensively, but
writing a Django Model->DOT converter shouldn't be too hard - might be
a nice little project if someone is looking to get intimate with
Django model internals.

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
-~--~~~~--~~--~--~---

Re: pictorial representation of models?

[Adrian Holovaty]

On 4/14/06, Glenn Tenney <[EMAIL PROTECTED]> wrote:
> In my reading up on Ruby on Rails, I found a link to a page on the RoR
> wiki that shows a pictorial representation of a schema (model) along
> with documentation etc.
>
> See 
> http://wiki.rubyonrails.org/rails/pages/AccessControlListExample/versions/25
>
> Does anything like that exist to take a Django model and automatically
> generate a picture of that schema???   I think it would be a BIG help...

Yeah, just to be clear, that's not a Rails feature; looks like it was
done by hand. Nothing like that exists (to my knowledge) for Django,
but it wouldn't be too hard to do, I don't think. Could be a nice pet
project for somebody!

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---