On Fri, Jul 10, 2009 at 10:19:56AM -0400, Gary Poster wrote:
>
> On Jul 10, 2009, at 9:24 AM, Barry Warsaw wrote:
>
>> On Jul 10, 2009, at 8:58 AM, Marius Gedminas wrote:
>>
>>> What do people use to avoid repeating the version number both in the
>>> setup.py as well as in application/library code,
On Jul 10, 2009, at 2:07 PM, P.J. Eby wrote:
At 09:24 AM 7/10/2009 -0400, Barry Warsaw wrote:
On Jul 10, 2009, at 8:58 AM, Marius Gedminas wrote:
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library
At 09:24 AM 7/10/2009 -0400, Barry Warsaw wrote:
On Jul 10, 2009, at 8:58 AM, Marius Gedminas wrote:
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library wants to know its own version number?
I've see
At 03:58 PM 7/10/2009 +0300, Marius Gedminas wrote:
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library wants to know its own version number?
I've seen several options:
1) put __version__ = '4.2' in
One additional fact:
I just discovered that the proxy uses NTLM authentication. There's a
plugin here:
http://code.google.com/p/python-ntlm/
Which allows me to do an NTLM auth on the proxy server - but is there a
way to hook this auth-handler into easy_install, but is that even
possible? Could t
Dear Distutils SIG,
I note that easy_install can be used behind a proxy simply by setting
the "HTTP_PROXY" environment variable.
But what of a proxy which requires authentication? Is there a technique
that will allow me to specify some kind of authentication credentials in
addition to the addres
On Jul 10, 2009, at 9:24 AM, Barry Warsaw wrote:
On Jul 10, 2009, at 8:58 AM, Marius Gedminas wrote:
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library wants to know its own version number?
I've s
Marius Gedminas writes:
> What do people use to avoid repeating the version number both in the
> setup.py as well as in application/library code, when the
> application/library wants to know its own version number?
>
> I've seen several options:
>
> 1) put __version__ = '4.2' in yourpackage/_
On Jul 10, 2009, at 9:20 AM, Paul Moore wrote:
2009/7/10 Jim Fulton :
I don't think this perspective is reflective so much of web
development as
of application development. Those of us who work on web
applications need
to provide working applications, often with hard scalability and
reli
On Jul 10, 2009, at 8:58 AM, Marius Gedminas wrote:
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library wants to know its own version number?
...
4) I don't recall actually ever seeing this one,
On Jul 10, 2009, at 7:39 AM, David Cournapeau wrote:
Jim Fulton wrote:
On Jul 10, 2009, at 1:21 AM, David Cournapeau wrote:
I think it is important that people who come from different
communities
participate to this: people who work on web development have
problems
which are mostly orthog
On Fri, 10 Jul 2009 15:58:32 +0300, Marius Gedminas wrote:
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library wants to know its own version number?
I've seen several options:
1) put __version__ = '
On Jul 10, 2009, at 8:58 AM, Marius Gedminas wrote:
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library wants to know its own version number?
I've seen several options:
1) put __version__ = '4.2' in
2009/7/10 Jim Fulton :
> I don't think this perspective is reflective so much of web development as
> of application development. Those of us who work on web applications need
> to provide working applications, often with hard scalability and reliability
> requirements. We need to have control ov
What do people use to avoid repeating the version number both in the
setup.py as well as in application/library code, when the
application/library wants to know its own version number?
I've seen several options:
1) put __version__ = '4.2' in yourpackage/__init__.py, have setup.py
do from y
Jim Fulton wrote:
>
> On Jul 10, 2009, at 1:21 AM, David Cournapeau wrote:
>> I think it is important that people who come from different communities
>> participate to this: people who work on web development have problems
>> which are mostly orthogonal to mine, but I get the impression that most
>
On Jul 10, 2009, at 1:21 AM, David Cournapeau wrote:
I think it is important that people who come from different
communities
participate to this: people who work on web development have problems
which are mostly orthogonal to mine, but I get the impression that
most
people on distutils-sig
17 matches
Mail list logo
