Difference between revisions of "User talk:Foxboron/Python packaging guidelines"

From ArchWiki
Jump to: navigation, search
(Whether to target two python versions: re)
(Whether to target two python versions: re)
 
Line 6: Line 6:
  
 
: Felix pointed out that he was seeing the .pyc be installed due to testsuite usage, but that that doesn't seem to be an issue today so I'm unsure what might have caused it. At least, {{ic|python setup.py}} test via unittests, and pytest, both pick up the copy from the setup.py root, not the {{ic|build/}} directory, alongside the actual tests to run. Does anyone know of a case where that is actually an issue? At this stage I'm mostly just believing Felix that it was ever an issue, since I certainly cannot confirm. -- [[User:Eschwartz|Eschwartz]] ([[User talk:Eschwartz|talk]]) 18:23, 29 June 2018 (UTC)
 
: Felix pointed out that he was seeing the .pyc be installed due to testsuite usage, but that that doesn't seem to be an issue today so I'm unsure what might have caused it. At least, {{ic|python setup.py}} test via unittests, and pytest, both pick up the copy from the setup.py root, not the {{ic|build/}} directory, alongside the actual tests to run. Does anyone know of a case where that is actually an issue? At this stage I'm mostly just believing Felix that it was ever an issue, since I certainly cannot confirm. -- [[User:Eschwartz|Eschwartz]] ([[User talk:Eschwartz|talk]]) 18:23, 29 June 2018 (UTC)
 +
 +
: As discussed on IRC, we're going to convert this into a note on 2to3 use. No other issues have been suggested and can be verified to currently exist, so I guess this seems reasonable. -- [[User:Eschwartz|Eschwartz]] ([[User talk:Eschwartz|talk]]) 18:42, 13 July 2018 (UTC)

Latest revision as of 18:42, 13 July 2018

Whether to target two python versions

I don't think this makes much sense to recommend in the common case. It's only really useful in exceptional cases like when the setup.py itself specifies to run 2to3 for automated supporting of both python2 and python3. Worth noting that this isn't really recommended, and most projects do the sane thing and write polyglot code that runs everywhere instead...

Maybe make a special note that "if 2to3 is used, then you'll need to copy [...]".-- Eschwartz (talk) 21:10, 28 June 2018 (UTC)

Felix pointed out that he was seeing the .pyc be installed due to testsuite usage, but that that doesn't seem to be an issue today so I'm unsure what might have caused it. At least, python setup.py test via unittests, and pytest, both pick up the copy from the setup.py root, not the build/ directory, alongside the actual tests to run. Does anyone know of a case where that is actually an issue? At this stage I'm mostly just believing Felix that it was ever an issue, since I certainly cannot confirm. -- Eschwartz (talk) 18:23, 29 June 2018 (UTC)
As discussed on IRC, we're going to convert this into a note on 2to3 use. No other issues have been suggested and can be verified to currently exist, so I guess this seems reasonable. -- Eschwartz (talk) 18:42, 13 July 2018 (UTC)