Re: Django in Boo
Hans-Christian Holm wrote: > My first reaction to Django was "hey, this looks nice, maybe it could be > ported to Boo, my favourite language at the moment?" On second thought, I'd > rather see Django run on IronPython. You could use Boo with that, if you > wanted to. I would be very interesting to see if Django+IronPython could run > in ASP.NET through some DjangoHttpHandler. I don't see why it shouldn't > (theoretically), unless there are some troublesome dependencies on libraries > would have to be ported to .NET first. I am interested in that too. Unfortunately it is not possible to run Django with IronPython as it is --- IronPython doesn't support the Python standard library (pure Python modules are supported). During PyCon 2006 I had a brief conversation with Jim Hugunin about that. Let's hope they will find a way to support the rest (C modules). Otherwise we are talking about porting Django with all obvious downsides of this solution. Another problem is unresolved issues with MS SQL, which doesn't support limit-offset queries directly. While it is possible to use other databases from .Net environment, MS SQL native provider has the best performance. :-) Thanks, Eugene --~--~-~--~~~---~--~~ 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 in Boo
My first reaction to Django was "hey, this looks nice, maybe it could be ported to Boo, my favourite language at the moment?" On second thought, I'd rather see Django run on IronPython. You could use Boo with that, if you wanted to. I would be very interesting to see if Django+IronPython could run in ASP.NET through some DjangoHttpHandler. I don't see why it shouldn't (theoretically), unless there are some troublesome dependencies on libraries would have to be ported to .NET first. As for Boo, there is MonoRail (http://www.castleproject.org/index.php/MonoRail), a Ruby Action Pack inspired framework for .NET. MonoRail has special support for Boo in Brail templates. All this sounds very nice, but as much I've tried to like MonoRail, I never got those good vibrations I hoped for. With Django, I got them. Hans-Christian - Original Message - From: "wizeman" <[EMAIL PROTECTED]> To: "Django users" <django-users@googlegroups.com> Sent: Friday, March 03, 2006 11:45 PM Subject: Django in Boo > > Hi. I'm just starting to use Django and I'm loving it. > > Don't you think it would be great if Django was ported to Boo ( > http://boo.codehaus.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: Django in Boo
On 3/5/06, gabor <[EMAIL PROTECTED]> wrote:
>
> >>> def f(y):
> ... x = y * 3
> ... return x + y
> ...
> >>> f(5)
> 20
> >>> f('_django_')
> '_django__django__django__django_'
> >>>
>
> you know...this whole 'static typing' thing is a little a double-edged
> sword, isn't it? :))
You know, my first thought there was "badger badger badger badger" . . . :-p
--~--~-~--~~~---~--~~
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 in Boo
wizeman wrote:
> Jeremy Dunck wrote:
>> IronPython -is- Python, runs on .Net, and is coming along nicely.
>
> Yes, IronPython is also cool. You know when you look at something and
> you say - wow, this is a great idea and it would be great if everyone
> realizes that? I had that feeling with Python right away, but only in
> the last few years it started to be considered a "real" language.
>
> One thing that I consider a good idea is static typing combined with
> type inference. It just makes for good programming practice and doesn't
> require verbose syntax. You can do things like:
>
> def f(y as int):
> x = y * 3
> return x + y
>
> and the compiler figures out the type of 'x' and the return type of
> 'f()' automatically, or you can specify it yourself if you want to. And
> it can catch a lot of errors, especially in big projects.
>
>>> def f(y):
... x = y * 3
... return x + y
...
>>> f(5)
20
>>> f('_django_')
'_django__django__django__django_'
>>>
you know...this whole 'static typing' thing is a little a double-edged
sword, isn't it? :))
gabor
--~--~-~--~~~---~--~~
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 in Boo
On Saturday 04 March 2006 05:12, wizeman wrote: > Think about it. Python was an esoteric language in the beginning. And > Boo isn't that esoteric, it can be thought of as an extension to the > Python syntax. > And virtually all .NET libraries can be used in Boo, it runs on the > .NET/Mono runtime. The .NET libraries are very unpythonic. They are about the last libraries I'd *want* to use if I were using python or a python-like language. For example: all the public method names start with capital letters (so they look like classes); only instances are first class objects; there are huge numbers of unwieldy collection classes (now in untyped, strongly typed and generic flavours) instead of a few good ones etc. etc. The only languages I've seen that the .NET libraries work well with are C# and VB.NET (and VB.NET is really just C# 1.0 without the curly braces -- yes, really). For the same reason I'm not particularly drawn to using IronPython in my day job, even if I could, because I'd still have to use .NET libraries for the projects I work on. Luke -- "The first ten million years were the worst. And the second ten million, they were the worst too. The third ten million, I didn't enjoy at all. After that I went into a bit of a decline." (Marvin the paranoid android) 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: Django in Boo
Jeremy Dunck wrote: > IronPython -is- Python, runs on .Net, and is coming along nicely. Yes, IronPython is also cool. You know when you look at something and you say - wow, this is a great idea and it would be great if everyone realizes that? I had that feeling with Python right away, but only in the last few years it started to be considered a "real" language. One thing that I consider a good idea is static typing combined with type inference. It just makes for good programming practice and doesn't require verbose syntax. You can do things like: def f(y as int): x = y * 3 return x + y and the compiler figures out the type of 'x' and the return type of 'f()' automatically, or you can specify it yourself if you want to. And it can catch a lot of errors, especially in big projects. Another thing that I consider a great idea is programming by contract, and while it isn't part of Boo, it can be cleanly done with syntax macros. But anyway, this is getting off-topic and I don't want to bore you. I wanted to raise some awareness of the language and maybe get you to check it out. Or you can ignore it, as long as you have fun in coding... :) --~--~-~--~~~---~--~~ 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 in Boo
On 3/3/06, wizeman <[EMAIL PROTECTED]> wrote: > > Ok, I was thinking more in an academic perspective instead of a > real-world one. > > Think about it. Python was an esoteric language in the beginning. And > Boo isn't that esoteric, it can be thought of as an extension to the > Python syntax. IronPython -is- Python, runs on .Net, and is coming along nicely. --~--~-~--~~~---~--~~ 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 in Boo
Ok, I was thinking more in an academic perspective instead of a real-world one. Think about it. Python was an esoteric language in the beginning. And Boo isn't that esoteric, it can be thought of as an extension to the Python syntax. And virtually all .NET libraries can be used in Boo, it runs on the .NET/Mono runtime. Well, I guess there aren't many Boo fans (yet) ;) If only I made web pages for a living.. *sniff* --~--~-~--~~~---~--~~ 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 in Boo
wizeman wrote: > > I think one of the big advantages is the static typing feature. It's > great, because if you change a variable or method name (or type) in one > of your classes, and forget to change the method calls in other > classes, the error(s) would be caught at compile-time instead of > run-time. > > What do you think about this? > It would be a great undertaking, but it would be awesome :) One problem is going to be the Python Standard Library and bridge libraries to system-specific and 3rd-party features (e.g., web servers, databases), unless Boo solved it already. In general this is the problem for all esoteric languages irrespective of how cool they are. Another thing to consider is the payback of such transition. Unless you have some mission critical CPU constrained web applications, it doesn't worth it. Thanks, Eugene --~--~-~--~~~---~--~~ 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 in Boo
On 3/3/06, Tom Tobin <[EMAIL PROTECTED]> wrote: > Err, knock yourself out porting it if you want (as it's BSD licensed > after all), but I don't think you'll see many of us jumping to switch > from Python anytime soon. ;-) That's a much more measured response than my initial one (which I was smart enough not to send). ;-) --~--~-~--~~~---~--~~ 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 in Boo
On Friday 03 March 2006 14:45, wizeman wrote: > If you don't know Boo, here are some of the main features: > > - Python-like syntax > - Power of static typing with the ease-of-use of type inference > - It's compiled, so type mismatches are caught right after changing > something > - It runs on the Mono runtime (CLR), which is faster than the Python > implementation > - Extendable through macros > - It can use any .NET/Mono libraries > - Etc > > I think one of the big advantages is the static typing feature. It's > great, because if you change a variable or method name (or type) in one > of your classes, and forget to change the method calls in other > classes, the error(s) would be caught at compile-time instead of > run-time. Boo, Hiss :) I'm using Django *because* it's in Python. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django in Boo
On 3/3/06, wizeman <[EMAIL PROTECTED]> wrote: > > Hi. I'm just starting to use Django and I'm loving it. > > Don't you think it would be great if Django was ported to Boo ( > http://boo.codehaus.org/ ) ? Err, knock yourself out porting it if you want (as it's BSD licensed after all), but I don't think you'll see many of us jumping to switch from Python anytime soon. ;-) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Django in Boo
Hi. I'm just starting to use Django and I'm loving it. Don't you think it would be great if Django was ported to Boo ( http://boo.codehaus.org/ ) ? If you don't know Boo, here are some of the main features: - Python-like syntax - Power of static typing with the ease-of-use of type inference - It's compiled, so type mismatches are caught right after changing something - It runs on the Mono runtime (CLR), which is faster than the Python implementation - Extendable through macros - It can use any .NET/Mono libraries - Etc I think one of the big advantages is the static typing feature. It's great, because if you change a variable or method name (or type) in one of your classes, and forget to change the method calls in other classes, the error(s) would be caught at compile-time instead of run-time. What do you think about this? It would be a great undertaking, but it would be awesome :) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
