Untitled conversation
- User
def zapiszSpisStron(data): try: with open(SPIS_STRON, 'w') as f: json.dump(data, f, indent=4) rozmiar = os.stat(SPIS_STRON).st_size print(f'Uaktualniono plik spisu stron. Rozmiar {rozmiar}') except Exception as e: print(f'Nie można zapisać pliku spisu stron {SPIS_STRON}') print(e)Can I read the new filesize easier if I have the file already opened?
Assistant
Great question!
You're currently opening the file with
with open(...) as f:and then usingjson.dump(data, f)to write data. After that, you're callingos.stat(SPIS_STRON).st_sizeto get the file size.✅ Your Question:
Can I read the new file size easier if I have the file already opened?
🧠 Short Answer:
Yes, you can get the file size more efficiently while the file is still open, by using the file object (
f) directly — but only after writing the data.
✅ Better Way (Get size without reopening or using
os.stat()):After writing with
json.dump(), you can use:f.tell()This tells you how many bytes have been written to the file so far — effectively giving you the file size in bytes at that moment.
However, there's a caveat: the exact final file size may not be known until the file is closed, because of buffering. But for practical purposes like logging,
f.tell()works well after you finish writing and before closing the file.Here's how to update your function:
✅ Improved Version of Your Function
def zapiszSpisStron(data): try: with open(SPIS_STRON, 'w') as f: json.dump(data, f, indent=4) f.flush() # Make sure all data is written to the buffer rozmiar = f.tell() # Get current position = size in bytes print(f'Uaktualniono plik spisu stron. Rozmiar: {rozmiar} bajtów') except Exception as e: print(f'Nie można zapisać pliku spisu stron {SPIS_STRON}') print(e)
🔍 Notes:
f.tell()gives the current position of the file pointer. Since you've just written to the end, this equals the file size in bytes.- We call
f.flush()beforef.tell()to ensure that all buffered data has been written internally (though in'w'mode it's usually not an issue). - The file is still inside the
withblock, so it will be properly closed afterward.
⚠️ Limitations:
- This method gives the file size in bytes only.
- It doesn't account for potential filesystem behavior (like compression, sparse files), but for logging/debugging purposes, it's perfectly fine.
✅ Summary:
Yes, you can get the file size more efficiently while the file is still open by using
f.tell()right after writing and before closing.Let me know if you want to also log human-readable sizes like "1.2 KB" or "345 Bytes"!
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.