Nick Coghlan wrote:
Talin wrote:
multiprocessing
multiprocessing would work for me
Me, too.
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/
Tom Pinckney wrote:
Why not use MPI? It's cross platform, cross language and very widely
supported already. And there're Python bindings already.
The point of pyprocessing is that fact that the API is the same as that
of the threading module - making it very easy to convert a multithreaded
pr
Steven D'Aprano wrote:
[...]
[tongue firmly in cheek]
Perhaps what we need is a more flexible enumerate function?
enumerate(iterable, start_at_index=0, count_from=0)
Super idea. Then we can have a thread about whether it belongs in
itertools or somewhere else.
[...]
Please take your tongue ou
Talin wrote:
multiprocessing
multiprocessing would work for me - it adds the concurrency implications
that threading has, but 'processing' on its own would be missing.
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---
Brett Cannon wrote:
On Tue, May 13, 2008 at 12:41 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Cannon wrote:
| It is up to the tests to clean up after themselves since they can be
| executed directly, so there is not magical location that gets
btw, I fixed the Lib/test/test_bsddb3.py file for the updated
Lib/bsddb/test/ modules. Thats how the test suite gets run by the
buildbots (run the test suite from a python trunk sandbox using
"./python Lib/test/regrtest.py -v -u bsddb test_bsddb test_bsddb3" to
reproduce exactly how it is run your
Greg Ewing wrote:
Steven D'Aprano wrote:
With iterators being such a fundamental part of Python these days,
perhaps one day we'll see the functions in the itertools module become
iterator methods
I hope not. The set of potential functions that operate
on iterators is open-ended, and there's n
multiprocessing
Greg Ewing wrote:
Jesse Noller wrote:
I am looking for any questions, concerns or benchmarks python-dev has
regarding the possible inclusion of the pyprocessing module to the
standard library
Sounds good, but I'd suggest giving a more specific
name than "processing", which is
The inclusion of the processing module does not exclude the potential
to also use or one day include MPI bindings.
The goal is to add a module with a "known" API and semantics which
allows programmer using cPython to easily take advantage of multple
cores (and as a side benefit, machines).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 13, 2008, at 7:12 PM, Martin v. Löwis wrote:
If you generated your python subversion ssh key during this time on a
machine fitting the description above, please consider replacing your
keys.
apt-get update ; apt-get upgrade on debian will pr
Why not use MPI? It's cross platform, cross language and very widely
supported already. And there're Python bindings already.
On May 13, 2008, at 8:52 PM, Jesse Noller wrote:
I am looking for any questions, concerns or benchmarks python-dev has
regarding the possible inclusion of the pyproces
On May 13, 2008, at 8:57 PM, Greg Ewing <[EMAIL PROTECTED]>
wrote:
Jesse Noller wrote:
I am looking for any questions, concerns or benchmarks python-dev has
regarding the possible inclusion of the pyprocessing module to the
standard library
Sounds good, but I'd suggest giving a more spec
Jesse Noller wrote:
I am looking for any questions, concerns or benchmarks python-dev has
regarding the possible inclusion of the pyprocessing module to the
standard library
Sounds good, but I'd suggest giving a more specific
name than "processing", which is so generic as to
be meaningless.
--
I am looking for any questions, concerns or benchmarks python-dev has
regarding the possible inclusion of the pyprocessing module to the
standard library - preferably in the 2.6 timeline. In March, I began
working on the PEP for the inclusion of the pyprocessing (processing)
module into the python
Steven D'Aprano wrote:
With iterators being such a fundamental part of Python these days,
perhaps one day we'll see the functions in the itertools module become
iterator methods
I hope not. The set of potential functions that operate
on iterators is open-ended, and there's no reason to
single
On Tue, May 13, 2008 at 7:12 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > If you generated your python subversion ssh key during this time on a
> > machine fitting the description above, please consider replacing your
> > keys.
> >
> > apt-get update ; apt-get upgrade on debian will pro
On Tue, May 13, 2008 at 4:54 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Gregory P. Smith wrote:
> | After that, merging his changes into trunk will be relatively easy and I
> | think we should give jcea commit access and let him do it and henc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregory P. Smith wrote:
| After that, merging his changes into trunk will be relatively easy and I
| think we should give jcea commit access and let him do it and henceforth
| use python svn as the official repository for the pybsddb code and
| docume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trent Nelson wrote:
|> Next week I will (if nothing goes wrong) publish pybsddb
|> 4.6.4. This release supports distributed transactions and
|> replication, testsuite is way faster, and rewritten to be
|> able to launch tests from multiple threads/pro
> If you generated your python subversion ssh key during this time on a
> machine fitting the description above, please consider replacing your
> keys.
>
> apt-get update ; apt-get upgrade on debian will provide you with a
> ssh-vulnkey program that can be used to test if your ssh keys are
> valid
On Tue, May 13, 2008 at 3:11 PM, Steven D'Aprano <[EMAIL PROTECTED]> wrote:
> With iterators being such a fundamental part of Python these days,
> perhaps one day we'll see the functions in the itertools module become
> iterator methods, as happened with strings. But that's a discussion for
> a
On Wed, 14 May 2008 05:01:20 am you wrote:
> > While slices are wonderfully useful things, they aren't panaceas.
> > They're not so useful with iterators, and they make a copy of the
> > data, which can be problematic if there's a *lot* of it.
>
> That's why we have itertools.islice().
I always
On Tue, May 13, 2008 at 1:45 PM, Guilherme Polo <[EMAIL PROTECTED]> wrote:\
> Thanks for pointing it out Gregory.
>
> ssh-vulnkey says most of my keys are compromised, including the one
> used for python's svn.
Then according to the developer FAQ, you should change your keys and
email [EMAIL PR
"Duncan Booth" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
|
| If you are generating paginated output then a function to generate an
| arbitrary page would likely want to enumerate starting at some value
larger
| than one.
|
| Of course in that case you'll also want to skip part
On Tue, May 13, 2008 at 12:41 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Brett Cannon wrote:
> | It is up to the tests to clean up after themselves since they can be
> | executed directly, so there is not magical location that gets cleaned
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Cannon wrote:
| It is up to the tests to clean up after themselves since they can be
| executed directly, so there is not magical location that gets cleaned
| up in case a test screws up. You can use test.test_support.TESTFN if
| you want a loca
On Tue, May 13, 2008 at 9:09 PM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I just committed pybsddb 4.6.4 to python svn. My next step (after a
> successfull buildbot cycle, I hope!) is to commit the new testsuite.
> First I need to review any cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just committed pybsddb 4.6.4 to python svn. My next step (after a
successfull buildbot cycle, I hope!) is to commit the new testsuite.
First I need to review any changes there since I maintain pybsddb.
The testsuite creates a lot of files/directori
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Ewing wrote:
| Steven D'Aprano wrote:
|> The only thing I can think of is printing lines with line numbers
|
| Parsing a file and wanting to be able to print
| error messages with line numbers would seem to
| be a fairly likely use.
What is wron
Guido van Rossum schrieb:
On Tue, May 13, 2008 at 11:59 AM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
2008/5/13, Steven D'Aprano <[EMAIL PROTECTED]>:
> Perhaps what we need is a more flexible enumerate function?
> enumerate(iterable, start_at_index=0, count_from=0)
+1 to provide both op
On Tue, May 13, 2008 at 11:59 AM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
> 2008/5/13, Steven D'Aprano <[EMAIL PROTECTED]>:
>
>
> > Perhaps what we need is a more flexible enumerate function?
> > enumerate(iterable, start_at_index=0, count_from=0)
>
> +1 to provide both options: they're not
On Tue, May 13, 2008 at 11:53 AM, Steven D'Aprano <[EMAIL PROTECTED]> wrote:
> On Wed, 14 May 2008 12:25:01 am Guido van Rossum wrote:
>
> > However I see no use for skipping items
> > from the start,
>
> You've never had to deal with data where the first N items were special
> in some way? e.g
2008/5/13, Steven D'Aprano <[EMAIL PROTECTED]>:
> Perhaps what we need is a more flexible enumerate function?
> enumerate(iterable, start_at_index=0, count_from=0)
+1 to provide both options: they're not intrusive (as I can keep using
enumerate without those), and having both helps in the under
On Wed, 14 May 2008 12:25:01 am Guido van Rossum wrote:
> However I see no use for skipping items
> from the start,
You've never had to deal with data where the first N items were special
in some way? e.g. skipping over a header line in a file?
I know I've written code like this before:
it =
2008/5/13 Gregory P. Smith <[EMAIL PROTECTED]>:
> Heads up.
>
> Debian screwed up. As a result all ssh and ssl keys generated in the
> last 18 months on debian and ubuntu systems may be compromised due to
> not using a good random number generator seed.
> http://lists.debian.org/debian-security-an
Heads up.
Debian screwed up. As a result all ssh and ssl keys generated in the
last 18 months on debian and ubuntu systems may be compromised due to
not using a good random number generator seed.
http://lists.debian.org/debian-security-announce/2008/msg00152.html
and http://www.links.org/?p=327
"Steven D'Aprano" <[EMAIL PROTECTED]> wrote:
> On Mon, 12 May 2008 08:20:51 am Georg Brandl wrote:
>> I believe the following is a common use-case for enumerate()
>> (at least, I've used it quite some times):
>>
>> for lineno, line in enumerate(fileobject):
>> ...
>>
>> For this, it would be
On Tue, May 13, 2008 at 2:40 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Terry Reedy wrote:
>>
>> "Nick Coghlan" <[EMAIL PROTECTED]> wrote in message
>> news:[EMAIL PROTECTED]
>> | I'd like to hear from Raymond before we do this. I'm pretty sure we had
>> | a reason for *not* doing it that way in
Terry Reedy wrote:
"Nick Coghlan" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| I'd like to hear from Raymond before we do this. I'm pretty sure we had
| a reason for *not* doing it that way in when enumerate() was added, but
| I can't remember what that reason might have been...
39 matches
Mail list logo
