Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #80547 > unrolled thread
| Started by | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| First post | 2014-11-11 09:55 -0800 |
| Last post | 2014-11-11 09:55 -0800 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Communicating with a PHP script (and pretending I'm a browser) Ethan Furman <ethan@stoneleaf.us> - 2014-11-11 09:55 -0800
| From | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| Date | 2014-11-11 09:55 -0800 |
| Subject | Re: Communicating with a PHP script (and pretending I'm a browser) |
| Message-ID | <mailman.15682.1415728535.18130.python-list@python.org> |
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. Sounds like an excellent game plan to me. :) -- ~Ethan~
Back to top | Article view | comp.lang.python
csiph-web