Status of This Project

[mchang]

Hi all,

I've been trying to find an Amazon FPS wrapper in python, and this
seems like the closest one. However, when I actually tried to use it,
I find that it's targeting the old APIs, and the new FPS apis are
significantly different. Thus, I've been making manual changes to
client.py to get it working for me.

I was just wondering about the status of this project and whether it's
going to be further developed in the future. I wouldn't mind
contributing either. Also, do you guys know of any alternatives to
FPyS for interfacing with FPS in Python? Thanks!

[Tim Freund]

Hello --

FPyS was the only option when I started the project, and then I got
pulled away before I was able to deploy anything into production. My
partner and I have recently dusted off that application, and we're
starting to work on it again, so we were also planning on updating the
FPyS API.

I'd love to have some help moving the project forward -- knowing that
someone else is out there using it and working on it is a big motivator
for me. I have a repository created for the code out on bitbucket, but
I haven't migrated the code from subversion yet -- I thought that might
help people contribute without getting held up waiting for patches to be
checked in to a central subversion repository. Would that be helpful to
you? How else can we streamline the process?

Thanks for getting in touch!

Tim

--
Tim Freund
http://achievewith.us
913-207-0983

[mchang]

Thanks Tim!

I'm definitely interested in contributing to the project, as there
doesn't seem to be a definitive python interface to FPS currently.
The mercurial repository sounds good. I'm still in the process of
working out a basic "pay" request error I'm getting (I posted in the
forums but nobody is responding...). Other than that, to start out, I
think a data dump/brainstorm of what has changed with the Amazon API
since this project has last been touched would be good.

[Xingzhi Pan]

I used FPyS one year ago in a project. The production website (http://www.thesaints.org) is in PHP but FPyS helped a lot in prototyping the application in Python.

So FPS's API changed?

-Harry

2009/8/8 mchang <aznm...@gmail.com>

[mchang]

Yeah, there's additional parameters to REST api calls, and some
parameters are no longer needed. I'm not sure what it was like back
then, but there are different "quickstart" apis for different
functionalities.

On Aug 7, 6:33 pm, Xingzhi Pan <vengeance.st...@gmail.com> wrote:
> I used FPyS one year ago in a project. The production website (http://www.thesaints.org) is in PHP but FPyS helped a lot in prototyping the
> application in Python.
>
> So FPS's API changed?
>
> -Harry
>

> 2009/8/8 mchang <aznm1k...@gmail.com>

[Tim Freund]

I got the easy part done -- I have uploaded the project to bitbucket:
http://bitbucket.org/timfreund/fpys/

I am going to try to build a demo application that uses the recurring
payments API -- as I build it I'll makes notes of any API changes that I
come across and report them back here. The existing demo application
was written with TurboGears 1 -- does anyone have a preference for the
recurring payment demo?

I found a small bug in the API that I introduced when I merged the
recurring payments patch from Daniel -- if you were using FPyS checked
out from SVN, you may have encountered that bug when trying to get your
basic payment to work. Which forum did you post on, the Amazon AWS forum?

Thanks!

Tim

[mchang]

Hey Tim,

I definitely saw that error from svn, that's what got me editing the
source code in the first place :). The problem, I believe, was that
recurringPeriod was a parameter, but when you put it into the
querystring without a value (and thereafter signed it), it was invalid?

[Griffin]

Hey Tim,

Any progress on the move to bitbucket or the demo app? I'm starting
to rely on fpys for an app and I've had to manually change the source
code. I've forked it an put it into my companys SVN repo. I would
love to contribute it back, though, if there's a need.

- Griffin