Jump to content

problem---debug cura


mautotech

Recommended Posts

Posted · problem---debug cura

when I debug setup.py in Cura folder using following command in Windows Console

python -m pdb setup.py ,I got some erro,and I don't known how to solve it!

-> import sys

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(3)<module>()

-> import os

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(5)<module>()

-> if sys.platform.startswith('darwin'):

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(71)<module>()

-> import zipfile

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(72)<module>()

-> try:

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(73)<module>()

-> import cx_Freeze

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(78)<module>()

-> freezeVersion = map(int, cx_Freeze.version.split('.'))

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(79)<module>()

-> if freezeVersion[0] < 4 or freezeVersion[0] == 4 and freezeVersion[1] < 2:

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(83)<module>()

-> sys.path.append(os.path.abspath('cura_sf'))

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(86)<module>()

-> build_exe_options = {

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(87)<module>()

-> "silent": True,

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(89)<module>()

-> 'encodings.utf_8',

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(90)<module>()

-> "OpenGL", "OpenGL.arrays", "OpenGL.platform", "OpenGL.GLU",

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(92)<module>()

-> 'Tkinter', 'tcl', 'cura_sf', 'fabmetheus_utilities', 'skeinforge_application'

, 'numpy',

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(94)<module>()

-> ('images', 'images'),

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(95)<module>()

-> ], "build_exe": 'freeze_build'}

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(99)<module>()

-> base = None

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(100)<module>()

-> if sys.platform == "win32":

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(101)<module>()

-> base = "Win32GUI"

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(103)<module>()

-> cx_Freeze.setup( name = "Cura",

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(104)<module>()

-> version = "RC5",

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(105)<module>()

-> description = "Cura",

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(106)<module>()

-> options = {"build_exe": build_exe_options},

(Pdb)

> d:\codes\3dprinter\host\cura\setup.py(107)<module>()

-> executables = [cx_Freeze.Executable("cura.py", base=base)])

(Pdb)

SystemExit: SystemEx...pplied',)

> d:\codes\3dprinter\host\cura\setup.py(107)<module>()

-> executables = [cx_Freeze.Executable("cura.py", base=base)])

(Pdb)

--Return--

> d:\codes\3dprinter\host\cura\setup.py(107)<module>()->None

-> executables = [cx_Freeze.Executable("cura.py", base=base)])

why SytemExit

 

  • Link to post
    Share on other sites

    Posted · problem---debug cura

    The setup.py has been made for Linux and MacOS. It's not used for windows.

    I'm using PyCharm for Cura development, which has debug features buildin.

     

  • Link to post
    Share on other sites

    Posted · problem---debug cura

    thanks David,According to your Instruction,I execute ./package.sh win32 in the Git Shell suceefully.

    But What to do next,Because No executal Windows Application generated.

     

  • Link to post
    Share on other sites

    Posted · problem---debug cura

    That's to generate a release package, it also requires nsis installed, and will generate an installer in the base directory. Else it will only generate a zip file I think, or just a directory with the final package in it.

     

  • Link to post
    Share on other sites

    Posted · problem---debug cura

    Hi,

    I'm bumping up this thread because I'm using PyCharm and I've tried to set up a debug configuration for my virtualenv ... but it doesn't work.

    By defining pythonw as the interpreter, here's what I get in the PyCharm debugger console:

     


    /Users/me/.virtualenvs/Cura/bin/pythonw -m Cura.cura /Applications/PyCharm.app/helpers/pydev/pydevd.py --multiproc --client 127.0.0.1 --port 57621 --file /Users/me/projects/Cura/cura.py
    Traceback (most recent call last):
    File "<string>", line 1, in <module>
    AttributeError: 'module' object has no attribute 'real_prefix'
    /Users/me/.virtualenvs/Cura/bin/pythonw: line 5: /bin/python: No such file or directory
    /Users/me/.virtualenvs/Cura/bin/pythonw: line 5: exec: /bin/python: cannot execute: No such file or directory
    Process finished with exit code 126

    By defining python from the virtualenv, Cura won't start because it doesn't recognize any attached screen.

    How can I specify the right interpreter in order to debug Cura with pythonw?

    See attached Run/Debug configuration.

    I'm on OS X 10.8.5

    Schermata%202014-12-01%20alle%2021.07.20.png

     

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...