Am 15.10.2011 01:32, schrieb Greg Ewing:
> Martin v. Löwis wrote:
>> That wouldn't be instead, but in addition - you need the
>> variable name, anyway.
>
> But the details of exactly how the name is constructed
> could be kept as an implementation detail.
Is there a use case for keeping that deta
Martin v. Löwis wrote:
That wouldn't be instead, but in addition - you need the
variable name, anyway.
But the details of exactly how the name is constructed
could be kept as an implementation detail.
Not sure whether there is actually
a gain in readability - people not familiar with this wou
Instead of an explicit prefix, how about a macro, such as
Py_ID(__string__)?
That wouldn't be instead, but in addition - you need the
variable name, anyway. Not sure whether there is actually
a gain in readability - people not familiar with this would
assume that it's a function call of some kin
On 14 October 2011 17:46, "Martin v. Löwis" wrote:
>
>> - On formats, I strongly believe that having multiple formats is a
>> problem. But I need to be clear here - an installer (MSI, wininst) is
>> a bundle containing executable code (which drives the interface), plus
>> a chunk of data that is t
- On formats, I strongly believe that having multiple formats is a
problem. But I need to be clear here - an installer (MSI, wininst) is
a bundle containing executable code (which drives the interface), plus
a chunk of data that is the objects to be installed. (I am
oversimplifying here, but bea
ACTIVITY SUMMARY (2011-10-07 - 2011-10-14)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open3077 (+25)
closed 21884 (+31)
total 24961 (+56)
Open issues wit
On 14 October 2011 15:13, "Martin v. Löwis" wrote:
>> Thanks for the clarification. I can see why this would be important.
>> But maintaining 3 different interfaces to do essentially the same
>> thing (collect some data from the user, then based on that data put
>> the same set of files in the sam
One other aspect is that MSI format is essentially opaque (correct me
if I'm wrong here).
You are wrong: msiexec /a unpacks an MSI extracts the files from the
MSI (documented as "administrative installation", meaning that the
result of it can again be installed, as it will also produce a
strippe
Hi Antoine,
> changeset: 701b2e0e6f3f
> user:Antoine Pitrou
> date:Thu Oct 13 18:07:37 2011 +0200
> summary:
> Add a comment explaining this heuristic.
>
> diff --git a/Objects/stringlib/fastsearch.h b/Objects/stringlib/fastsearch.h
> --- a/Objects/stringlib/fastsearch.h
> ++
On 14 October 2011 15:07, "Martin v. Löwis" wrote:
>> I can't really comment on this. I agree in principle with what you're
>> saying, but I know little about the MSI format so I can't say much
>> more. It feels to me like you're suggesting that the MSI file
>> encapsulate the file layout logic th
On Oct 14, 2011, at 04:08 PM, Martin v. Löwis wrote:
>It actually is _Py_IDENTIFIER (and was _Py_identifier).
Yep, I saw your commit to make the change. Thanks!
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@p
Thanks for the clarification. I can see why this would be important.
But maintaining 3 different interfaces to do essentially the same
thing (collect some data from the user, then based on that data put
the same set of files in the same places) seems a waste of effort, and
a recipe for discrepanci
Am 13.10.11 20:38, schrieb Barry Warsaw:
On Oct 13, 2011, at 08:08 PM, Martin v. Löwis wrote:
Py_CONST_STRING or Py_IDENTIFIER would be fine with me. Given that
everything else uses "Id" in their name, Py_IDENTIFIER is probably better?
I agree that either is fine, with a slight preference fo
I can't really comment on this. I agree in principle with what you're
saying, but I know little about the MSI format so I can't say much
more. It feels to me like you're suggesting that the MSI file
encapsulate the file layout logic that already has to exist in
pysetup, though, which sounds like d
Le 14/10/2011 07:44, Georg Brandl a écrit :
Am 14.10.2011 00:30, schrieb Victor Stinner:
Le jeudi 13 octobre 2011 03:34:00, Victor Stinner a écrit :
We would need a new format for Py_BuildValue, e.g. 'a' for ASCII string.
Later we can add new functions like _PyDict_GetASCII().
The main differ
15 matches
Mail list logo
