I need development and publishing workflow advice for my scripts
Rudi Hammad
I have my maya environment set to a specific root folders were I publish all my scripts,so I can import them later. Everything fine so far.
I have in another hard drive, a structure of folders were I develop a lot of scripts, and when they are OK I copy them to the publish root folders.
This development folders are not set up to the maya environment, because it would be crazy since they are a lot.
Now, here is the problem. A lot of times, during the development, I need to import scripts that are not published yet because they are in progress.
So I copy temporally the scripts in progress in the publish folder to be able to import them. And then I delete. This is not a clean work flow...
I don´t know if I´ve explained my self...anyway, any workflow advice?
thanks
Justin Israel
If this is a Linux/osx environment, you could use something like virtualenv to switch between production and dev environments and then launch Maya from that shell env
Are these python scripts that you need to import? You can also dynamically adjust your sys.path from within a running Maya to add extra package locations. And then if you are on linux/osx you can symlink your development locations to where you need them.
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_m...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/d60956be-fa65-4c96-9b25-04a51447cc2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Rudi Hammad
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/
yes they are python files. I am using eclipse. I remember that you told me once that you used it at the beginning, and the you switched to another. So far I am very happy with eclipse, so I am staying with it.
anyway...I´ll check virtualenv too because I am not sure what it is, and symlinks. is symlinks a good solution?
El sábado, 19 de diciembre de 2015, 1:36:25 (UTC+1), Justin Israel escribió:
If this is a Linux/osx environment, you could use something like virtualenv to switch between production and dev environments and then launch Maya from that shell env
Are these python scripts that you need to import? You can also dynamically adjust your sys.path from within a running Maya to add extra package locations. And then if you are on linux/osx you can symlink your development locations to where you need them.
On Sat, 19 Dec 2015 1:05 PM Rudi Hammad <rudih...@gmail.com> wrote:
Hello,--
I have my maya environment set to a specific root folders were I publish all my scripts,so I can import them later. Everything fine so far.
I have in another hard drive, a structure of folders were I develop a lot of scripts, and when they are OK I copy them to the publish root folders.
This development folders are not set up to the maya environment, because it would be crazy since they are a lot.
Now, here is the problem. A lot of times, during the development, I need to import scripts that are not published yet because they are in progress.
So I copy temporally the scripts in progress in the publish folder to be able to import them. And then I delete. This is not a clean work flow...
I don´t know if I´ve explained my self...anyway, any workflow advice?
thanks
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
Justin Israel
I'm not saying you should change your IDE or anything. I was only talking about your shell environment. But you are on Windows so that is a different story. You can use some form of env management like virtualenv Maya. but it still means you have to launch Maya from a shell or some environment managed launcher. Or you can write a tool that can adjust the sys.path within Maya
I am on windows 8. You mean this right?
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/
yes they are python files. I am using eclipse. I remember that you told me once that you used it at the beginning, and the you switched to another. So far I am very happy with eclipse, so I am staying with it.
anyway...I´ll check virtualenv too because I am not sure what it is, and symlinks. is symlinks a good solution?
El sábado, 19 de diciembre de 2015, 1:36:25 (UTC+1), Justin Israel escribió:If this is a Linux/osx environment, you could use something like virtualenv to switch between production and dev environments and then launch Maya from that shell env
Are these python scripts that you need to import? You can also dynamically adjust your sys.path from within a running Maya to add extra package locations. And then if you are on linux/osx you can symlink your development locations to where you need them.
On Sat, 19 Dec 2015 1:05 PM Rudi Hammad <rudih...@gmail.com> wrote:
Hello,--
I have my maya environment set to a specific root folders were I publish all my scripts,so I can import them later. Everything fine so far.
I have in another hard drive, a structure of folders were I develop a lot of scripts, and when they are OK I copy them to the publish root folders.
This development folders are not set up to the maya environment, because it would be crazy since they are a lot.
Now, here is the problem. A lot of times, during the development, I need to import scripts that are not published yet because they are in progress.
So I copy temporally the scripts in progress in the publish folder to be able to import them. And then I delete. This is not a clean work flow...
I don´t know if I´ve explained my self...anyway, any workflow advice?
thanks
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_m...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/d60956be-fa65-4c96-9b25-04a51447cc2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_m...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/31bcf9db-53e7-42cb-949f-ef4338a91861%40googlegroups.com.
yury nedelin
Just curious, why not just have all of your Maya scripts in the location that Maya can see? If you are working with python and you really like separation between temp work and production ready work namespaces will help. Having multiple environments for launching Maya as Justin suggested is a really good workflow but you could also just add all of your script locations to your local Maya env and just not worry about it.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2F-9nqtfCfQoSbvVzy9AYRO-Q8L6uS5Udpdm31LiFwuQ%40mail.gmail.com.
Marcus Ottosson
The most successful way I’ve seen this work, is by running software after you’ve set up an environment for it.
For example, here’s how you could launch Eclipse in “development mode” and “production mode” respectively.
$ set PYTHONPATH=c:\path\to\development\files
$ c:\program files\eclipse\eclipse.exe
Now when you import anything within Eclipse, it would look towards your development directory. To launch in “production mode”, you could do something similar.
$ set PYTHONPATH=c:\path\to\production\files
$ c:\program files\eclipse\eclipse.exe
And the same goes for any program; Sublime Text, Maya, Notepad and so forth. And it works the same on any platform, apart from the command to set variables (“export” versus “set”) and the actual executable file.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CACqGScgXE49kvrOi1QkacoSJJLqCa-QU9ACfhE_wP6WWgpydiA%40mail.gmail.com.
Rudi Hammad
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/d60956be-fa65-4c96-9b25-04a51447cc2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/31bcf9db-53e7-42cb-949f-ef4338a91861%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2F-9nqtfCfQoSbvVzy9AYRO-Q8L6uS5Udpdm31LiFwuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CACqGScgXE49kvrOi1QkacoSJJLqCa-QU9ACfhE_wP6WWgpydiA%40mail.gmail.com.