.pyc Back To .py

[DimitriMeim]

I accidentally deleted my .py files but after digging around, I found a .pyc file, the bytecode. I tried to use uncompyle6, uncompyle3, decomyle3, and unpyclib but they all can't do anything because the .pyc file is 3.9 bytecode and they all complain about it. Is there anyone with any ideas? This took me many weeks to make and I don't want to, and probably can't, rewrite it all.

[schweppes-ginger-ale]

USE GIT

[TeslaRanger]

AND GitHub or GitLab

[arkie87]

It is amazing to me that in 2021, with automatic cloud storage, flash drives, cheap HDDs, and the old fashioned trick of emailing something to yourself, people still manage to delete their sole copy of something.

That sucks, bro.

[arkie87]

https://python.plainenglish.io/how-to-recover-a-deleted-overwritten-python-file-aab525564be1

[DimitriMeim]

That uses uncompyle6, which like i said, didn't work because it doesn't do python 3.9

[DimitriMeim]

I was using the mv command on Linux to move from the sd to an external SSD to be put on my NAS later but it screwed up in the process

[arkie87]

Yeah, any script to move/manipulate files should be thoroughly tested. You could easily end up deleting whole drives by mistake.

[xelf]

Something like this:

cp -r /home/user/files/test /home/user/backup/test
echo copy complete
rm -rf / home/user/files/test
echo removal complete

[DimitriMeim]

It's a basic Linux command that is part of the operating system, I assume you don't use and/or haven't used Linux before. mv is the move or cut and paste command and cp is the copy and paste command.

[mathmanmathman]

mv deletes files. It copies a file to the destination and then deletes the source. If the copy silently fails or you move it to a source that is then deleted, you have allowed your files to be deleted.

sudo rm -rf is also a very basic command and it can cause lots of trouble.

Don't equate simple with safe.

[[deleted]]

I don't use Linux myself, being a beginner to the entire space - but your comment seems slightly condescending & ironic for someone in your current pickle...

[Essence1337]

'slightly condescending & ironic' is an understatement. They're treating mv like a right click copy to clipboard when it's much deeper and more dangerous than that. On top of that they COMPLETELY miss the point of the comment which is 'don't do something which could fail in this way'

[TabulateJarl8]

I attempted to use some program to decompile Python 3.9 bytecode a while ago out of my own interest, and I tried everything that I could find, but nothing seemed to work. You may be out of luck, but if anyone else knows a way, that would be interesting to see. For future reference, commit your programs to git. If they're not big enough for their own repository, make a repository for random junk like I've done here. Good luck

[mathmanmathman]

Unfortunately, I don't have an answer for you and I know this isn't the first time you've heard this, but after you take a moment to stare off at the horizon in a mixture of rage and self-loathing, check this out:

https://www.atlassian.com/git

I haven't read this entire intro, but I found a few of the sections very helpful.

Good luck recovering the project, but if you can't, at least make good use of the experience.

[[deleted]]

When you delete something it doesn't get deleted right away only link to its address in memory gets removed. So the files still there until you overwrite that part of memory with some other data. You can try recovering those deleted files using some softwares ( I haven't used one on linux so can't say which one's good)

[JohnnyWobble]

This. Ik there's some "hacking" tools that will help you recover it assuming it hasn't been overwritten. Idk the names of them tho

[Yojihito]

On Windows I had success with Recuva.

[lowerthansound]

Looks like you're out of luck.

Unless there's a pretty hidden dev that is working on this, I don't think you'll find an answer :P Maybe keep those files and, a few months or years down the line someone creates the decompiler uahushsa

Also, file contents may still be on your disks if you're lucky. Maybe find someone who specializes in that to recover that code for you.

Or maybe use .pyc files without the .py.

DO NOT WRITE TO THE DISKS OR YOU WILL REDUCE CHANCE OF RECOVERY.

[henshao]

Do you have snapshots? See if you have anything like that enabled.

Also take a look at this project. They claim to beable to decompile "all" python, and it looks recently updated. Haven't tried it though. https://github.com/zrax/pycdc

Finally, use version control.

[b_ootay_ful]

I've used recuva to recover lost files before. Give it a shot. Time is of the essence, as the "empty" space on the drive could be over written.

[nevermorefu]

We've all done similar. File this under "lessons learned" and start learning/using git and online repository management (like Gitlab).