On Sep 29, 1:18 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 28-Sep-07, at 11:16 PM, Milan Andric wrote:
>
> > Is there some standard practice on a machine that has production code
> > running in mod_python but also has developers running their django-
> > python web server? Is that disc
Thanks for the input!
On Sep 28, 10:18 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 28-Sep-07, at 11:16 PM, Milan Andric wrote:
>
> > Is there some standard practice on a machine that has production code
> > running in mod_python but also has developers running their django-
> > python w
On 28-Sep-07, at 11:16 PM, Milan Andric wrote:
> Is there some standard practice on a machine that has production code
> running in mod_python but also has developers running their django-
> python web server? Is that discouraged? I figure a regular user
> would not share the same django with
Hi!
RajeshD gave you a great answer. My experience says that the best
and most comfortable way of working for developers is to set up full
environment on their own machines. Then use subversion (or other
version control system) and its branch and tag features and... what I
really love use Ian
Hi,
On Sep 28, 1:46 pm, Milan Andric <[EMAIL PROTECTED]> wrote:
> Is there some standard practice on a machine that has production code
> running in mod_python but also has developers running their django-
> python web server? Is that discouraged?
Yes absolutely discouraged. The standard practi
Is there some standard practice on a machine that has production code
running in mod_python but also has developers running their django-
python web server? Is that discouraged? I figure a regular user
would not share the same django with mod_python because of .pyc files
and permissions? So dev
6 matches
Mail list logo
