Communicating with a PHP script (and pretending I'm a browser)

Joel Goldstick joel.goldstick at
Tue Nov 11 19:26:01 CET 2014

On Tue, Nov 11, 2014 at 12:55 PM, Ethan Furman <ethan at> wrote:
> On 11/11/2014 09:30 AM, Larry Martell wrote:
>> They are technically savvy. They are a 100% PHP shop. They have a big,
>> complicated app that they've been working on for 10 years. No one
>> there knows python or django. They want to put some new frontends on
>> their app. I was bought in for another project (involving Google Tag
>> Manager and Google Analytics), which I completed. Then they asked me
>> about this project. I told them they should redo their app in Flask or
>> Django. It took some cajoling, but they eventually said OK. But then a
>> few days later they said before I went off and reimplemented
>> everything in python, could I just build the new frontend and call the
>> existing PHP code. This would enable them to get the new frontends out
>> to their clients sooner, and then I could go back and port the PHP to
>> python. I don't see what is so wrong with that.

You obviously have thought this through.  It just raises red flags for me.

> Sounds like an excellent game plan to me.  :)
> --
> ~Ethan~
> --

Joel Goldstick

More information about the Python-list mailing list