[Python-Dev] PEP 514 and pywin32

[Glenn Linderman]

So today I tried to install pywin32 on my new Python 3.6.0 and got the 
following error:


---
Cannot install
---
Python version 3.6-32 required, which was not found in the registry.
---
OK
---

Seems like pywin32, although built for 3.6, doesn't understand or 
conform to the PEP 514? So the installer doesn't work? I suspect maybe 
the code would still work, if it would install. I also noted that pip 
cannot find a compatible pywin32, and PyPI only reports compatibility 
through Python 3.3.


1. Where should this be reported? SourceForge?
2. Anyone know a workaround?

--
Glenn

Experience is that marvelous thing that enables you to recognize a
mistake when you make it again. -- Franklin Jones
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Merry Christmas to me, and Python users everywhere

[Glenn Linderman]

On 12/27/2016 8:09 AM, Ethan Furman wrote:

On 12/26/2016 08:46 PM, Glenn Linderman wrote:

So either Google (my email host) noticed that I got 3 of the same 
message,
 and suppressed two of them, or the python-dev mail server that hosts 
the
 mailing lists merged the expanded destinations with duplicate 
suppression.

 I'm inclined to think the former is more likely.


I am also subscribed to those mailing lists, I do not use gmail, and I 
got all three.


Thanks for this extra information, Ethan. That points at Gmail pretty 
conclusively as the source of the reduction in number of messages. Since 
it has long been known that Gmail suppresses CC or BCC to self, it is 
likely that suppressing duplicate messages from cross-posted mailing 
lists is also done... likely achieved due to matching Message-Id values.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Document C API that is not part of the limited API

[Ronald Oussoren]

> On 27 Dec 2016, at 20:04, Serhiy Storchaka  wrote:
> 
> From the documentation:
> 
> https://docs.python.org/3/c-api/stable.html
> 
>In the C API documentation, API elements that are not part of the limited 
> API are marked as "Not part of the limited API."
> 
> But they don't.
> 
> I prepared a sample patch that adds the notes to Unicode Objects and Codecs C 
> API (http://bugs.python.org/issue29086). I'm going to add them to all C API.
> 
> What are your though about formatting the note? Should it be before the 
> description, after the description, but before the "deprecated" directive (as 
> in the patch), or after the first paragraph of the description? Should it be 
> on the separate line or be appended at the end of the previous paragraph, or 
> starts the first paragraph (if before the description)? May be introduce a 
> special directive for it?

A directive would make it easier to ensure that the text about the stable API 
is consistent.  I’d also consider adding that directive to all API’s that *are* 
part of the stable API instead of the other way around (that would also require 
changes to …/stable.html). That would have two advantages: firstly it makes it 
easier to document from which version an API is part of the stable ABI, and 
secondly forgetting the annotation would imply that an API is not part of the 
stable ABI instead of accidentally claiming to increase the stable ABI.

Ronald

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Document C API that is not part of the limited API

[Serhiy Storchaka]

From the documentation:

https://docs.python.org/3/c-api/stable.html

In the C API documentation, API elements that are not part of the 
limited API are marked as "Not part of the limited API."


But they don't.

I prepared a sample patch that adds the notes to Unicode Objects and 
Codecs C API (http://bugs.python.org/issue29086). I'm going to add them 
to all C API.


What are your though about formatting the note? Should it be before the 
description, after the description, but before the "deprecated" 
directive (as in the patch), or after the first paragraph of the 
description? Should it be on the separate line or be appended at the end 
of the previous paragraph, or starts the first paragraph (if before the 
description)? May be introduce a special directive for it?



___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Merry Christmas to me, and Python users everywhere

[Ethan Furman]

On 12/26/2016 08:46 PM, Glenn Linderman wrote:


So either Google (my email host) noticed that I got 3 of the same message,
 and suppressed two of them, or the python-dev mail server that hosts the
 mailing lists merged the expanded destinations with duplicate suppression.
 I'm inclined to think the former is more likely.


I am also subscribed to those mailing lists, I do not use gmail, and I got all 
three.

--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com