the
> future more attention is paid to "documenting" publicly that someone's
> being booted out was inevitable, by an exchange of messages on
> python-dev (or python-committers if we want to limit distribution).
> And no, I don't think that IRC (where
So if there turns out to be a major security hole or sever bug in 2.7,
then it shouldn't be filed against 2.7? and fixed in a 2.7.x sort of
branch?
In that case, would you just suggest everyone using 2.7 to jump to 3.x?
As long as a 2.x version is supported, filing bugs, branching and even
relea
have. Is there still
interest/motivation for supporting generic functions in the standard
library?
Darren
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/opt
On Sat, Sep 12, 2009 at 9:57 AM, Darren Dale wrote:
> I would be very interested in seeing a framework for generic functions
> in the numpy standard library.
Sorry, I meant to say "python standard library"
___
Python-Dev mailing
it that isn't
> strictly necessary to provide the feature listed in the rationale.
It would be nice to have a suitable foundation upon which more
elaborate third party dispatchers could build. The potential generic
functions have in a project like numpy are pretty exciting.
Darren
__
Hi Paul,
On Sun, Sep 13, 2009 at 10:54 AM, Paul Moore wrote:
> 2009/9/13 Darren Dale :
>>> If Phillip doesn't respond here, you may want to ask him directly.
>>> My impression is that it is deferred because nobody is pursuing it
>>> actively (including Philli
17:02:06) an ubuntu Karmic. Is it a known
issue, or am I misreading the documentation?
Thanks,
Darren
___
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.com
On Sun, Oct 18, 2009 at 10:50 AM, Darren Dale wrote:
> According to http://docs.python.org/reference/datamodel.html , the
> reflected operands functions like __radd__ "are only called if the
> left operand does not support the corresponding operation and the
> operands are of di
ion``). It's not about strictness
>> or looseness.
>
> I agree about the impreciseness of these terms. I'm not sure what the
> correct terminology is...
Those aren't new proposals, though, they already exist in distutils.
Darren
__
On Thu, Dec 10, 2009 at 7:43 AM, Malthe Borch wrote:
> 2009/12/10 Darren Dale :
>> Those aren't new proposals, though, they already exist in distutils.
>
> I see. Thanks for clarifying –– maybe the PEP should better explain this.
It is already pretty clear:
"Distu
gotiator.
Standard (according to websters.com):
1. something considered by an authority or by general consent as a
basis of comparison; an approved model.
2. an object that is regarded as the usual or most common size or form
of its kind
3. a rule or pri
thing explicit when building python 2.6.5 to find
the updated sqlite3?
thanks for any tips.
Darren
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pytho
created in a thread can only be used in
that same thread.The object was created in thread id -1217128768 and
this is thread id -1218753680
I set the -DSQLITE_THREADSAFE=1 flag on sqlite3 when I configured, built
and installed the lib.
Darren
On Mon, 2010-03-08 at 22:52 +0100, "Martin v. Löwis&q
That worked great Oleg! Thank you!
On Tue, 2010-03-09 at 01:52 +0300, Oleg Broytman wrote:
> On Mon, Mar 08, 2010 at 05:28:10PM -0500, Darren Govoni wrote:
> > ProgrammingError: SQLite objects created in a thread can only be used in
> > that same thread.The object was creat
ributed separately?
Darren
___
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.com
le-version-externally-managed --no-deps
> --record some_tmp_file
>
> The --no-deps keeps Setuptools from resolving dependencies
Seeking clarification: how can pip recursively install dependencies
*and* keep Setuptools from resolving dependencies?
Darren
__
ed. I'm still
unclear as to why they might be discouraged. I recently helped convert
a popular package to use PEP 328 relative imports. Would the python
devs consider this a mistake?
Thanks,
Darren
___
Python-Dev mailing list
Python-Dev@python.org
http
red
version of foo. This is not a hypothetical, we once had exactly this
problem when we distributed an old version of enthought.traits with
matplotlib (even though we checked for pre-existing installations,
crufty build/ directories containing the out-of-date traits package
were overwriting existing in
On Tue, Oct 5, 2010 at 1:45 PM, Antoine Pitrou wrote:
> Le mardi 05 octobre 2010 à 13:28 -0400, Darren Dale a écrit :
>> >>
>> >> As the OP pointed out, for code that may be *included* in other projects
>> >> there is no other choice. This is often useful f
On Tue, Oct 5, 2010 at 3:37 PM, Terry Reedy wrote:
> On 10/5/2010 2:21 PM, Guido van Rossum wrote:
>>
>> On Tue, Oct 5, 2010 at 11:17 AM, Darren Dale wrote:
>>>
>>> The issue is implementing a PEP with nice support for relative
>>> imports, and the
hey have priority.
However, styleguide.html does not explain that the PEPs are more up-to-date.
We shouldn't expect someone to go to the PEPs after finding an answer to
their question in the styleguide.
Perhaps one of these documents could be revised
the property builtin, documentation, and unit tests.
Unfortunately, I have not been able to python-3.3 from a mercurial
checkout on either Ubuntu 11.04 or OS X 10.6.6 (for reasons unrelated
to the patch), and so I have not been able to test the patch.
Darren
On Sat, Mar 19, 2011 at 3:06 PM, Darren Dale wrote:
> I suggested at python-ideas a way that the declaration of abstract
> properties could be improved to support the decorator syntax:
> http://mail.python.org/pipermail/python-ideas/2011-March/009411.html .
> A relatively small c
=python-3.3 should be
extended to provide examples with properties/descriptors. The syntax would be
backward compatible with older python versions, but with =python3.3. In my opinion, this is a feature: python-3.3 has identified a bug
in ConcreteFoo. The developer would not have tagged that meth
On Wed, Jun 8, 2011 at 11:55 AM, Nick Coghlan wrote:
> On Thu, Jun 9, 2011 at 1:01 AM, Darren Dale wrote:
> [snip excellent analysis of the problem]
>
> I have some suggestions regarding a few details of your current code,
> but your basic proposal looks sound to me.
>
>
On Wed, Jun 8, 2011 at 10:01 PM, Nick Coghlan wrote:
> On Thu, Jun 9, 2011 at 8:51 AM, Darren Dale wrote:
>>> for base in bases:
>>> for name in getattr(base, "__abstractmethods__", ()):
>>> # CHANGE 4: Using rpartition
26 matches
Mail list logo
