slpkg & tar2xzm > txz2xzm
- ncmprhnsbl
- DEV Team
- Posts: 3925
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
slpkg & tar2xzm > txz2xzm
yeah, had i looked little harder, i would have noticed that *.pyc and *.pyo s are stripped
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
- Ed_P
- Contributor
- Posts: 8343
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
slpkg & tar2xzm > txz2xzm
"stripped"?? They do look "strange" in Text Editor, hex and text show, but all 3 are 90kb.
Ed
- ncmprhnsbl
- DEV Team
- Posts: 3925
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
slpkg & tar2xzm > txz2xzm
as in removed in the porteus build process.
if you compare the slackware python2 package with what's in porteus, you'll see lots of unecessary stuff removed..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
- Ed_P
- Contributor
- Posts: 8343
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
slpkg & tar2xzm > txz2xzm
Yes, and so too the pydoc.py file and it is obviously needed. What about the hex stuff in the other two pydoc files? Are they corrupt or does it serve a purpose?
Ed
-
- Full of knowledge
- Posts: 2065
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
slpkg & tar2xzm > txz2xzm
Some quotes from the i-net
(personally, I know next to nothing about python)
.py - Regular script
.pyc - compiled script (Bytecode)
.pyo - optimized pyc file (As of Python3.5, Python will only use pyc rather than pyo and pyc)
.py: This is normally the input source code that you've written.
.pyc: This is the compiled bytecode. If you import a module, python will build a *.pyc file
that contains the bytecode to make importing it again later easier (and faster).
.pyo: This is a *.pyc file that was created while optimizations (-O) was on.
A program doesn't run any faster when it is read from a ‘.pyc’ or ‘.pyo’ file than when it is read
from a ‘.py’ file; the only thing that's faster about ‘.pyc’ or ‘.pyo’ files
is the speed with which they are loaded.
- Ed_P
- Contributor
- Posts: 8343
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
slpkg & tar2xzm > txz2xzm
Thank you donald.
I can relate. I didn't know python was a script language like bash until 2 months ago.
"use pyc rather than pyo and pyc"!!? Interesting.
The 3 files are all ~90kb so I don't see how one will load faster than the others. Anyways, interesting quotes donald.
Ed
slpkg & tar2xzm > txz2xzm
I have 32bit Mate Porteus, in /usr/lib/python2.7 there is only pydoc_data. Do I need to reinstall python from source?
-
- Full of knowledge
- Posts: 2065
- Joined: 17 Jun 2013, 13:17
- Distribution: Porteus 3.2.2 XFCE 32bit
- Location: Germany
slpkg & tar2xzm > txz2xzm
@afrodeity
You need to clean your changes folder or savedat container.
Because it is not the only "missing files" issue you have,
it seems you screwed up your installation.
As always in such a case:
Boot into Always Fresh mode and check the content of /usr/lib/python2.7
The files/Folders are there.
So what happend? -- someone/somewhat has created whiteout files which
make the files invisible to the system/you.
The files are still there as long as you didn't alter the base modules.
[they are read only by default]
You need to clean your changes folder or savedat container.
Because it is not the only "missing files" issue you have,
it seems you screwed up your installation.
As always in such a case:
Boot into Always Fresh mode and check the content of /usr/lib/python2.7
The files/Folders are there.
So what happend? -- someone/somewhat has created whiteout files which
make the files invisible to the system/you.
The files are still there as long as you didn't alter the base modules.
[they are read only by default]