Hello... this is my first post to this list and...
I would like to introduce myself by proposing a module for inclusion
(hopefully in a "near future") among the standard libraries (modules)
offered by Python (of course the idea is to present it here, promote
the debate and if "we all like it", wel
You need to bring this sort of thing up in python-ideas before here,
first of all. Also, there isnt a strong case for including a module
that is only used by one project somewhere. Promote it on its own,
outside of this other project. Let other people use it and get
feedback from real use. When its
[I just saw the other post about unit testing, while I was writing this.
A strange conincidence.]
Hello,
since this is the first time I post to this list, I'd like to introduce
myself briefly. As you can see my name is Sebastian. I am working as a
software developer both as a professional and as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 12, 2008, at 10:30 AM, Sebastian Rittau wrote:
[I just saw the other post about unit testing, while I was writing
this.
A strange conincidence.]
Indeed. I've played around (again) recently with both nose and
py.test, so I'd like to mak
On Tue, 12 Aug 2008 11:05:57 -0400, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 12, 2008, at 10:30 AM, Sebastian Rittau wrote:
[I just saw the other post about unit testing, while I was writing this.
A strange conincidence.]
Indeed. I've play
On Tue, Aug 12, 2008 at 11:05:57AM -0400, Barry Warsaw wrote:
-> -BEGIN PGP SIGNED MESSAGE-
-> Hash: SHA1
->
-> On Aug 12, 2008, at 10:30 AM, Sebastian Rittau wrote:
->
-> >[I just saw the other post about unit testing, while I was writing
-> >this.
-> >A strange conincidence.]
->
-> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 12, 2008, at 11:12 AM, Jean-Paul Calderone wrote:
A SIG might be a good idea. There's also already the "testing in
python"
list, too:
http://lists.idyll.org/listinfo/testing-in-python
A lot of this discussion would be appropriate there.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 12, 2008, at 11:13 AM, C. Titus Brown wrote:
I'll forward this idea on to testing-in-python:
http://lists.idyll.org/listinfo/testing-in-python
where there was another bikeshed discussion about testing, a few weeks
ago. That might b
Hello:
I am looking to replace 2 Python developers for my client in Dallas
TX. This is a full time position and due to teh challenge in finding
Python Developers, my client is willing to be open on his salary
requirement and will offer relocation assistance as well plus
benefits. Please email resu
On Tue, Aug 12, 2008, Bhavani wrote:
>
> I am looking to replace 2 Python developers for my client in Dallas
> TX. This is a full time position and due to teh challenge in finding
> Python Developers, my client is willing to be open on his salary
> requirement and will offer relocation assistance
Every so often, running the SSL test suite in verbose mode, I get
something like this:
server: connection cipher is now ('AES256-SHA', 'TLSv1/SSLv3', 256)
server: connection cipher is now ('AES256-SHA', 'TLSv1/SSLv3', 256)
That is, duplicate output lines. Any idea why that is? They're all
wri
Is it using fork()? Threads?
On Tue, Aug 12, 2008 at 10:01 AM, Bill Janssen <[EMAIL PROTECTED]> wrote:
> Every so often, running the SSL test suite in verbose mode, I get
> something like this:
>
> server: connection cipher is now ('AES256-SHA', 'TLSv1/SSLv3', 256)
> server: connection cipher is
> Is it using fork()? Threads?
No on fork(), yes on threads.
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive
On Tue, Aug 12, 2008 at 11:32 AM, Bill Janssen <[EMAIL PROTECTED]> wrote:
>> Is it using fork()? Threads?
>
> No on fork(), yes on threads.
Hmm... I don't believe that io.py is thread-safe. :-(
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
First, I'd like to know why this discussion is happening on
the committers list.
Python-dev is the right list for these things. I've adjusted the
CC accordingly.
On 2008-08-12 20:44, Martin v. Löwis wrote:
I am planning to offer a single file patch for 2.3 and 2.4. As far as
one more 2.5 releas
On Tue, Aug 12, 2008 at 4:21 PM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> First, I'd like to know why this discussion is happening on
> the committers list.
>
> Python-dev is the right list for these things. I've adjusted the
> CC accordingly.
>
> On 2008-08-12 20:44, Martin v. Löwis wrote:
>
>> Because there won't typically be sufficient testing and release
>> infrastructure to allow arbitrary bug fixes to be committed on the
>> branch. The buildbots are turned off, and nobody tests the release
>> candidate, no Windows binaries are provided - thus, chances are very
>> high that a bug f
17 matches
Mail list logo
