Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: Federico Pellegrin <fede@evolware.org>,
	Marcus Hoffmann <marcus.hoffmann@othermo.de>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [External] - Re: Python pyc only and problem with scripts
Date: Tue, 9 Aug 2022 18:35:50 +0200	[thread overview]
Message-ID: <20220809163550.GF3168@scaer> (raw)
In-Reply-To: <PH1P110MB1603D8E2804E4F31B878B6039F629@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM>

Vincent, All,

On 2022-08-09 12:54 +0000, Vincent Fazio spake thusly:
[--SNIP--]
> That said,  if you read PEP 3147, it's pretty clear that sourceless distributions are "legacy",
> so anything we do is likely outside of the scope of what upstream intends to support. It may still be
> worth having a discussion about long term support options

Ref;
    https://peps.pythondiscord.com/pep-3147/#case-4-legacy-pyc-files-and-source-less-imports

    ---8<---
    Case 4: legacy pyc files and source-less imports

    Python will ignore all legacy pyc files when a source file exists
    next to it. In other words, if a foo.pyc file exists next to the
    foo.py file, the pyc file will be ignored in all cases

    In order to continue to support source-less distributions though,
    if the source file is missing, Python will import a lone pyc file
    if it lives where the source file would have been.
    ---8<---

Vincent, Thomas, and I have had a quick discussion on IRC, which boils
down to reading the PEP3147 in two (or three) ways:

  - Vincent: legacy (pyc files and source-less imports)
    => both pyc files on their own *and* source-less distributions
       are considered legacy

  - Yann: (legacy pyc files) and (source-less imports)
    => only pyc files on thier own are legacy; source-less distribution
       is still supported

  - Thomas: in-between
    => "Because we can't break the world overnight, we continue to
       support this, but it sucks"

So, Vincent has opened an issue to ask for clarification:
    https://github.com/python/cpython/issues/95827

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-09 16:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  7:40 [Buildroot] Python pyc only and problem with scripts Federico Pellegrin
2022-08-08 10:05 ` Marcus Hoffmann
2022-08-08 10:17   ` Thomas Petazzoni via buildroot
2022-08-08 10:30     ` Marcus Hoffmann
2022-08-08 10:47       ` Thomas Petazzoni via buildroot
2022-08-08 17:55         ` Marcus Hoffmann
2022-08-26  9:09       ` Marcus Hoffmann
2022-08-08 10:20 ` Thomas Petazzoni via buildroot
2022-08-08 13:19   ` Federico Pellegrin
2022-08-08 20:48     ` Arnout Vandecappelle
2022-08-09  4:49       ` Federico Pellegrin
2022-08-09 12:54         ` [Buildroot] [External] - " Vincent Fazio
2022-08-09 16:35           ` Yann E. MORIN [this message]
2022-08-26 16:31       ` [Buildroot] " James Hilliard
2022-08-26 16:22 ` James Hilliard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220809163550.GF3168@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=fede@evolware.org \
    --cc=marcus.hoffmann@othermo.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vfazio@xes-inc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox