Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

peps.python.org

Post reply on HN
Print view View original

11–20 of 30 posts

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#11

Post by SushiHippie »

Verath wrote: post #4
SushiHippie wrote: post #2

Is there a reason, why the __pyproject__ variable is not a dict but a toml string?

I think they do kind of answer that under the "Why not use (possibly restricted) Python syntax?". I understand their reasoning to be that it would require other tools to know how to parse python. Which is much more difficult than parsing toml

Ah okay, I read this but I've understood it in another way. I thought they meant using multiple variables could become a problem. But I guess it makes some sense to not parse the python ast tree but to parse with a regex.

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#12

Post by SushiHippie »

frfl wrote: post #3
SushiHippie wrote: post #2

Is there a reason, why the __pyproject__ variable is not a dict but a toml string?

Maybe because then you can just inline a pyproject text without any extra effort and the existing tooling for pyproject parsing can work in both cases?

Yeah copying a pyproject.toml seems like a valid case. But I'd guess that the toml will be parsed to something like a dict anyway after reading the file/string.

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#13

Post by adamckay »

This will be useful, and definitely handy when sharing random scripts with a defined structure for its requirements. I've struggled to give scripts to non-developers to run recently and between getting them to configure a virtualenv and install dependencies by hand to using `pipx` it's been a pain so hopefully this will alleviate some if it in the future.

Not sure, however, that I buy the argument that it's going to be simpler for non-programmers to use TOML embedded inside a multiline string versus using something along the lines of requirements.txt - there's going to be absolutely zero syntax highlighting so things like missing quotes or bracket's will need to be carefully identified.

There's also going to be inevitable differences between `__pyproject__` and `pyproject.toml` which could lead to more confusion, such as the `readme` key - that's likely to be useful to include some help information alongside your script so it's self documenting, but in `pyproject.toml` it must refer to another file and in `__pyproject__` I'd assume it can itself be a multiline string..?

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#14

Post by SushiHippie »

lijok wrote: post #8
SushiHippie wrote: post #2

Is there a reason, why the __pyproject__ variable is not a dict but a toml string?

It's probably because pyproject.toml is the direction in which the python ecosystem is going. On that note, I will never understand why they chose .toml instead of just json or yaml..

Yes, but you can write a pyproject toml file also as a python dictionary.

Instead of:

[project] requires-python = ">=3.11" dependencies = [ "requestsYou could write:

{ "project": { "requires-python":">=3.11", "dependencies" : [ "requests<3", "rich" ] }

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#15

Post by lijok »

SushiHippie wrote: post #14
lijok wrote: post #8

Earlier quoted context omitted.

It's probably because pyproject.toml is the direction in which the python ecosystem is going. On that note, I will never understand why they chose .toml instead of just json or yaml..

Yes, but you can write a pyproject toml file also as a python dictionary. Instead of: [project] requires-python = ">=3.11" dependencies = [ "requests You could write: { "project": { "requires-python":">=3.11", "dependencies" : [ "requests<3", "rich" ] }

No way !

Gotta think carefully about this... Might upset some coworkers

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#16

Post by SushiHippie »

Denvercoder9 wrote: post #10
lijok wrote: post #8

Earlier quoted context omitted.

It's probably because pyproject.toml is the direction in which the python ecosystem is going. On that note, I will never understand why they chose .toml instead of just json or yaml..

> On that note, I will never understand why they chose .toml instead of just json or yaml.. https://peps.python.org/pep-0518/#other-file-formats

Thanks this also gave another reason why they didn't use a dict for configuration https://peps.python.org/pep-0518/#python-literals

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#17

Post by aldanor »

lijok wrote: post #8
SushiHippie wrote: post #2

Is there a reason, why the __pyproject__ variable is not a dict but a toml string?

It's probably because pyproject.toml is the direction in which the python ecosystem is going. On that note, I will never understand why they chose .toml instead of just json or yaml..

YAML is one of the most ambiguous formats out there, and definitely an overkill for what's needed to describe metadata.

JSON - not the most convenient to use for human beings, too much quoting, not too git friendly because of disallowed trailing commas, etc.

TOML sits somewhere inbetween, easy to write but the spec is very short; also being used in Rust and a few other places.

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#18

Post by lijok »

Denvercoder9 wrote: post #10
lijok wrote: post #8

Earlier quoted context omitted.

It's probably because pyproject.toml is the direction in which the python ecosystem is going. On that note, I will never understand why they chose .toml instead of just json or yaml..

> On that note, I will never understand why they chose .toml instead of just json or yaml.. https://peps.python.org/pep-0518/#other-file-formats

I think "easy for humans to edit" is where I mostly disagree with. To this day I have not worked with anyone that understood the .toml format.

Re: PEP 723 – Embedding pyproject.toml in single-file scripts – peps.python.org

#20

Post by heinrich5991 »

lijok wrote: post #18
Denvercoder9 wrote: post #10

Earlier quoted context omitted.

> On that note, I will never understand why they chose .toml instead of just json or yaml.. https://peps.python.org/pep-0518/#other-file-formats

I think "easy for humans to edit" is where I mostly disagree with. To this day I have not worked with anyone that understood the .toml format.

Hey. I think I understand the .toml format. What do you want to know?
Post reply on HN