fix: specify utf-8 encoding when writing toml files #6449
                
     Merged
            
            
          
      
        
          +1
        
        
          −1
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
📝 Summary
Fixes #6434.
Fixes a
UnicodeEncodeErroron Windows by specifying UTF-8 encoding when writing TOML files.🔍 Description of Changes
This pull request addresses an issue where saving a marimo notebook on Windows with a file path containing non-ASCII characters would result in a
UnicodeEncodeError.The error was caused by the
write_tomlfunction inmarimo/_utils/config/config.py, which did not specify the file encoding when writing the TOML configuration. This led to issues on operating systems where the default encoding is not UTF-8.The fix involves explicitly setting the encoding to
utf-8in thewrite_textmethod call within thewrite_tomlfunction. This ensures consistent behavior across all platforms and prevents encoding-related errors.📋 Checklist