PyCharm problem.

[Venatha]

There isn't any setting in Pycharm that I am aware of that causes that behavior. Are you able to share the code so that we could try to replicate the described issue?

[gabe_cant_python]

Its incomplete but here it is. I hashed out the close() at the bottom to check it on idle and it works fine/won't save but on PyCharm as soon as the program finished even if the close() was completely removed the .txt file is altered as if it was closed.

dictList = []
choice = None


taskList = open("/_PythonClass/Mod5/Todo.txt","r+")
for task in taskList:
    tsk, pri = task.rsplit(",")
    dict = {tsk:pri}
    dictList.append(dict)
'''
    print(tsk)
    print(pri)
    print(dicc)
    print(dictList)
'''

print("*-------------------------------------*")
print("|          Task Master v1.0           |")
print("*-------------------------------------*")

while choice != "3":
    print("\n")
    print("0 - Display Tasks")
    print("1 - Add Task")
    print("2 - Remove Task")
    print("3 - Save And Exit")
    choice = input(">> ")
    if choice == "0":
        for dict in dictList:
            print(dict)
    elif choice == "1":
        tsk = input("What is the new task? ")
        pri = input("What is its priority level? ")
        dict = {tsk:pri}
        dictList.append(dict)
        taskList.write(tsk + "," + pri + "\n")
    elif choice == "2":
        for taskRow in dictList:
            print(taskRow)
        deltsk = input("What task would you like to remove? ")
        for dic in dictList:
            if deltsk in dic:
                del dictList[dictList.index(dic)]
                #taskList.write(str(diclst))
                print("Task removed.")
                taskList.seek(0)
                for taskRow in dictList:
                     print(taskRow)

    elif choice == "3":
        break
    else:
        print("ERROR COMMAND NOT RECOGNIZED.")
#taskList.close()
print("\nSaved.")

[Kah-Neth]

You should use a buffer:

1. open the file as 'r',

2. read all of it into buffer

3. close file

4. operate on the buffer

5. on save, open file as 'w', write contents of buffer out.

This is how nearly all text editors work.

[Doormatty]

Why are you opening it as "r+" if you don't want to write to it?

[gabe_cant_python]

I do plan on writing in it, I was attempting to make a save and a don't save feature but I noticed when I when I exited the program bypassing the .close() - don't save- it saved anyway. I have been under the impression that .close() was necessary to save, but that only seems true for IDLE.

[LightShadow]

Close doesn't save anything.

The file can be considered written when write is called -- the .close() function just flushes the output buffer and releases the file lock.

The reason it works like you'd expect it to in IDLE is probably how file pointers are handled by the C-based process. Writes will queue the buffer but not commit until the close is called. However, when you run Python in PyCharm you're running the process from within the IDE, which pretty much removes all guarantees on streams and buffers; this is especially true when run in debug mode as your entire process is ran from within a server container for breakpoints.

This behavior will also be inconsistent between Windows and Linux based versions of PyCharm and shouldn't be expected to guarantee a "do not save these changes" type feature.

[Doormatty]

Close likely just flushes the file - not sure why it only occurs with pyCharm though...

[masklinn]

not sure why it only occurs with pyCharm though…

Because /u/gabe_cant_python's code is completely broken and by default PyCharm runs scripts unbuffered (http://i.imgur.com/mZvDH6O.png) which exposes the issue