> On 12/8/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> > fwiw, I've seen a 2.5x ratio for my stuff over the last year; I've always
> > assumed
> > that most people on other platforms are simply getting their stuff from the
> > vendor's
> > standard repository.
I've noticed a similar thing, bu
"Albert Strasheim" <[EMAIL PROTECTED]> wrote:
> As part of the Windows Vista release, Microsoft have created the "Windows
> SDK" that looks like Platform SDK on steroids. It includes 32-bit and 64-bit
> libraries and compilers, debugging tools, etc. and supports Windows XP,
> Windows Server 200
Jeremy Kloth <[EMAIL PROTECTED]> wrote:
> [[ This may be somewhat c.l.p.-ish but I feel that this crossed into CPython
> development enough to merit posting here ]]
>
> I have received a bug report for 4Suite that involves a PyObject_IsInstance
> check failing for what appears to be the correct
Evgeniy Khramtsov <[EMAIL PROTECTED]> wrote:
>
> The question to python core developers:
> Is there any plans to implement non-blocking timer like a
> threading.Timer() but without thread?
> Some interpreted languages (like Tcl or Erlang) have such functionality,
> so I think it would be a grea
Evgeniy Khramtsov <[EMAIL PROTECTED]> wrote:
> Mike Klaas пиÑеÑ:
>
> > I'm not sure how having python execute code at an arbitrary time would
> > _reduce_ race conditions and/or deadlocks. And if you want to make it
> > safe by executing code that shares no variables or resources, then it
>
"Christos Georgiou" <[EMAIL PROTECTED]> wrote:
>
> Hello, people. I am not sure whether this is a bug or intentional, so I
> thought checking it with you before opening a bug. I will explain this
> issue, but please understand this is not a question for help to change the
> algorithm (this has
"Terry Reedy" <[EMAIL PROTECTED]> wrote:
> "A.M. Kuchling" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> | [*] Anyone else keep wanting to write "byte type"?
>
> All the other builtin types I can think of are singular. So I think byte
> should be also.
But a "byte" already
Larry Hastings <[EMAIL PROTECTED]> wrote:
> I just ran a quickie experiment and determined: when leaving a scope,
> variables are deleted FIFO, aka in the same order they were created.
> This surprised me; I'd expected them to be deleted LIFO, aka last
> first. Why is it thus? Is this behavi
"Brett Cannon" <[EMAIL PROTECTED]> wrote:
> I have discovered an issue relating to func_globals for functions and
> the deallocation of the module it is contained within. Let's say you
> store a reference to the function encodings.search_function from the
> 'encodings' module (this came up in C c
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson schrieb:
> > Seems to me like a bug, but the bug could be fixed if the module's
> > dictionary kept a (circular) reference to the module object. Who else
> > has been waiting for
Neal Becker <[EMAIL PROTECTED]> wrote:
[snip]
> It's not a question, it's a critique. I believe this is a misfeature since
> it's so easy to make this mistake.
And it is going away with Py3k. Making it go away for Python 2.6 would
either allow for two syntaxes to do the same thing, or would req
"Phillip J. Eby" <[EMAIL PROTECTED]> wrote:
>
> At 01:17 PM 1/20/2007, Josiah Carlson wrote:
>
> >Neal Becker <[EMAIL PROTECTED]> wrote:
> >[snip]
> > > It's not a question, it's a critique. I believe this is a misfeature
> &g
Nick Maclaren <[EMAIL PROTECTED]> wrote:
>
> Oops. Something else fairly major I forgot to ask. Python long.
> I can't find any clean way of converting to or from this, and
> would much rather not build a knowledge of long's internals into
> my code. Going via text is, of course, possible - bu
"Guido van Rossum" <[EMAIL PROTECTED]> wrote:
> Thank you guys! Now I want something fun to do with my life again too! :-)
You could hand BDFL responsibilities off onto perhaps Tim, Raymond, or
Martin for a few months and try to convince Google to open an office in
Hawaii. Pick up one of those T
See the two threads started in python-dev by Tomer Filiba on (according
to my clock) July 6, 2006 and October 6, 2006, both have __dir__ in the
subject.
- Josiah
Giovanni Bajo <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I could not find a PEP for __dir__. I was thinking today that if __dir__ wa
"Guido van Rossum" <[EMAIL PROTECTED]> wrote:
>
> I recently needed to access an HTTP URL with a timeout. I ended up
> monkey-patching httplib.HTTPConnection so that the connect() method
> has an optional second paramer, timeout, defaulting to None; if not
> None, a call to settimeout() is added
Hrvoje Nikic <[EMAIL PROTECTED]> wrote:
>
> I propose modifying PyString_InternInPlace to better cope with string
> subtype instances.
Any particular reason why the following won't work for you?
_interned = {}
def intern(st):
#add optional type checking here
if st not in _interned:
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Richard Tew schrieb:
> > but at that stage I need to
> > poll two different resources for events. In order to avoid this it makes
> > sense to stop using asyncore for sockets and to write a new
> > replacement socket object based on IO completion por
Anthony Baxter <[EMAIL PROTECTED]> wrote:
> > The performance question is important, certainly. Initial
> > reaction on python-ideas was that a 1% cost would not count as
> > substantial
>
> I'd disagree. Those 1% losses add up, and it takes a heck of a lot
> of work to claw them back. Again, t
Ron Adam <[EMAIL PROTECTED]> wrote:
> Georg Brandl wrote:
> Would it be possible for attrview to be a property?
Yes, but getting the right spelling will be hard.
> Something like... (Probably needs more than this to handle all cases.)
>
> class obj(object):
> def _attrview(self):
"Greg Falcon" <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > Also, Nick's examples show (conceptual)
> > aliasing problems: after "x = attrview(y)", both x and y refer to the
> > same object, but use a different notation to access it.
>
> Of course there is an aliasing here, but it's be
Greg Ewing <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson wrote:
> > def intern(st):
> > ...
> >
> > If I remember the implementation of intern correctly, that's more or
> > less what happens under the covers.
>
> That doesn't qu
Tristan Seligmann <[EMAIL PROTECTED]> wrote:
> * Richard Tew <[EMAIL PROTECTED]> [2007-02-14 16:49:03 +]:
>
> > I am not writing a competing event driven mechanism. What I was doing
> > was feeling out whether there was any interest in better support for
> > asynchronous calls.
>
> I interp
Greg Ewing <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson wrote:
>
> > Assuming that dictionaries and the hash algorithm for strings is not
> > hopelessly broken, I believe that one discovers quite quickly when two
> > strings are not equal.
>
> You
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] schrieb:
> > Asyncore *only* implements asynchronous IO -- any "tasks" performed in
> > its context are the direct result of an IO operation, so it's hard to
> > say it implements cooperative multitasking (and Josiah can correct m
Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
> On Thu, 15 Feb 2007 02:36:22 -0700, Andrew Dalke <[EMAIL PROTECTED]> wrote:
[snip]
> >2) asyncore is
> >smaller and easier to understand than Twisted,
>
> While I hear this a lot, applications written with Twisted _are_ shorter and
> contain less i
Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
>
> On Thu, 15 Feb 2007 13:55:31 -0800, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> >
> >Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
> > [snip]
> >>
> >> Now if we can only figu
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>
> Larry Hastings schrieb:
> > Oof! I'm embarrassed to have forgotten that. But that's not a fatal
> > problem. It means that on Windows the PerfectReactor must service the
> > blocking GetMessage loop, and these other threads notify the
> > Per
"Raymond Hettinger" <[EMAIL PROTECTED]> wrote:
> > Raymond Hettinger schrieb:
> >> d, g, v, t, r = model(somecontract)
>
> [MvL]
> > I find that line quite unreadable
>
> Of course, I can't give you the fully spelled-out line from proprietary code.
> But at this point we're just talking about t
Larry Hastings <[EMAIL PROTECTED]> wrote:
> For new code, I can't think of a single place I'd want to use a
> "NamedTuple" where a "record" wouldn't be arguably more suitable. The
> "NamedTuple" makes sense only for "fixing" old APIs like os.stat.
I disagree.
def add(v1, v2)
retu
Larry Hastings <[EMAIL PROTECTED]> wrote:
>
> Steven Bethard wrote:
> > On 2/20/07, Larry Hastings <[EMAIL PROTECTED]> wrote:
> >> I considered using __slots__, but that was gonna take too long.
> > Here's a simple implementation using __slots__:
>
> Thanks for steering me to it. However, your
Larry Hastings <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson wrote:
> > one thing to note with your method - you can't guarantee the order
> > of the attributes as they are being displayed.
> >
> Actually, my record type *can*; see the hack using the
"Steven Bethard" <[EMAIL PROTECTED]> wrote:
[snip]
> In short, for object construction and attribute access, the Record
> class is faster (because __init__ is a simple list of assignments and
> attribute access is through C-level slots). For unpacking and
> iteration, the NamedTuple factory is fa
Larry Hastings <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson wrote:
> > Larry Hastings <[EMAIL PROTECTED]> wrote:
> >
> >> Josiah Carlson wrote:
> >>
> >>> one thing to note with your method - you can't guaran
Jordan Greenberg <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > How would this change be helpful? I'm utterly mystified by these
> > suggestions that bool would be more useful if it didn't behave like an
> > int in arithmetic.
>
> I don't think anyones really saying it would be more
"Chris AtLee" <[EMAIL PROTECTED]> wrote:
> I just got bitten by the runtime library incompatibility problem on
> windows when I tried to load a C extension compiled with MSVC 2005
> (64-bit) into Python 2.5.
I would guess it is more an issue of 32bit + 64bit dynamic linking
having issues, but I c
Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> On 05/03/2007 20.30, Phil Thompson wrote:
> > 2. Publically identify the core developers and their areas of expertise and
> > responsibility (ie. which parts of the source tree they "own").
>
> I think this should be pushed to its extreme consequences f
"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
Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> On 3/6/2007 3:11 AM, Josiah Carlson wrote:
> > Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> >> I think this should be pushed to its extreme consequences for the standard
> >> library. Patching the standard libr
Andrew Bennetts <[EMAIL PROTECTED]> wrote:
> Glyph's proposing that rather than risk breaking existing code (and in the
> worst
> possible way: silently, giving wrong answers rather than exceptions), we
> examine
> what benefits changing splitext would bring, and see if there's a way to get
> th
Andrew Bennetts <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson wrote:
> [...]
> >
> > Offer a new splitext that uses X on posix and Y on win32, but causes a
> > DeprecationWarning with pointers to the two renamed functions that are
> > available on both
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 li
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-run
"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
"Steven Bethard" <[EMAIL PROTECTED]> wrote:
> On 3/20/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> > So, I have two modifications to make to the patch:
> >
> > - change the name to "create_connection"
> > - make timeout obligatory named
> >
> > Is everybody ok with this?
>
> FWLIW, +1. It wa
Facundo Batista <[EMAIL PROTECTED]> wrote:
> Josiah Carlson wrote:
> > sentinel = object()
> >
> > def connect(HOST, PORT, timeout=sentinel):
> > ...
> > if timeout is not sentinel:
> > sock.settimeout(timeout)
> > ...
>
"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:
>new_
"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 = socket.create_co
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
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.
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
"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 origina
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 publi
"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 al
"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
Facundo Batista <[EMAIL PROTECTED]> wrote:
> Jean-Paul Calderone wrote:
> > If the openssl binary is available, when the test starts, launch it in
> > a child process, talk to it for the test, then kill it when the test is
> > done.
>
> Ok, I have a demo of this.
>
> Right now, I face this probl
"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 (
"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.
> >
> > c
"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
> >
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 functio
"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
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 = PyMem_R
"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 a
"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 networ
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
> >
"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. Th
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
>
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 tha
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)...
http://mail.python.org/pipermail/python-3000/2006-September/003795.
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"
"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 onl
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.
>
"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
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
[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 co
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 dea
hancements & new features ===
>
> - 1641 (add delayed calls feature)
> - 1563 (conversion to py3k and some other changes)
>
>
> IMHO the first thing to do should be modifying 1736190 patch to fix
> the minor issues came out in comments 52767 (re-add simple_producer
&
asks[0][0]-now), 0)
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 pat
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 r
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
ering 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
s
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
<[EM
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 was
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. Th
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 u
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 seem
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:
>> > O
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 http://bugs.pytho
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
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 S
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]
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 f
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 available via the bsddb module, but to match the A
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
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
>
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:
>>>>
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 t
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 tha
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 s
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 t
101 - 200 of 548 matches
Mail list logo
