[Python-Dev] Python Documentation Translation in italian language

[Alessandro Cucci]

Hello folks,
I want to start a project for translating the Python Documentation in
Italian.
I'm reading the PEP545, trying to understand how it works.

I founded a Python User Group in my city and I can work with them on the
translations, plus next month I will be speaker at Pycon Italy, so I can
easily sponsor this project during the talk and reclute more people to work
on that.

Is there anybody who can help me to start?
Thanks, have a nice day.

*Alessandro Cucci*
___
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] Concurrent.futures: no type discovery for PyCharm

[Ilya Kamenshchikov]

I am using concurrent.futures to parallelize independent tasks on multiple
cores once in a while. Each time I have a difficulty remembering the
specific syntax and have to look it up in old code or google. I would much
prefer to be able to find the source through the PyCharm and have
autocompletion. It takes adding two lines to the __init__.py of
concurrent.futures:

(insert on line 19)

from .process import ProcessPoolExecutor
from .thread import ThreadPoolExecutor

I would also guess that it would make the __getattr__ redundant?

Am I missing something or can this change be done this way and would
indeed be an improvement?

Best Regards,
--
Ilya Kamenshchikov
___
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] Concurrent.futures: no type discovery for PyCharm

[Inada Naoki]

See https://bugs.python.org/issue32596
___
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] Concurrent.futures: no type discovery for PyCharm

[Ilya Kamenshchikov]

alright, so would an import under TYPE_CHECKING guard be an option? like:

from typing import TYPE_CHECKING
if TYPE_CHECKING:
from .process import ProcessPoolExecutor
from .thread import ThreadPoolExecutor


Perhaps we can have both clarity and performance.
___
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] Python Documentation Translation in italian language

[Terry Reedy]

On 4/20/2019 4:14 AM, Alessandro Cucci wrote:

Hello folks,
I want to start a project for translating the Python Documentation in 
Italian.

I'm reading the PEP545, trying to understand how it works.

I founded a Python User Group in my city and I can work with them on the 
translations, plus next month I will be speaker at Pycon Italy, so I can 
easily sponsor this project during the talk and reclute more people to 
work on that.


Is there anybody who can help me to start?
Thanks, have a nice day.


Devguide:
"7.6. Translations

There are now several official documentation translations (see section 
21.5. Documentation Translations and PEP 545 for details). Discussions 
about translations occur on the doc-sig mailing list."


There is no Italian translation yet.  There may or may not be one in 
progress.  Post to doc-sig.


https://mail.python.org/mailman/listinfo/doc-sig


--
Terry Jan Reedy

___
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] Concurrent.futures: no type discovery for PyCharm

[Inada Naoki]

"import typing" is slow too.

2019年4月21日(日) 1:43 Ilya Kamenshchikov :

> alright, so would an import under TYPE_CHECKING guard be an option? like:
>
> from typing import TYPE_CHECKING
> if TYPE_CHECKING:
> from .process import ProcessPoolExecutor
> from .thread import ThreadPoolExecutor
>
>
> Perhaps we can have both clarity and performance.
>
>
___
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] Concurrent.futures: no type discovery for PyCharm

[Glenn Linderman]

On 4/20/2019 2:08 PM, Inada Naoki wrote:

"import typing" is slow too.

2019年4月21日(日) 1:43 Ilya Kamenshchikov >:


alright, so would an import under TYPE_CHECKING guard be an
option? like:

from typingimport TYPE_CHECKING
if TYPE_CHECKING:
 from .processimport ProcessPoolExecutor
 from .threadimport ThreadPoolExecutor

Perhaps we can have both clarity and performance.



How about:


from faketyping import TYPE_CHECKING

where faketyping.py:

TYPE_CHECKING = None


I don't know enough about how TYPE_CHECKING (or typing) is optionally 
enabled to come up with an exactly correct proposal.
___
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] Concurrent.futures: no type discovery for PyCharm

[Nathaniel Smith]

On Sat, Apr 20, 2019 at 2:11 PM Inada Naoki  wrote:
>
> "import typing" is slow too.

Many static analysis tools will also accept:

TYPE_CHECKING = False
if TYPE_CHECKING:
...

At least mypy and pylint both treat all variables named TYPE_CHECKING
as true, regardless of where they came from. I'm not sure if this is
intentional or because they're cutting corners, but it works...

-n

-- 
Nathaniel J. Smith -- https://vorpus.org
___
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