On Wed, Aug 8, 2018 at 5:09 AM Paul Moore wrote:
> This strikes me as *absolutely* something that should be promoted
> outside of the stdlib, as a 3rd party project, and once it's
> established as a commonly used and accepted standard, only then
> propose that the stdlib offer support for it (if
> On 8 Aug 2018, at 12:08, Victor Porton wrote:
>
>> On 08/08/18 12:25, Barry Scott wrote:
>>> On Tuesday, 7 August 2018 22:57:51 BST Victor Porton wrote:
>>> This is an idea of a new PEP.
>>>
>>> I propose to create a portable file format which will list command line
>>> options to run Pytho
On 07/08/18 22:57, Victor Porton wrote:
This is an idea of a new PEP.
I propose to create a portable file format which will list command line
options to run Python scripts with dual purpose:
You are going about this the wrong way. If you want IDE-makers to use
your putative file format, you
Hi Victor
Thank you for your contribution, regarding standards for Python tools.
Here is my two cents worth.
You wrote:
> We need a standard to make PyCharm and others to conform to it.
Things don't quite work that way, in the Python community. True, we
have a Benevolent Dictator For Life (BDFL)
On 08/08/18 12:25, Barry Scott wrote:
On Tuesday, 7 August 2018 22:57:51 BST Victor Porton wrote:
This is an idea of a new PEP.
I propose to create a portable file format which will list command line
options to run Python scripts with dual purpose:
At the moment I solve this problem with vario
On Tuesday, 7 August 2018 22:57:51 BST Victor Porton wrote:
> This is an idea of a new PEP.
>
> I propose to create a portable file format which will list command line
> options to run Python scripts with dual purpose:
At the moment I solve this problem with various solutions, depending on
requi
On Wed, 8 Aug 2018 at 00:35, Victor Porton wrote:
>
> > But I see no reason why this has anything to do with the Python standard
> > library. Can you explain why you want to distribute an experimental
> > file format in the Python std lib?
>
> As I pointed out, I want this format to become common
a suggest : don't make it obligatory
i think it might come as suggested settings as settings on different
environments different.
or we can specify only in modules like in setup.py the name of the file,
then each user configures it's own (considering pip we can make use it
false by default)
in t
On 08/08/18 02:18, Steven D'Aprano wrote:
On Wed, Aug 08, 2018 at 12:57:51AM +0300, Victor Porton wrote:
This is an idea of a new PEP.
I propose to create a portable file format which will list command line
options to run Python scripts with dual purpose:
Feel free to create whatever file form
On Wed, Aug 08, 2018 at 12:57:51AM +0300, Victor Porton wrote:
> This is an idea of a new PEP.
>
> I propose to create a portable file format which will list command line
> options to run Python scripts with dual purpose:
Feel free to create whatever file format you like. There are tens of
thou
This is an idea of a new PEP.
I propose to create a portable file format which will list command line
options to run Python scripts with dual purpose:
1. for automatic tests executing scripts from this file (and optionally
checking their stdout against specified values).
2. for running the
11 matches
Mail list logo
