Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #80616 > unrolled thread

Converting a PHP app to Python + Django (was: Communicating with a PHP script (and pretending I'm a browser))

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.

Contents

  Converting a PHP app to Python + Django (was: Communicating with a PHP script (and pretending I'm a browser)) Ben Finney <ben+python@benfinney.id.au> - 2014-11-13 04:54 +1100

#80616 — Converting a PHP app to Python + Django (was: Communicating with a PHP script (and pretending I'm a browser))

Michael Torrie <torriem@gmail.com> writes:

> If the shop is entire a PHP shop, and no one knows python, then
> rewriting things in Python and Django is a really bad idea.

It can be done well; see “Transitioning from PHP to Django on the sly”
<URL:http://pyvideo.org/video/2233/transitioning-from-php-to-django-on-the-sly>.

The presenter emphasises that one of the more important requirements is
to convince everyone: the management, the developers, even stakeholder
customers/users.

> I've worked in shops before where one person comes in with a new
> language, writes some code, then leaves, leaving us stranded as it
> were.

Right. On the other hand, I've worked in shops where the big PHP code
base is seen by all as a legacy code base, and the stakeholders were
quite open to being convinced to migrate — provided a clear migration
path.

That's what the above presentation goes into. I recommend it.

-- 
 \         “The double standard that exempts religious activities from |
  `\       almost all standards of accountability should be dismantled |
_o__)                   once and for all.” —Daniel Dennett, 2010-01-12 |
Ben Finney

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web