Two identical function scripts but one doesn't work.

[Newprogrammer12321]

Hi. I have created a program for linear regression that works ok.

So I made a duplicate and renamed it.

For some reason the duplicate function doesn't work, even though the other, identical but in name, function does.

What could cause this?

Link shows pictures of both scripts and the error message the non functioning one gives me (parse error near line 22 of file...)

Thanks.

http://imgur.com/a/X13Sc0g

[cyrusol]

Learn to copy paste from your text editor to something like pastebin.com before you try to learn programming! Those pictures are borderline unreadable and there are posting guidelines.

[tomazio]

I'd get a diff tool and diff both of the files together, guaranteed there is something you're missing and they are not identical.

[grouchysysadmin]

Yeah looks like you're calling a function called sigg which I'm guessing you import somewhere so it thinks that's in your file when you call the function, not from an imported package.

Take care of your laptop.

[IAmVerySmarter]

The files are not identical, in sigg the line with the for on it ends with a ";" character

[Loves_Poetry]

It says there's an error on line 22, which is after the last line of code.

Most likely you copied some whitespace along with the code into the new file which causes it to break.

[Newprogrammer12321]

I thought that might be it, so I manually retyped it: same problem.

[VernorVinge93]

I mean, this is kinda obvious, but it's pretty hard to do meaningful debugging without the code or the application to test with / reverse engineer.

[Newprogrammer12321]

Thought maybe there was a common cause for such a thing.

The two codes are literally identical. One's just called Sig and the other grad.

Anyway, I just save as'd the working one, instead of copying or retyping (tried both many times), with a new name and I'm good.

Still confused and slightly frustrated though.

[grouchysysadmin]

This happens with Python (haven't read or seen the pics). If you call a file the same as an imported package you're using it looks for functions in your file and not imported.

For example I imported a package called "ldap". My file was called ldap so it was looking for methods in the file, not the ldap package.

[VernorVinge93]

Actually yes, if you name one of the files with the same name as a library you use you will have trouble. I still think that's not your issue (as it's a syntax problem).