On Friday 12 March 2010 11:44 PM, Mike Orr wrote:
On Fri, Mar 12, 2010 at 9:28 AM, Krishnakant Mane<[email protected]> wrote:
IC, but Beta? can I develop an application using the beta version? Is it
stable enough?
When I said "beta" I meant the latest prerelease version, which is RC1
Ic, this means even pylons 1.0 is RC just like 0.10.
now. It normally takes a month or two to write an application and get
it ready for production. By that time, 1.0 final will almost certainly
be released, and it will be almost identical to RC1.
That's true, but my question was probably unclear.
I did not ask about the stability with respect to deployment. My
question was regarding consistency during development.
I wan't like to have some unpredictible problems during development,
just to know that its a bug to be resolved in the final release or even
worst, I might discover a so far unknown problem and it might stop the
development of that module or any further dependent modules which needed
that broken feature. If the Pylons development team does not fear any
such major show-stopper with the RC, I think I don't mind. As you
rightly said, an application won't go live on production server till it
is completely tested in terms of its functinality. So if pylons version
1 is not recommended for production now, I am ok with it.
Pylons 0.10 is mainly for existing applications. It's like 1.0 but
doesn't still has the deprecated features, so 0.9.7 applications won't
require as many changes.
So will i have to change the parts of the code manually for using the latest
features?
If you create an 0.9.7 application, you will have to modify it for
1.0. If you run it under 0.10, it should work but you'll get
deprecation warnings. You may also have to stick to an older version
of WebHelpers (0.6.4).
So, right now if I use 1.0 beta, does it come with the correct version
of webhelpers?
And is there a one-stop list of what I should change in my controls or
mako templates (which I any ways intend to use against any other
templating module )?
If you create an 0.10 application, the structure should be the same as
a 1.0 application. But 0.10 will allow you to use old features that
1.0 won't, so the burden will be on you to use only 1.0-compatible
features if you want to avoid having to make changes later.
The easiest way to upgrade an application is to run "paster create -t
pylons AppName" on top of the existing application. It will notice the
differences between your actual files and the application template,
and offer to make the changes automatically, write the changes to
backup files, or show you a diff. In any case you'll have to review
the changes manually and make sure your customizations remain intact,
but it may save some typing and errors vs making all the changes
manually.
Ah, that's a very nice feature indeed.
So what I do is install Pylons 1.0 beta in a virtual environment and
then drop the folder containing the older app in there.
Then run paster create -t pylons <appname>
is that correct?
And can I use the easy_install command to install pylons 1 beta in a vertual
environment?
RC1 is on PyPI as of this moment, so you should be able to easy_install it.
I did easy_install pylons and it took 0.10 RC.
What should I do for the beta for 1.0?
Happy hacking.
Krishnakant.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
