Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SubProcess Startup error #46444

Closed
madhusudansk mannequin opened this issue Feb 25, 2008 · 4 comments
Closed

SubProcess Startup error #46444

madhusudansk mannequin opened this issue Feb 25, 2008 · 4 comments
Labels
topic-IDLE type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@madhusudansk
Copy link
Mannequin

madhusudansk mannequin commented Feb 25, 2008

BPO 2191
Nosy @facundobatista
Files
  • Python3.0a IDLE startup error.htm: HTML file with error screenshot
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2008-02-25.21:30:01.677>
    created_at = <Date 2008-02-25.20:07:32.474>
    labels = ['expert-IDLE', 'type-crash']
    title = 'SubProcess Startup error'
    updated_at = <Date 2008-02-26.07:46:49.764>
    user = 'https://bugs.python.org/madhusudansk'

    bugs.python.org fields:

    activity = <Date 2008-02-26.07:46:49.764>
    actor = 'madhusudan.sk'
    assignee = 'none'
    closed = True
    closed_date = <Date 2008-02-25.21:30:01.677>
    closer = 'facundobatista'
    components = ['IDLE']
    creation = <Date 2008-02-25.20:07:32.474>
    creator = 'madhusudan.sk'
    dependencies = []
    files = ['9554']
    hgrepos = []
    issue_num = 2191
    keywords = []
    message_count = 4.0
    messages = ['62996', '63001', '63003', '63035']
    nosy_count = 2.0
    nosy_names = ['facundobatista', 'madhusudan.sk']
    pr_nums = []
    priority = 'normal'
    resolution = 'works for me'
    stage = None
    status = 'closed'
    superseder = None
    type = 'crash'
    url = 'https://bugs.python.org/issue2191'
    versions = ['Python 3.0']

    @madhusudansk
    Copy link
    Mannequin Author

    madhusudansk mannequin commented Feb 25, 2008

    After installing the Python.msi x86 installer on an Intel P4 machine
    running Windows XP SP2, I am getting the error "Subprocess startup
    error" and when i click OK on the dialog box the Python IDLE closes. I
    do not have Microsoft Visual Studio installed on my system but do have
    the .NET framework 1.1 installed. The reason code in the pop up says
    either the IDLE cannot start a subprocess or a firewall is blocking the
    connection. Is it necessary that the anitvirus/firewall software needs
    to be disabled before installing Python 3.0 or is it the case as
    mentioned in the http://www.python.org/download/releases/3.0/ "Read
    this first" section i.e. python30.dll cannot be installed in system32
    folder?

    @madhusudansk madhusudansk mannequin added topic-IDLE type-crash A hard crash of the interpreter, possibly with a core dump labels Feb 25, 2008
    @madhusudansk
    Copy link
    Mannequin Author

    madhusudansk mannequin commented Feb 25, 2008

    One more thing i am already running Python 2.5.2 and concurrently
    installed Python 3.0 a without uninstalling the 2.5.2.

    @facundobatista
    Copy link
    Member

    IDLE works in a server/client configuration with itself. Most probably
    the firewall is blocking IDLE's connections.

    Best way to try this is full disabling the firewall, and trying.

    If it works, remember to activate the firewall back, and configure it
    properly to work with IDLE.

    @madhusudansk
    Copy link
    Mannequin Author

    madhusudansk mannequin commented Feb 26, 2008

    hi,
    thanks so much for the clarification but i never faced this problem
    with 2.5.2. This is the only instance of pyhton that causes the
    mentioned error.

    On 2/26/08, Facundo Batista <report@bugs.python.org> wrote:

    Facundo Batista added the comment:

    IDLE works in a server/client configuration with itself. Most probably
    the firewall is blocking IDLE's connections.

    Best way to try this is full disabling the firewall, and trying.

    If it works, remember to activate the firewall back, and configure it
    properly to work with IDLE.

    ----------
    nosy: +facundobatista
    resolution: -> works for me
    status: open -> closed


    Tracker <report@bugs.python.org>
    <http://bugs.python.org/issue2191\>


    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    topic-IDLE type-crash A hard crash of the interpreter, possibly with a core dump
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant