Re: Pylons 0.9.6 Release Candidate 1

2007-07-18 Thread Jonas
On 17 jul, 20:08, Philip Jenvey [EMAIL PROTECTED] wrote: models has indeed moved to model. You might want to switch your app to use model so you're more in sync with the template, but it's not at all required. Nothing internally in Pylons assumes you have a model directory. There is a bug

Re: Pylons 0.9.6 Release Candidate 1

2007-07-18 Thread Jonas
On 17 jul, 20:08, Philip Jenvey [EMAIL PROTECTED] wrote: models has indeed moved to model. You might want to switch your app to use model so you're more in sync with the template, but it's not at all required. Nothing internally in Pylons assumes you have a model directory. There is a bug

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread voltron
Hi! I noticed that a few directories are not created when one creates a new project: i18n docs templates The models directory is also now called model. Is that all intentional or is something wrong? --~--~-~--~~~---~--~~ You received this message because you

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread Christoph Haas
On Mon, Jul 16, 2007 at 03:19:16PM -0700, Ben Bangert wrote: On Jul 16, 2007, at 2:40 PM, Jose Galvez wrote: Sure, First I was testing with pylons-0.9.6rc2dev_r2256-py2.5.egg The project was created with pylons 0.9.4.1 and then converted after installing rc2 using

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread Ian Bicking
Christoph Haas wrote: On Mon, Jul 16, 2007 at 03:19:16PM -0700, Ben Bangert wrote: On Jul 16, 2007, at 2:40 PM, Jose Galvez wrote: Sure, First I was testing with pylons-0.9.6rc2dev_r2256-py2.5.egg The project was created with pylons 0.9.4.1 and then converted after

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread Jose Galvez
Thats what I did, I found it much easier to diff the folders rather then look at the diff at the time of upgrade. What I am going to do is use your workingenv to set up a parallel project to do the upgrade and migration in. I will also be using diff on the folders rather then looking at the

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread Christoph Haas
On Tue, Jul 17, 2007 at 11:34:03AM -0500, Ian Bicking wrote: Christoph Haas wrote: On Mon, Jul 16, 2007 at 03:19:16PM -0700, Ben Bangert wrote: On Jul 16, 2007, at 2:40 PM, Jose Galvez wrote: Sure, First I was testing with pylons-0.9.6rc2dev_r2256-py2.5.egg The

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread Philip Jenvey
On Jul 17, 2007, at 9:34 AM, Ian Bicking wrote: Christoph Haas wrote: On Mon, Jul 16, 2007 at 03:19:16PM -0700, Ben Bangert wrote: On Jul 16, 2007, at 2:40 PM, Jose Galvez wrote: Sure, First I was testing with pylons-0.9.6rc2dev_r2256-py2.5.egg The project was created with

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread Evert Rol
I noticed that a few directories are not created when one creates a new project: i18n docs templates The models directory is also now called model. Is that all intentional or is something wrong? i18n and templates should be created, but as empty directories. It must be a bug if

Re: Pylons 0.9.6 Release Candidate 1

2007-07-17 Thread voltron
Hi Phillip. I tried it out again several times, same thing. I am getting this on windows 2000 professional. I have created the folders though, and everything works as expected. On Jul 17, 9:08 pm, Philip Jenvey [EMAIL PROTECTED] wrote: On Jul 16, 2007, at 11:27 PM, voltron wrote: Hi!

Re: Pylons 0.9.6 Release Candidate 1

2007-07-16 Thread jose
Again this is a pretty big departure from the previous builds with respect to the Response object. I've done some quick preliminary testing, and at least between version 9.4 and RC2 my controllers (simple hello world stuff) were able to still use the Response object directly. Is this going to

Re: Pylons 0.9.6 Release Candidate 1

2007-07-16 Thread Ben Bangert
On Jul 16, 2007, at 11:00 AM, jose wrote: Again this is a pretty big departure from the previous builds with respect to the Response object. I've done some quick preliminary testing, and at least between version 9.4 and RC2 my controllers (simple hello world stuff) were able to still use the

Re: Pylons 0.9.6 Release Candidate 1

2007-07-16 Thread jose
Well I just tried using render_response and it generates an error not a warning, so I looks like I may have to migrate my projects anyway, not a huge deal just something to work on. I think I'll do my migration within a working env and then just port the new build once I know it works rather

