I'm sure that only 1 or 2 people cares about my opinion on this, but I will
say that PEP 572 is taking one of my least favorite features of C/C++ and
adding it to Python. About the only good thing I can say about it is that
it might make some things more convenient to write. Worse to read, worse
up to python-dev to offer a slightly wider audience
for commentary/concerns, and hopefully to get a stamp of approval that it
is ready.
Thank you,
- Josiah
On Sat, Mar 29, 2014 at 11:58 PM, Josiah Carlson josiah.carl...@gmail.com
wrote:
I've got a patch with partial tests and documentation
And as I was writing the thank you to folks, I hit send too early. Also
thank you to Victor Stinner, Guido, Terry Reedy, and everyone else on this
thread :)
- Josiah
On Thu, May 29, 2014 at 5:34 PM, Josiah Carlson josiah.carl...@gmail.com
wrote:
Pinging this thread 2 months later
to continue following this issue and participate in the
discussion, I'll see you over on http://bugs.python.org/issue1191964 .
- Josiah
On Fri, Mar 28, 2014 at 11:35 AM, Josiah Carlson
josiah.carl...@gmail.comwrote:
On Fri, Mar 28, 2014 at 10:46 AM, Guido van Rossum gu...@python.orgwrote
*This* is the type of conversation that I wanted to avoid. But I'll answer
your questions because I used to do exactly the same thing.
On Fri, Mar 28, 2014 at 3:20 AM, Victor Stinner victor.stin...@gmail.comwrote:
2014-03-28 2:16 GMT+01:00 Josiah Carlson josiah.carl...@gmail.com:
def do_login
On Fri, Mar 28, 2014 at 10:46 AM, Guido van Rossum gu...@python.org wrote:
On Fri, Mar 28, 2014 at 9:45 AM, Josiah Carlson
josiah.carl...@gmail.comwrote:
If it makes you feel any better, I spent an hour this morning building a
2-function API for Linux and Windows, both tested, not using
On Fri, Mar 28, 2014 at 12:42 PM, Terry Reedy tjre...@udel.edu wrote:
On 3/28/2014 12:45 PM, Josiah Carlson wrote:
If it makes you feel any better, I spent an hour this morning building a
2-function API for Linux and Windows, both tested, not using ctypes, and
not even using any part
/0LpyQtU5
- Josiah
On Fri, Mar 28, 2014 at 1:09 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 28 March 2014 05:09, Josiah Carlson josiah.carl...@gmail.com wrote:
So yeah. Someone want to make a decision? Tell me to write the docs, I
will.
Tell me to go take a long walk off a short pier, I'll
Hopping in to give my take on this, which I've expressed to Antoine
off-list.
When I first built the functionality about 8.5-9 years ago, I personally
just wanted to be able to build something that could replace some of
Expect: http://expect.sourceforge.net/ . The original and perhaps current
API
more wishful thinking on my part than anything.
- Josiah
On Thu, Mar 27, 2014 at 4:24 PM, Victor Stinner victor.stin...@gmail.comwrote:
2014-03-27 22:52 GMT+01:00 Josiah Carlson josiah.carl...@gmail.com:
* Because it is example docs, maybe a multi-week bikeshedding discussion
about API
On Thu, Mar 27, 2014 at 7:18 PM, Terry Reedy tjre...@udel.edu wrote:
On 3/27/2014 9:16 PM, Josiah Carlson wrote:
You don't understand the point because you don't understand the feature
request or PEP. That is probably my fault for not communicating the
intent better in the past. The feature
, then your thread would be on-topic.
I replied off-list because I didn't want to contribute to the off-topic
posting, but if posting on-list is required for you to pay attention, so be
it.
- Josiah
On Nov 12, 2013 2:51 PM, Victor Stinner victor.stin...@gmail.com wrote:
2013/11/12 Josiah Carlson
Pardon me for this drive-by posting, but this thread smells a lot like this
old thread (don't be afraid to read it all, there are some good points in
there; not directed at you Martin, but at all readers/posters in this
thread)...
On Fri, Jan 29, 2010 at 11:25 PM, Stephen J. Turnbull
step...@xemacs.org wrote:
Josiah Carlson writes:
Lisp lists are really stacks
No, they're really (ie, concretely) singly-linked lists.
Now, stacks are an abstract data type, and singly-linked lists provide
an efficient implementation
On Fri, Jan 29, 2010 at 11:31 PM, Stephen J. Turnbull
step...@xemacs.org wrote:
Josiah Carlson writes:
On Thu, Jan 28, 2010 at 8:57 PM, Steve Howell showel...@yahoo.com wrote:
What do you think of LISP, and car in particular (apart from
the stupidly cryptic name)?
Apples
On Thu, Jan 28, 2010 at 8:57 PM, Steve Howell showel...@yahoo.com wrote:
--- On Thu, 1/28/10, Josiah Carlson josiah.carl...@gmail.com wrote:
[...] in the decade+ that I've been using
Python and
needed an ordered sequence; lists were the right solution
99% of the
time [...]
What do you
On Thu, Jan 28, 2010 at 9:48 PM, Terry Reedy tjre...@udel.edu wrote:
On 1/28/2010 6:30 PM, Josiah Carlson wrote:
I would also point out that the way these things are typically done is
that programmers/engineers have use-cases that are not satisfied by
existing structures, they explain
Having read the entirety of the thread (which is a rare case these
days, I need more spare time), and being that I'm feeling particularly
snarky today, I'm going to agree 100% with everything that Raymond has
said in this message and his few subsequent messages. Snarky comments
to follow.
I
If one doesn't care about slicing, the obvious implementation using a
dictionary and two counters works great for a deque with random
indexing. Well... except for the doubling in memory usage.
- Josiah
On Wed, Jan 27, 2010 at 4:15 PM, Raymond Hettinger
raymond.hettin...@gmail.com wrote:
On
On Wed, Jul 1, 2009 at 6:48 PM, Benjamin Petersonbenja...@python.org wrote:
2009/7/1 Eric Pruitt eric.pru...@gmail.com:
Hello,
I am working on the subprocess.Popen module for Python 2.7 and am now moving
my changes over to Python 3.1 however I am having trouble with the whole
byte situation
On Tue, Jun 9, 2009 at 7:46 AM, Kálmán
Gergelykalman.gerg...@duodecad.hu wrote:
Hello, my name is Greg.
I've just started using python after many years of C programming, and I'm
also new to the list. I wanted to clarify this
first, so that maybe I will get a little less beating for my
On Sun, Mar 1, 2009 at 10:45 AM, Hirokazu Yamamoto
ocean-c...@m2.ccsnet.ne.jp wrote:
I uploaded the patch with choice (a)
http://bugs.python.org/file13215/py3k_mmap_and_bytes.patch
If (b) is suitable, I'll rewrite the patch.
___
Python-Dev mailing
On Thu, Mar 5, 2009 at 12:46 PM, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Daniel Stutzbach wrote:
If you have a working select(), it will tell you the sockets on which
read() and write() won't block, so non-blocking reads and writes are not
necessary.
No, but there should be an
On Thu, Mar 5, 2009 at 1:09 PM, Bill Janssen jans...@parc.com wrote:
Josiah Carlson josiah.carl...@gmail.com wrote:
On Thu, Mar 5, 2009 at 12:46 PM, Greg Ewing greg.ew...@canterbury.ac.nz
wrote:
Daniel Stutzbach wrote:
If you have a working select(), it will tell you the sockets
On Thu, Mar 5, 2009 at 3:11 PM, gl...@divmod.com wrote:
On 07:30 pm, n...@arctrix.com wrote:
Chris McDonough chr...@plope.com wrote:
As far as I can tell, asyncore/asynchat is all undocumented
internals. Any use of asyncore in anger will use internals;
there never was any well-understood
On Wed, Mar 4, 2009 at 1:31 PM, Guido van Rossum gu...@python.org wrote:
On Wed, Mar 4, 2009 at 1:27 PM, Chris McDonough chr...@plope.com wrote:
Daniel Stutzbach wrote:
On Wed, Mar 4, 2009 at 12:54 PM, Guido van Rossum gu...@python.org wrote:
The same as always. We don't change APIs in bugfix
Recently I found the need to generate some constants inside a class
body. What I discovered was a bit unintuitive, and may not be
intended...
In 2.5 and 2.6:
class foo:
... x = {}
... x.update((i, x.get(i, None)) for i in xrange(10))
...
Traceback (most recent call last):
File stdin,
On Fri, Feb 20, 2009 at 3:14 PM, Nick Coghlan ncogh...@gmail.com wrote:
Josiah Carlson wrote:
The behavior of 3.0 WRT list comprehensions behaving the same way as
generator expressions is expected, but why generator expressions
(generally) don't keep a reference to the class scope during
Would anyone mind terribly if I backported a version of:
http://bugs.python.org/issue4501 to 2.4 and 2.5?
It fixes some strange duplicate data issues on poll() with packets
with a nonstandard flag set.
- Josiah
On Sat, Dec 13, 2008 at 2:55 PM, Martin v. Löwis mar...@v.loewis.de wrote:
On Mon, Dec 15, 2008 at 1:14 PM, Victor Stinner
victor.stin...@haypocalc.com wrote:
Le Monday 15 December 2008 19:50:42 Josiah Carlson, vous avez écrit :
Would anyone mind terribly if I backported a version of:
http://bugs.python.org/issue4501 to 2.4 and 2.5?
First the patch have be reviewed
On Tue, Nov 4, 2008 at 5:31 AM, Leonardo Santagada [EMAIL PROTECTED] wrote:
On Nov 4, 2008, at 12:11 AM, Josiah Carlson wrote:
There is no shortage of algorithms (such as matrix multiplication) that
are parallelizable but not particularly good candidates for an IPC-based
multiprocessing
On Sun, Nov 2, 2008 at 3:51 PM, [EMAIL PROTECTED] wrote:
Antoine I think it is important to remind that the GIL doesn't prevent
Antoine (almost) true multithreading. The only thing it prevents is
Antoine full use of multi-CPU resources in a single process.
I believe everyone here
On Mon, Nov 3, 2008 at 10:59 AM, Curt Hagenlocher [EMAIL PROTECTED]wrote:
On Mon, Nov 3, 2008 at 11:50 AM, Josiah Carlson [EMAIL PROTECTED]wrote:
On Sun, Nov 2, 2008 at 3:51 PM, [EMAIL PROTECTED] wrote:
Antoine I think it is important to remind that the GIL doesn't
prevent
Antoine
On Wed, Oct 8, 2008 at 10:30 AM, Bill Janssen [EMAIL PROTECTED] wrote:
Sidnei da Silva [EMAIL PROTECTED] wrote:
https://bugs.edge.launchpad.net/zope2/+bug/280020
I think there are real issues here with both asynchat and Medusa.
Asynchat has been heavily re-written, and the ac_out_buffer has
On Sat, Sep 27, 2008 at 8:54 AM, Victor Stinner
[EMAIL PROTECTED] wrote:
Second, I would like to help to fix all Python security issues. It looks like
Python community isn't very reactive (proactive?) about security. Eg. a DoS
was reported in smtpd server (integrated to Python)... 15 months
On Mon, Sep 22, 2008 at 5:15 PM, Brendan O'Connor [EMAIL PROTECTED] wrote:
Hi everyone,
I was enjoying reading Raymond Hettinger's Objects/dictnotes.txt, and
was wondering, which (if any) of its suggestions implemented? I see
most of it was written back in 2003.
If I remember correctly (and
On Sat, Sep 13, 2008 at 1:20 PM, Armin Ronacher
[EMAIL PROTECTED] wrote:
Hi everybody,
In Python 2.x when iterating over a weak key dictionary for example, the
common
idom for doing that was calling dictionary.keys() to ensure that a list of all
objects is returned it was safe to iterate
On Sat, Sep 13, 2008 at 5:21 PM, Scott David Daniels
[EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
On Sat, Sep 13, 2008 at 1:20 PM, Armin Ronacher wrote:
Iterating over weak key dictionaries might not be the most common task
but I
know some situations where this is necessary
On Thu, Sep 11, 2008 at 2:40 AM, Gerhard Häring [EMAIL PROTECTED] wrote:
As far as I can see, the specification of the dbm interface is the module
docstring in dbm/__init__.py, which reads:
[...]
It has the following interface (key and data are strings):
d[key] = data # store
On Thu, Sep 4, 2008 at 10:03 AM, [EMAIL PROTECTED] wrote:
Compared to sqlite, you don't need to know SQL, you can finetuning
(for example, using ACI instead of ACID, deciding store by store), and
you can do replication and distributed transactions (useful, for
example, if
On Thu, Sep 4, 2008 at 5:02 PM, [EMAIL PROTECTED] wrote:
me I suggested in another message (perhaps on another thread) that
me maybe a dbm.sqlite module would be worth having.
http://bugs.python.org/issue3783
I did a similar thing today. I can post my version later today.
- Josiah
On Mon, Aug 11, 2008 at 8:43 AM, zooko [EMAIL PROTECTED] wrote:
On Aug 2, 2008, at 13:58 PM, Antoine Pitrou wrote:
Martin v. Löwis martin at v.loewis.de writes:
P.S. Just in case it isn't clear: I would oppose any specific proposal
to add this Ascii85 algorithm to the standard library. It
The standard high-bit-density encoding past base-64 is base-85
(http://en.wikipedia.org/wiki/Ascii85), which encodes 4 binary bytes
as 5 ascii bytes, versus 3 binary bytes as 4 ascii bytes. It works,
is an RFC somewhere, ... and maybe should find it's way into the
Python standard library's codec
On Sat, Aug 2, 2008 at 10:09 AM, Martin v. Löwis [EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
The standard high-bit-density encoding past base-64 is base-85
(http://en.wikipedia.org/wiki/Ascii85), which encodes 4 binary bytes
as 5 ascii bytes, versus 3 binary bytes as 4 ascii bytes
On Mon, Jul 21, 2008 at 2:26 AM, Jesus Cea [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josiah Carlson wrote:
| I'm still curious as to what deep features people are using in bsddb.
| Anyone have any pointers to open source software?
I'm using replication
On Thu, Jul 24, 2008 at 7:08 PM, Greg Ewing [EMAIL PROTECTED] wrote:
Fredrik Johansson wrote:
Anyway, it is easy to define pseudo-operators in Python;
A *matrixmul* B
A *dot* B
A *cross* B
A *elementwise* B
Urg. This is another one of those recipes that I consider
is too clever for its
On Wed, Jul 23, 2008 at 2:14 PM, Sebastien Loisel [EMAIL PROTECTED] wrote:
Dear Pythonistas,
I've googled for this but I wasn't able to find anything definitive. I was
recently looking at scipy to see if I could use it in stead of MATLAB for my
class on numerical PDEs, but I noticed that
On Sat, Jul 19, 2008 at 6:44 PM, Jesus Cea [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josiah Carlson wrote:
| On-disk key - value dictionary. In every use of bsddb that I've seen
| (or done myself), that's been the extent of it's use. That's what I
On Fri, Jul 18, 2008 at 7:43 PM, Greg Ewing [EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
It's entirely possible that I know very little about what was being
made available via the bsddb module, but to match the API of what is
included in the documentation (plus the dictionary interface
On Sat, Jul 19, 2008 at 7:54 AM, Josiah Carlson
[EMAIL PROTECTED] wrote:
On Fri, Jul 18, 2008 at 7:43 PM, Greg Ewing [EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
It's entirely possible that I know very little about what was being
made available via the bsddb module, but to match the API
On Sat, Jul 19, 2008 at 3:22 AM, Nick Coghlan [EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
On Fri, Jul 18, 2008 at 11:03 AM, Fred Drake [EMAIL PROTECTED] wrote:
On Jul 18, 2008, at 1:45 PM, Josiah Carlson wrote:
It's entirely possible that I know very little about what was being
made
On Fri, Jul 18, 2008 at 7:21 AM, Guido van Rossum [EMAIL PROTECTED] wrote:
On Thu, Jul 17, 2008 at 10:43 PM, Brett Cannon [EMAIL PROTECTED] wrote:
On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum [EMAIL PROTECTED] wrote:
On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake [EMAIL PROTECTED] wrote:
On
On Fri, Jul 18, 2008 at 8:11 AM, Guido van Rossum [EMAIL PROTECTED] wrote:
On Fri, Jul 18, 2008 at 7:57 AM, Josiah Carlson
[EMAIL PROTECTED] wrote:
Invariably, when someone goes and removes a module, someone else is
going to complain, but I used feature X, not having feature X will
break my
Andy,
You had an idea, and it was a pretty good idea, but the practical
considerations made it a nonstarter. That's ok, it happens all the
time, among both new and seasoned Python developers alike. Search for
a case for top and bottom values on Google for a bit of a laugh ;) .
- Josiah
On
This doesn't need to be an interpreter thing; it's easy to implement
by the user (I've done it about a dozen times using a single global
flag). If you want it to be automatic, it's even possible to make it
happen automatically using sys.settrace() and friends (you can even
make it reasonably fast
A few years ago (yes, it's been that long), I proposed adding a new
format code to struct that would pack integers as strings, similar to
the 's' format code. In particular, struct.pack('60G', v) would be a
60-byte big-endian unsigned integer as a string. The feature request
is
I'm working on it now. I'll do my best to have a fix by the time I go
to work this morning.
- Josiah
On Tue, Jun 10, 2008 at 6:12 AM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 8:10 AM, Barry Warsaw [EMAIL PROTECTED] wrote:
I don't want to be picky, but it seems the
On Tue, Jun 10, 2008 at 8:26 AM, Giampaolo Rodola' [EMAIL PROTECTED] wrote:
On 10 Giu, 07:01, Josiah Carlson [EMAIL PROTECTED] wrote:
On Mon, Jun 9, 2008 at 7:19 PM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
On Mon, Jun 9, 2008 at 8:42 PM, Josiah Carlson [EMAIL PROTECTED] wrote:
Would
As we approach the 2.6 beta date, and after getting my updated public
key pushed to the python.org servers, I would really like to get the
asyncore/asynchat patch (with documentation) committed. Previously,
we were waiting on documentation, which the last patch had, but which
was 80 columns.
On Mon, Jun 9, 2008 at 7:19 PM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
On Mon, Jun 9, 2008 at 8:42 PM, Josiah Carlson [EMAIL PROTECTED] wrote:
Would it be ok if I committed the changes? Neal, do you want to
commit the changes if I post an updated patch with a blurb for the
NEWS file
On Mon, Mar 31, 2008 at 12:11 AM, Neal Norwitz [EMAIL PROTECTED] wrote:
On Sun, Mar 30, 2008 at 7:44 PM, Josiah Carlson
[EMAIL PROTECTED] wrote:
I haven't really had time to update the tests/documentation, but
again, I wasn't experiencing any strange test failures with
asyncore
that are not related to being unable to discover a port number?
According to the release schedule, we should have at least a couple
more months for documentation and tests to be updated (I can get
patches ready for alpha 3).
- Josiah
On Wed, Mar 26, 2008 at 12:21 AM, Josiah Carlson
[EMAIL PROTECTED] wrote
the quirks of gmail may take some time).
On Tue, Mar 25, 2008 at 10:34 PM, Josiah Carlson
[EMAIL PROTECTED] wrote:
On Tue, Mar 25, 2008 at 9:00 PM, Neal Norwitz [EMAIL PROTECTED] wrote:
On Thu, Feb 14, 2008 at 10:09 AM, Giampaolo Rodola' [EMAIL PROTECTED]
wrote:
On 14 Feb, 16:36
Let us not get side-tracked in this discussion. Whether or not to
include any portion of Twisted into Python 2.6 is well past being a
reasonable question; 2.6 alpha 1 has been released. It's a question
as to whether someone with commit access can or will commit the patch
as posted, run the tests
As far as I can tell, the asyncore.py, asynchat.py, and updated
test_asyncore.py are good. I have been using earlier variants in my
own projects (prior to their updating to pass the test suite) for
quite a few months now. The updated modules provide better
performance, features, and support for
)
asyncore.poll(timeout=thistimeout)
- Josiah
On Fri, Feb 15, 2008 at 11:45 AM, Giampaolo Rodola' [EMAIL PROTECTED] wrote:
On 15 Feb, 03:24, Josiah Carlson [EMAIL PROTECTED] wrote:
As I stated 2+ and 6+ months ago, the patches I submitted 9+ months
ago work (I've been using them in my own
) and then commit it.
I've used that same modified asynchat version in my pyftpdlib project
and I can tell that it works pretty good.
I guess that Josiah Carlson could do that pretty quickly if he has
time to do so.
Independently from all a nice thing to do would be adding tests for
many asyncore
On Dec 5, 2007 9:19 AM, Guido van Rossum [EMAIL PROTECTED] wrote:
The asyncore and asynchat modules are in a difficult position when it
comes to Python 3000. None of the core developers use it or
particularly care about it (AFAIK), and the API has problems because
it wasn't written to deal
[EMAIL PROTECTED] wrote:
Pete That points towards a way forward. Why do programming languages
Pete continue to assume use of a monospaced font? It was natural when
Pete we used punch cards and line printers, but now? Python relies on
Pete the indentation but could be
Talin [EMAIL PROTECTED] wrote:
In PEP 9 there's a requirement that PEPs must follow the emacs
convention of 2 spaces after a period. (I didn't know this was an emacs
convention, I thought it was a convention of people who used typewriters.)
If the PEP is displayed as HTML, then one or two
David Gowers [EMAIL PROTECTED] wrote:
Has anyone tried PyGEGL, the Python interface to gegl (www.gegl.org),
with SVN Python?
When I 'import gegl', that causes an immediate crash with the
following backtrace.
I would wager a beer or two that the issue is in the wrapping of gegl.
Having
Steve Holden [EMAIL PROTECTED] wrote:
Tracker wrote:
ACTIVITY SUMMARY (07/01/07 - 07/08/07)
Tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, simply click on
the issue ID. Do *not* respond to this message.
1645 open ( +0)
Brett Cannon [EMAIL PROTECTED] wrote:
On 7/5/07, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 11:53 AM 7/5/2007 +0200, Guido van Rossum wrote:
I see no big problems with this, except I wonder if in the end it
wouldn't be better to *always* define __package_name__ instead of only
when it's
Armin Ronacher [EMAIL PROTECTED] wrote:
It's one of those non issues but there are still some situations where you
have to deal with Infinity and NaN, even in Python. Basically one the problems
is that the repr of floating point numbers is platform depending and sometimes
yields nan which is
Talin [EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
Captchas like this are easily broken using computational methods, or
even the porn site trick that was already mentioned. Never mind
Stephen's stated belief, that you quoted, that he believes that even the
hard captchas are going
Aaron Brady [EMAIL PROTECTED] wrote:
Stephen J. Turnbull [EMAIL PROTECTED] wrote:
If we're going to do CAPTCHA, what we're looking for is something that
any 4 year old does automatically, but machines can't do at all.
Visual recognition used to be one, but isn't any more. The CAPTCHA
Georg Brandl [EMAIL PROTECTED] wrote:
Hi,
over the last few weeks I've hacked on a new approach to Python's
documentation.
As Python already has an excellent documentation framework, the docutils,
with a
readable yet extendable markup format, reST, I thought that it should be
possible
Talin [EMAIL PROTECTED] wrote:
Terry Reedy wrote:
My underlying point: seeing porno spam on the practice site gave me a bad
itch both because I detest spammers in general and because I would not want
visitors turned off to Python by something that is completely out of place
and
Fred L. Drake, Jr. [EMAIL PROTECTED] wrote:
On Saturday 05 May 2007, Aahz wrote:
I'm with MAL and Fred on making literals immutable -- that's safe and
lots of newbies will need to use byte literals early in their Python
experience if they pick up Python to operate on network data.
Khalid A. Bakr [EMAIL PROTECTED] wrote:
--- Martin v. Löwis [EMAIL PROTECTED] wrote:
There must be more to the problem than just an open
file. Please undo the change that triggered the
addition of the test, and see whether you
can reproduce the original problem with an arbitrary
Kumar McMillan [EMAIL PROTECTED] wrote:
I get this warning from my test suite when I introduced a segment of code:
python(18603,0xa000d000) malloc: *** Deallocation of a pointer not
malloced: 0x310caa3; This could be a double free(), or free() called
with the middle of an allocated block;
Kristján Valur Jónsson [EMAIL PROTECTED] wrote:
I just ran some static analysis of the python core 2.5 with Visual Studio
team system.
There was the stray error discovered. I will update the most obvious ones.
[snip]
2) There is a lot of code that goes like this:
f-buf =
SevenInchBread [EMAIL PROTECTED] wrote:
So I've cooked up some very simple functions to add to functools - to expand
it into a more general-purpose module.
[snip]
I don't use a functional approach very often, but I haven't ever had a
case where I would want or need to use any of the functions
Guido van Rossum [EMAIL PROTECTED] wrote:
On 4/8/07, Paul Pogonyshev [EMAIL PROTECTED] wrote:
Guido van Rossum wrote:
What if someone passes a callable that doesn't have the expected
signature?
Well, I don't know a way to catch such situations now, so removing
callable() will not
Martin v. Löwis [EMAIL PROTECTED] wrote:
The problem is that os.kill only works in Unix and Macintosh. So,
there's a better way to do this? Or I shall check if I'm in one of those
both platforms and only execute the tests there?
If you have a compilation of pywin32 (isn't it shipped
Steven Bethard [EMAIL PROTECTED] wrote:
On 4/3/07, Christian Heimes [EMAIL PROTECTED] wrote:
I'd be willing to look at adding it, if the group thinks it's the right
thing to do.
I like the idea and I'm proposing to add two more methods to subprocess
Popen.
class Popen(...):
Stephen Hansen [EMAIL PROTECTED] wrote:
I'm sure everyone remembers the big ol' honking discussion on the change to
os.splitext; it sorta fizzled after Guido asked if people would accept a
pronouncement on the subject. I'm not anyone in the Python world, but felt
strongly enough on the
Lino Mastrodomenico [EMAIL PROTECTED] wrote:
Is there any interest in a library of this kind (inside or outside of
the stdlib)?
For decoding, not many packages can currently match VLC. It has wrappers
for most major GUI toolkits, and seems to be easily accessable via
ctypes. There are also
The original went through. You likely didn't get any responses because
the proposal has text that is significantly longer than most other SoC
proposals, and perhaps people just haven't had the time to read it yet.
Also, I don't believe anyone else has posted the full text of their
proposal
Guido van Rossum [EMAIL PROTECTED] wrote:
Sure. os.fork() and the os.exec*() family can stay. But os.spawn*(),
that abomination invented by Microsoft? I also hear no opposition
against killign os.system() and os.popen().
As long as os.system migrates to subprocess.system (as you originally
Facundo Batista [EMAIL PROTECTED] wrote:
Alan Kennedy wrote:
I recommend modifying the patch to remove *all* proposed changes to
the socket module. Instead, the patch should restrict itself to fixing
the httplib module.
-1 to repeat the same functionality in 5 other libraries.
As I
Bart³omiej Wo³owiec [EMAIL PROTECTED] wrote:
For some time I'm interested in regular expressions and Finite State Machine.
Recently, I saw that Python uses Secret Labs' Regular Expression Engine,
which very often works too slow. Its pesymistic time complexity is O(2^n),
although other
Facundo Batista [EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
sentinel = object()
def connect(HOST, PORT, timeout=sentinel):
...
if timeout is not sentinel:
sock.settimeout(timeout)
...
A keyword argument via **kwargs is also fine. I have no preference
Alan Kennedy [EMAIL PROTECTED] wrote:
[snip]
def create_connection(address, timeout=sentinel):
[snip]
if timeout != sentinel:
new_socket.settimeout(timeout)
if new_socket.gettimeout() == 0:
result = new_socket.connect_ex(address)
else:
Alan Kennedy [EMAIL PROTECTED] wrote:
[Facundo]
Letting timeout be positional or named, it's just less error prone.
So, if I can make it this way, it's what I prefer, :)
So, if I want a timeout of, say, 80 seconds, I issue a call like this
new_socket =
Greg Ewing [EMAIL PROTECTED] wrote:
Alan Kennedy wrote:
The standard mechanism in C for doing a non-blocking connect is to
issue the connect call, and check the return value for a non-zero
error code. If this error code is errno.EAGAIN (code 10035), then the
call succeeded, but you
Alan Kennedy [EMAIL PROTECTED] wrote:
I'm working on a select implementation for jython (in combination with
non-blocking sockets), and a set of unit tests for same.
Great!
[snip]
But when I run the code on cpython, the code reports that both calls
would block, i.e. that neither side of the
Greg Ewing [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Can you suggest any use-cases for thread termination which will *not*
result in a completely broken and unpredictable heap after the thread
has died?
Suppose you have a GUI and you want to launch a
long-running
Gordon Messmer [EMAIL PROTECTED] wrote:
After some discussion, Aahz suggested that I discuss the problem here,
on python-dev. He seemed to think that the problem I saw may have been
an indication of a bug in python. Could anyone take a look at that
thread and say whether it looks like a
Martin v. Löwis [EMAIL PROTECTED] wrote:
Phillip J. Eby schrieb:
I consider it correct, or at the least, don't think it should be
changed, as it would make the behavior more difficult to reason about
and introduce yet another thing to worry about when writing
cross-version code.
1 - 100 of 478 matches
Mail list logo
