It would be great if you could open a bug at sourceforge...
Mark
On 9/06/2014 11:07 PM, Christian K. wrote:
Hi,
I was very pleased to see that retrieving properties of a MAPI object yields
either a str or bytes type depending on whether the _A or _W property
was queried and entryids are
On Jun 9, 2014, at 9:40 PM, Christian K. ckk...@hoc.net wrote:
Am 09.06.14 16:00, schrieb paul_kon...@dell.com:
On Jun 9, 2014, at 2:53 PM, Christian K. ckk...@hoc.net wrote:
Paul_Koning at Dell.com writes:
On Jun 9, 2014, at 9:07 AM, Christian K. ckkart at hoc.net wrote:
Hi,
paul_kon...@dell.com wrote:
Perhaps I’m missing something.
I'm not sure you're missing anything. You're simply describing another
implementation choice that could have been made. Both your scheme and
the actual scheme have their merits.
I’m used to Windows API calls that come in a foo_A and
Paul_Koning at Dell.com writes:
On Jun 9, 2014, at 9:40 PM, Christian K. ckkart at hoc.net wrote:
Am 09.06.14 16:00, schrieb Paul_Koning at Dell.com:
On Jun 9, 2014, at 2:53 PM, Christian K. ckkart at hoc.net wrote:
Paul_Koning at Dell.com writes:
On Jun 9, 2014, at
Mark Hammond skippy.hammond at gmail.com writes:
It would be great if you could open a bug at sourceforge...
Done.
___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
Christian K. ckkart at hoc.net writes:
Paul_Koning at Dell.com writes:
I would only want/expect to see “bytes” types when the values in question
are binary data streams, or
unknown format. But anytime we’re dealing with text strings, the Python 3
approach is that the Python
code
