On 4/07/2011 3:59 PM, Greg Ewing wrote:
Mark Hammond wrote:
On 2/07/2011 7:08 PM, Vinay Sajip wrote:
perhaps we could remember the last non-launcher association when we
install the launcher,
It might be better to look in the registry for other Python
installations and ask the user which on
Mark Hammond wrote:
On 2/07/2011 7:08 PM, Vinay Sajip wrote:
perhaps we could remember the last non-launcher association when
we install the launcher,
It might be better to look in the registry for other Python
installations and ask the user which one to restore if there
is more than one. T
2011/7/3 Nick Coghlan :
> On Mon, Jul 4, 2011 at 12:54 PM, Benjamin Peterson
> wrote:
>> 2011/7/3 Nick Coghlan :
>>> May need to replace that with an assert(f != NULL) to keep static
>>> analysers happy.
>>
>> Surely static analyzers don't assume every argument passed in is NULL?
>
> I didn't che
On Mon, Jul 4, 2011 at 12:54 PM, Benjamin Peterson wrote:
> 2011/7/3 Nick Coghlan :
>> May need to replace that with an assert(f != NULL) to keep static
>> analysers happy.
>
> Surely static analyzers don't assume every argument passed in is NULL?
I didn't check - was this change in a static func
2011/7/3 Nick Coghlan :
> On Mon, Jul 4, 2011 at 8:02 AM, benjamin.peterson
> wrote:
>> http://hg.python.org/cpython/rev/bbbeddafeec0
>> changeset: 71160:bbbeddafeec0
>> user: Benjamin Peterson
>> date: Sun Jul 03 17:06:32 2011 -0500
>> summary:
>> no one passes NULL here (or sho
On Mon, Jul 4, 2011 at 8:02 AM, benjamin.peterson
wrote:
> http://hg.python.org/cpython/rev/bbbeddafeec0
> changeset: 71160:bbbeddafeec0
> user: Benjamin Peterson
> date: Sun Jul 03 17:06:32 2011 -0500
> summary:
> no one passes NULL here (or should anyway)
>
> files:
> Python/c
On Mon, Jul 4, 2011 at 9:24 AM, Alejandro Santos wrote:
> Should I report a new issue?
Yes please, tracker items are the best way to get that kind of
oversight cleaned up. Thanks for noticing!
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
Hi,
While reading through the Extending and Embedding docs for Python 3.2
I've noticed something. While the "Py_InitModule" does not exists on
Py3k, it is still mentioned on the docs:
http://docs.python.org/py3k/extending/extending.html#keyword-parameters-for-extension-functions
http://docs.pytho
On 3 July 2011 19:20, Vinay Sajip wrote:
> Paul Moore gmail.com> writes:
>
>> OK, having looked through this, it looks pretty solid to me. I might
>> try installing Vinay's implementation and seeing how it feels in use,
>> as well...
>
> Do have a play, it would be nice to get feedback. It's only
Paul Moore gmail.com> writes:
> OK, having looked through this, it looks pretty solid to me. I might
> try installing Vinay's implementation and seeing how it feels in use,
> as well...
Do have a play, it would be nice to get feedback. It's only available as source,
though - is that OK?
> I'd
On 30 June 2011 13:50, Paul Moore wrote:
> On 30 June 2011 12:13, Michael Foord wrote:
>> I have that email (the update one from Mark not the silent nodding from Tim)
>> still sitting in my inbox waiting for me to properly read through and
>> comment on... Sorry for being useless, I'll try and mo
Mark Hammond gmail.com> writes:
> But this only happens when they install a later version, then uninstall
> the later one and continue to use the old one. I'd suggest that is (a)
> rare and (b) possibly already broken (ie, the old association may not be
> restored now). If the old associatio
Mark Hammond gmail.com> writes:
> I'm not fundamentally opposed to doing something better here - I'm just
> trying to avoid this kind of stuff being a requirement for acceptance.
> If you are more familiar with the installer than I and feel it can be
> done simply, then I'm happy for you to go
On 2/07/2011 7:08 PM, Vinay Sajip wrote:
Mark Hammond gmail.com> writes:
The PEP does say "if possible, should be installed somewhere likely to
already be on the system PATH (eg., the Windows System32) directory."
It is silent about what to do when that isn't possible, but I'd think it
OK if
14 matches
Mail list logo