Which version to use for new implementation
8 views
Skip to first unread message
Adam N
Aug 10, 2010, 2:53:38 PM8/10/10
to django-piston
Does anybody have advice on which version of Piston to use for a new
installation? 0.2.2 seems a bit old and doesn't use the python-oauth
library, which I feel would be better. However, I don't want to
follow tip for a production project.
Is there a stable revision number I can install from?
Thanks,
Adam
installation? 0.2.2 seems a bit old and doesn't use the python-oauth
library, which I feel would be better. However, I don't want to
follow tip for a production project.
Is there a stable revision number I can install from?
Thanks,
Adam
Rock
Aug 10, 2010, 11:51:42 PM8/10/10
to django-piston
I grabbed a version of the trunk on May 3rd which I have used quite
successfully for several deployed projects along with Django 1.2.1 and
Python 2.6.5. At the time it was marked in setup.py as version
"0.2.3rc1". I currently consider every version of piston other than
that particular drop to be either inferior or suspect. Sadly I don't
know enough about the inner workings of mercurial to give you any more
guidance than that. (If someone knows of a way I can peruse the .hg
area to get info that would enable others to pull the same bits from
bitbucket that I did, then please let me know.)
I have been hoping for a new official release of piston for months,
but sadly that appears to be getting farther away rather than closer
as far as I can tell. This means that I have had to remove piston from
one system in order to simplify the deployment process for our
customer. This means that one of the largest and most respected hi-
tech companies in the world will not be deploying a piston-based app
after all. (Actually in this case piston was probably overkill for
their needs anyway.)
successfully for several deployed projects along with Django 1.2.1 and
Python 2.6.5. At the time it was marked in setup.py as version
"0.2.3rc1". I currently consider every version of piston other than
that particular drop to be either inferior or suspect. Sadly I don't
know enough about the inner workings of mercurial to give you any more
guidance than that. (If someone knows of a way I can peruse the .hg
area to get info that would enable others to pull the same bits from
bitbucket that I did, then please let me know.)
I have been hoping for a new official release of piston for months,
but sadly that appears to be getting farther away rather than closer
as far as I can tell. This means that I have had to remove piston from
one system in order to simplify the deployment process for our
customer. This means that one of the largest and most respected hi-
tech companies in the world will not be deploying a piston-based app
after all. (Actually in this case piston was probably overkill for
their needs anyway.)
jespern
Aug 11, 2010, 12:08:24 AM8/11/10
to django-piston
As I've previously stated, 0.3 will hit the streets once the fork is
cleared for a release. I'm unfortunately extremely short on time these
days, so I can't do it.
Jesper
cleared for a release. I'm unfortunately extremely short on time these
days, so I can't do it.
Jesper
Mario Gonzalez
Aug 12, 2010, 10:20:32 AM8/12/10
to django-piston
On Aug 11, 12:08 am, jespern <jno...@gmail.com> wrote:
> As I've previously stated, 0.3 will hit the streets once the fork is
> cleared for a release. I'm unfortunately extremely short on time these
> days, so I can't do it.
>
Jesper,
> As I've previously stated, 0.3 will hit the streets once the fork is
> cleared for a release. I'm unfortunately extremely short on time these
> days, so I can't do it.
>
But why you and only you need to do all things? My question, is this a
project where new developers and ideas are accepted? Time ago others
developers and I offered help; what do you need to receive help? or is
this a 'close' project to new developers?
Many thanks in advance.
Reply all
Reply to author
Forward
0 new messages