Re: Pylons 0.9.6 Release Candidate 1

2007-07-16 Thread Jose Galvez
Sure, First I was testing with pylons-0.9.6rc2dev_r2256-py2.5.egg The project was created with pylons 0.9.4.1 and then converted after installing rc2 using overwrite the test project was not installed using easy_install simply created and run from the created egg my controller is: from

Re: Pylons 0.9.6 Release Candidate 1

2007-07-16 Thread Jose Galvez
Here is my easy_install pth fine so you can see what version of what I have installed: import sys; sys.__plen = len(sys.path) #./setuptools-0.6c6-py2.5.egg ./paste-1.4-py2.5.egg ./pastescript-1.3.5-py2.5.egg ./pastedeploy-1.3.1-py2.5.egg ./mako-0.1.8-py2.5.egg ./myghtyutils-0.52-py2.5.egg

Re: Pylons 0.9.6 Release Candidate 1

2007-07-16 Thread Ben Bangert
On Jul 16, 2007, at 2:40 PM, Jose Galvez wrote: Sure, First I was testing with pylons-0.9.6rc2dev_r2256-py2.5.egg The project was created with pylons 0.9.4.1 and then converted after installing rc2 using overwrite the test project was not installed using easy_install simply created and run

Re: Pylons 0.9.6 Release Candidate 1

2007-07-16 Thread Jose Galvez
Thanks Ben, thats exactly what I did I just let it override everything. Migration is going to be alot more work then I originally thought, I still have a copy of the original files (pre migration) I think I'll do a diff on the files to see whats different. From what you wrote below I should pay

Pylons 0.9.6 Release Candidate 1

2007-07-15 Thread Ben Bangert
Hi folks, We're putting out a release candidate for 0.9.6 this time to ensure any quirks we find can be corrected before the final. Please feel free to update your projects (http://wiki.pylonshq.com/display/ pylonsdocs/Upgrading), of course keep a backup of your existing one. :) After

Re: Pylons 0.9.6 Release Candidate 1

2007-07-15 Thread voltron
Hi! Great to see that a new shiny Pylons version is out :-)) I upgraded Pylons to 0.96 RC1 with easy_install -U Pylons. To test, I just created a new app with paster create -t pylons test3. Instad of a working test I got these errors when starting the new app:

Re: Pylons 0.9.6 Release Candidate 1

2007-07-15 Thread Ben Bangert
On Jul 15, 2007, at 3:53 AM, voltron wrote: Great to see that a new shiny Pylons version is out :-)) I upgraded Pylons to 0.96 RC1 with easy_install -U Pylons. To test, I just created a new app with paster create -t pylons test3. Instad of a working test I got these errors when starting the

Re: Pylons 0.9.6 Release Candidate 1

2007-07-15 Thread voltron
Hi Ben, That worked, the project starts now. Is there some documentation somewhere that I can read about how things are to done with this new version? For example: 1. Using SAContext with 0.96 2. using the Global config object 3. Using the Global response object 4. How to use HTTPExceptions in

Re: Pylons 0.9.6 Release Candidate 1

2007-07-15 Thread Jose Galvez
Ben Bangert wrote: On Jul 15, 2007, at 10:25 AM, voltron wrote: That worked, the project starts now. Is there some documentation somewhere that I can read about how things are to done with this new version? For example: 1. Using SAContext with 0.96 The latest SAContext works fine, and

Re: Pylons 0.9.6 Release Candidate 1

2007-07-15 Thread Max Ischenko
Hi, Here is the error I got: $ sudo python setup.py egg_info running egg_info Traceback (most recent call last): File setup.py, line 34, in module , File distutils/core.py, line 151, in setup File distutils/dist.py, line 974, in run_commands File distutils/dist.py, line 993, in

Re: Pylons 0.9.6 Release Candidate 1

2007-07-15 Thread Max Ischenko
On Jul 16, 8:46 am, Max Ischenko [EMAIL PROTECTED] wrote: Nevermind this; This seems to be a known bug in setuptools which pops up if you have any uncommitted directory when you run setup.py. As a workaround, you need to either commit or temporarily revert any directories marked as 'A' by