Re: RFC: Django 1.0 roadmap and timeline
Jacob, I feel your pain butty. Do what you think is right, django has been brilliant so far. The jump to version 1(lightspeed) has been a bit of a nightmare, but let's all remember a pre django world. I for one trust Jacob's judgement. Just do it mate, there's good good people who want to help. Chewie fixed the falcon with a blow from a spanner. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~--~~~~--~~--~--~---
Re: new to django / web development altogether
Hi Joyanta You have so many questions that it's impossible to answer them all, and some of them are unanswerable, 'who knows', 'it depends' type answers. Django is good though, damn good. On 11/04/2008, Patryk Zawadzki <[EMAIL PROTECTED]> wrote: > > 2008/4/11 joyanta <[EMAIL PROTECTED]>: > > > > > Hi, > > > > I am pretty much a server side and thick client software developer > > trying to get into web programming, and would like to know more on > > Django. I am slowly going through the tutorials etc. I am trying to > > figure out which technology to use; what criteria one needs to look > > into before picking a technology to create a web application (say .. > > facebook or ebay, web 2.0 apps). What advantages does Django has over > > Java Servlets? What to use when. And say you want to use Amazon web > > services, then? I just have very little experience in web programming, > > as majority of my day is spent doing C# / ADO.NET > > > > I would love some pointers or have a discussion. > > > The first technology you should use is called "join django-users and > not django-developers" ;) > > > -- > Patryk Zawadzki > PLD Linux Distribution > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~--~~~~--~~--~--~---
Re: Django expertise
Aaron try this site http://djangogigs.com/ On 03/04/2008, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > > On Thu, Apr 3, 2008 at 9:07 AM, Aaron <[EMAIL PROTECTED]> wrote: > > My apologies in advance if this is not the correct channel for this > > message, > > > It is not. From the group's description: > > """ > Discussion group for Django developers. This group is used for > discussion of developing Django itself, not user questions; Please use > django-users for issues regarding using the framework, questions for > the Django user community outreach, etc. > """ > > > Jacob > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~--~~~~--~~--~--~---
Re: Would a web search be a good addition to the contribs framework?
Thanks for the tips Ian Building this search solution is the next job on my every growing list, I think I'll blog it as it'll be a really good example of someone who is starting from the beggining with very little knowledge :-) On 03/10/2007, Ian Holsman <[EMAIL PROTECTED]> wrote: > > Matt Davies wrote: > > Hi Ian > > > > > > I'm not very clued up with Java so solr, although I've built it to > > work on 3 sites now with django, they're still single indexes. We've > > got over 200 sites in house that we're looking for a compelte search > > solution for. > > > > I think solr is definately the way to go, but as we're moving all our > > sites into django, then a one stop search application built in django > > to query all those sites would have been nice. Especially if someone > > else had written it :-) > > > > See, I'm lazy really, but I think I'm going to have to learn java as > > my boss is also a rails fan, so Sorl is looking like the most likely > > candidate. > > > > I love it by the way, it's fab! > > > > > you don't need to learn java, just how to install tomcat. > configuring solr is a matter of editing a single XML file for the most > part, and your done. > sure, you can go under the covers and add some advanced functionality if > you want to, and you would need to know java to do that, but for the > majority of people its a black box, just like a mysql database is. > > the client api (in python) means you can still use django for everything > else. > > regards > Ian > > ps. the facet search is a kicker, and once you get the hang of it, it > can replace a database query for TONs of things. > > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~--~~~~--~~--~--~---
Re: Would a web search be a good addition to the contribs framework?
Hi Ian BTW, this is different to what shabda was proposing, which was doing all-the-web type searches Ahh, I got you. I'm not very clued up with Java so solr, although I've built it to work on 3 sites now with django, they're still single indexes. We've got over 200 sites in house that we're looking for a compelte search solution for. I think solr is definately the way to go, but as we're moving all our sites into django, then a one stop search application built in django to query all those sites would have been nice. Especially if someone else had written it :-) See, I'm lazy really, but I think I'm going to have to learn java as my boss is also a rails fan, so Sorl is looking like the most likely candidate. I love it by the way, it's fab! On 03/10/2007, Ian Holsman <[EMAIL PROTECTED]> wrote: > > Matt Davies wrote: > > yes please shabda > > > > we're currenlty moving away from webglimpse and into solr for our > > search engine technology, but something inside django itself would be > > really useful. > > > > > While I live and breathe solr (we use it VERY heavily @ $WORK), I'm not > sure what you would be adding that the solr python client API doesn't > give you. > I would recommend using https://issues.apache.org/jira/browse/SOLR-216 > it's pretty simple to use. > > BTW, this is different to what shabda was proposing, which was doing > all-the-web type searches > > regards > Ian > > > Especially if you could query other django appilcations from within > > one application. > > > > ooh, now dat be tasty burgers > > > > On 01/10/2007, shabda.raaj <[EMAIL PROTECTED]> wrote: > > > >> It looks to me that a api to get web search functionality in Django > >> would be good idea. For example, I generally want to keep track of the > >> pages linking to my sites. Similarly being able to search from inside > >> of django might be useful in many cases. > >> Would a web search be a good addition to the contribs framework? I am > >> willing to code this. But before doing that, I just want to make sure > >> it would be useful to people :) > >> (I just plan to add convinient api for webservices found at > >> http://developer.yahoo.com/search/ ) > >> > >> > >> > > > > > > > > > > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~--~~~~--~~--~--~---
Re: Would a web search be a good addition to the contribs framework?
yes please shabda we're currenlty moving away from webglimpse and into solr for our search engine technology, but something inside django itself would be really useful. Especially if you could query other django appilcations from within one application. ooh, now dat be tasty burgers On 01/10/2007, shabda.raaj <[EMAIL PROTECTED]> wrote: > > It looks to me that a api to get web search functionality in Django > would be good idea. For example, I generally want to keep track of the > pages linking to my sites. Similarly being able to search from inside > of django might be useful in many cases. > Would a web search be a good addition to the contribs framework? I am > willing to code this. But before doing that, I just want to make sure > it would be useful to people :) > (I just plan to add convinient api for webservices found at > http://developer.yahoo.com/search/ ) > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~--~~~~--~~--~--~---
Re: Error message: The Python markdown library isn't installed. - Help needed please.
Hi John You need to install the python Markdown Module, it doesn't come with django mate or python, it's like an add on. I think on gentoo linux you can install it using emerge and etc-update. Not sure though, check your gentoo documentation on installing python modules. On 21/06/07, john-f <[EMAIL PROTECTED]> wrote: > > > Hi all > > I'm currently moving sites over to one server at my company. The > server will be hosting 2 versions of django (0.91 and 0.95). > > Currently all the 0.91 sites on the server are up and running. > However, after I set up my first 0.95 site on the server I'm getting a > "The Python markdown library isn't installed." error message when I go > to the site. > > My server setup: > -The server is a gentoo linux box. > -Main webserver is apache2 using fastcgi to run python/django. > -All media is on another server and is served by lighttpd. > -my django install is in /home/python/django_0.95/trunk/django/ > -I HAVE included 'django.contrib.markup' in INSTALLED_APPS in the > settings file. > -I HAVE set PYTHONPATH="/home/python/django_0.95/trunk:/var/devel" in > my fastcgi startup script for that site. > > I'd be very appreciative for any help. Thanks! > > John > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~--~~~~--~~--~--~---
Re: textile mysql unicode and newforms
Hi Waylan
I tried it the uicode branch on my local machine and it didn't make any
difference. I'm still keeping it on my local box though.
So, I tweaked the code a bit, so it looks like this at the top of the save
overide now, not at the bottom and it's working as expected.
if self.summary:
self.summary = self.summary.encode('ascii', 'ignore')
self.summary_html = textile.textile(self.summary)
That way we simply don't pass the pasted apostrophes at all, and textile
works, what i was after in the first place.
This works on the production server that isn't running the unicode branch
yet. Soon though, when we get some time to test.
I think I might have some trouble when my boss tells me they want to use the
same code base to do a welsh site though, lots of funny characters in there.
And the country
:-)
On 19/06/07, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
>
> I suspect the Unicode branch [1] addresses the issues you are having.
> A few weeks back there was a call for testers as it is now feature
> complete. I'd suggest giving that a try.
>
> [1]: http://code.djangoproject.com/wiki/UnicodeBranch
>
>
> On 6/19/07, vanderkerkoff <[EMAIL PROTECTED]> wrote:
> >
> > Hello everyone
> >
> > I'm running django from the trunk, so using the most up to date
> > version, python 2.5 with PyTextile 2.0.10.
> > mysql5.0.2 with all settings to utf-8 and django content type is utf-8
> >
> > I'm overwriting the save command on events using newforms, we're
> > textiling the input for an html field, here's what I mean.
> >
> > def save(self):
> > import textile
> > if self.body:
> > self.body_html = textile.textile(self.body)
> > super(Event, self).save()
> >
> >
> > it fails with this error
> >
> > Exception Value:'ascii' codec can't decode byte 0xb4 in position
> 0:
> > ordinal not in range(128)
> > Exception Location:
> /usr/local/lib/python2.5/site-packages/textile.py
> > in glyphs, line 2418
> >
> > My textile settings are
> > # Set your encoding here.
> > ENCODING = 'utf8'
> >
> > # Output? Non-ASCII characters will be automatically
> > # converted to XML entities if you choose ASCII.
> > OUTPUT = 'utf8'
> >
> > I tried changing my OUTPUT to ascii in textile but got the same error,
> > so to me it looks like the form is sending a unicode
> > series of bytes to textile which it can't understand.
> >
> > One way around this is to manipulate the self.summary prior to passing
> > it to textile, like this.
> >
> > self.body = self.body.decode('utf-8')
> > self.body = self.body.encode('ascii', 'ignore')
> >
> > This forces the passing of ascii to textile and it likes that alot,
> > and works.
> >
> > But if a user now copies and pastes the dreaded apostrophe form word
> > or another special character unique to word,
> > it fails with this error.
> >
> > Exception Value:'ascii' codec can't encode character u'\u2019'
> in
> > position 5: ordinal not in range(128)
> > Exception Location: /usr/local/lib/python2.5/encodings/utf_8.py in
> > decode, line 16
> >
> >
> > If I run the super save earlier in the save definition after removing
> > the textiling of the body section, and then
> > call the data out of the database further down in the save definition,
> > and then save it again like this
> >
> > e = Event.objects.get(id=new_id)
> > if e.body:
> > e.body_html = textile.textile(e.body)
> > super(Event, e).save()
> >
> > It all works fine, no encoding or decoding needed for pasted
> > apostrophes or anything.
> >
> > Here's the paste of the relevant part of the form with certain
> > sections commented out so you can see what I mean.
> >
> > http://pastie.textmate.org/71702
> >
> > I found this on the google groups form Ivan Sagalev
> > To summarizes: your storage (a database) and your input/output (the
> > web)
> > really should use utf-8 to avoid problems with "strange" characters.
> > If
> > you deal internally with unicode (which newforms produce for you) then
> > for now you should explicitly encode from it to utf-8 until Django
> > starts doing it automatically.
> >
> > I've also been reading this thread on the google developers group, and
> > I'm now completely confused as to what is going on.
> >
> > unicode issues in multiple tickets
> >
> > If anyone can tell me if there is some current status on this, or how
> > it works right now I'd be really grateful. If I have to encode and
> > decode then I
> > don't mind, not much anyway :-)
> >
> >
> > >
> >
>
>
> --
>
> Waylan Limberg
> [EMAIL PROTECTED]
>
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
Re: textile mysql unicode and newforms
Here's the add_event in my views which uses the newforms and calls the save.
http://pastie.textmate.org/71706
It will probably help :-)
On 19/06/07, vanderkerkoff <[EMAIL PROTECTED]> wrote:
>
> Hello everyone
>
> I'm running django from the trunk, so using the most up to date
> version, python 2.5 with PyTextile 2.0.10.
> mysql5.0.2 with all settings to utf-8 and django content type is utf-8
>
> I'm overwriting the save command on events using newforms, we're
> textiling the input for an html field, here's what I mean.
>
> def save(self):
> import textile
> if self.body:
> self.body_html = textile.textile(self.body)
> super(Event, self).save()
>
>
> it fails with this error
>
> Exception Value:'ascii' codec can't decode byte 0xb4 in position
> 0:
> ordinal not in range(128)
> Exception Location: /usr/local/lib/python2.5/site-packages/textile.py
> in glyphs, line 2418
>
> My textile settings are
> # Set your encoding here.
> ENCODING = 'utf8'
>
> # Output? Non-ASCII characters will be automatically
> # converted to XML entities if you choose ASCII.
> OUTPUT = 'utf8'
>
> I tried changing my OUTPUT to ascii in textile but got the same error,
> so to me it looks like the form is sending a unicode
> series of bytes to textile which it can't understand.
>
> One way around this is to manipulate the self.summary prior to passing
> it to textile, like this.
>
> self.body = self.body.decode('utf-8')
> self.body = self.body.encode('ascii', 'ignore')
>
> This forces the passing of ascii to textile and it likes that alot,
> and works.
>
> But if a user now copies and pastes the dreaded apostrophe form word
> or another special character unique to word,
> it fails with this error.
>
> Exception Value:'ascii' codec can't encode character u'\u2019' in
> position 5: ordinal not in range(128)
> Exception Location: /usr/local/lib/python2.5/encodings/utf_8.py in
> decode, line 16
>
>
> If I run the super save earlier in the save definition after removing
> the textiling of the body section, and then
> call the data out of the database further down in the save definition,
> and then save it again like this
>
> e = Event.objects.get(id=new_id)
> if e.body:
> e.body_html = textile.textile(e.body)
> super(Event, e).save()
>
> It all works fine, no encoding or decoding needed for pasted
> apostrophes or anything.
>
> Here's the paste of the relevant part of the form with certain
> sections commented out so you can see what I mean.
>
> http://pastie.textmate.org/71702
>
> I found this on the google groups form Ivan Sagalev
> To summarizes: your storage (a database) and your input/output (the
> web)
> really should use utf-8 to avoid problems with "strange" characters.
> If
> you deal internally with unicode (which newforms produce for you) then
> for now you should explicitly encode from it to utf-8 until Django
> starts doing it automatically.
>
> I've also been reading this thread on the google developers group, and
> I'm now completely confused as to what is going on.
>
> unicode issues in multiple tickets
>
> If anyone can tell me if there is some current status on this, or how
> it works right now I'd be really grateful. If I have to encode and
> decode then I
> don't mind, not much anyway :-)
>
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---
