Is there a way to be in one *.py file with its corresponding *.pyui file that creates the GUI.
Then you click a button and go to another *.py with its corresponding *.pyui file?

Even works with the new Scene module.
Thanks so much.

So, yes, I have StaSh and I am using it.

I want to use Working Copy, because I would like to use it with my grade 10 programming class.
They are almost all brand new to programming and just the concept of using GitHub is confusing enough for them, adding in the complexity of command line usually sends them over the deep end.
I like the GUI of Working Copy.

My ultimate workflow would be for them to create a directory in Pythonista, then the *.py and *.pyui files inside the directory. Then send the directory as a repo to Working Copy and then off to GitHub.

Thanks, Patrick

Great, thanks.

Here is a link to a version I have, saved in Google Drive:
https://drive.google.com/open?id=0BxJplyUFPhf-Z3BUbDJlMUJPdjQ

+1 for me to.

@omz Thanks for getting back to me.

I was wondering if there is any explanation on why it is no longer possible?
I used Pythonista last year with my grade 11 programming course and got over a dozen apps published on the App Store. I have just started using it again with this years group and told them we will be doing the same thing. If there is anything I can do to help the process along, please let me know. We will not be starting to write the final apps until December.

Thanks

In January I was successful at getting several apps onto the App Store.
I just went back to load another one and I am now getting a Code Signing Error.
I cleared out all my certificates and reloaded everything to ensure something had not expired.
I even loaded an app built completely in Xcode and it worked fine.
When I try using the Pythonista template I get:

ERROR ITMS-90035: "Invalid Signature. Code object is not signed at all. The file at path [My App.app/Frameworks/PythonistaKit.framework/pylib/future.py] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"
ERROR ITMS-90035: "Invalid Signature. Code object is not signed at all. The file at path [My App.app/Frameworks/PythonistaKit.framework/pylib/future.py] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

Anybody else getting this?
Anyone have a solution?

That works and I get the new view.
Problem is it looks like Pythonista is trying to load the buttons that are defined in the second *.pyui file, but the first *.py file does not have any reference to them. The are in the second *.py file.

Warning: Could not bind action: name 'calculate_button_touch_up_inside' is not defined
Warning: Could not bind action: name 'clear_button_touch_up_inside' is not defined

Is there a way to be in one *.py file with its corresponding *.pyui file that creates the GUI.
Then you click a button and go to another *.py with its corresponding *.pyui file?

Wondering if anyone has been able to submit an app successfully since Jan 1, 2017.
I still am getting signing errors and have no workaround that will work.
I have app waiting to get approved and need a solution.

Thanks

@omz I tried as you suggest and used the Application Loader. Same problem happening. Still getting code signing errors. Have tried using "Auto code signing" and even old school downloading the certificate myself and still getting the same messages.
Have you been able to get anything uploaded to the App Store?
Do you have a template that I could try?

Thanks

@omz I have used your script and changed all the files in pylib and pylib_ext. I even placed the header at the top of the files in "scripts". It still compiles OK to simulator and devices but I am still getting a code signing error.

error screenshot

Any ideas?
Here is my fork with the fix: https://github.com/Mr-Coxall/PythonistaAppTemplate

@omz Thanks so much for getting back to me.
I will give it a try and see what happens.

By any chance do you have an update to the GitHub repo with the changes already made to the pylib and pylib_ext, so that I do not have to run the scrip and change anything?

Thanks again, Patrick

I am trying to upload a Pythonista project to the Apple App Store.
I have tried many, many time and keep getting code signing errors.
I am using Xcode 8.2.1
So this is what I have done:

Started with new Xcode Swift single view project, archived it and was able to submit it to the App Store. So my certificates are all working. I downloaded the Xcode template and then archived it. When I submit to Apple, it hangs on the code signing for a really long time and then comes back with this error:

ERROR ITMS-90035: "Invalid Signature. Code object is not signed at all. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html"

The only thing I can figure out is that it seems to be trying to code sign the PythonistaKit.framework and does not seem to be able to. I can see "PythonistaKit.framework (0 Entitlements), just before I validate it.

Wondering if anyone else is able to reproduce this error, or even better have a fix to the problem.
Thanks

Got it working:
[https://github.com/Mr-Coxall/Git2Go-to-Pythonista](link url)