Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Slicker does not correctly move definitions containing unicode #35

Open
benjaminjkraft opened this issue Aug 30, 2018 · 0 comments
Open

Comments

@benjaminjkraft
Copy link
Contributor

benjaminjkraft commented Aug 30, 2018

If you try to move a single symbol whose definition contains unicode (and uses an imported name) to a file which does not already have a PEP 263 encoding comment, slicker crashes.

Here's a repro:

# test.py
# coding: utf-8
import x

def foo():
    x.y()
    return 'bár'

Then run slicker test.foo test2.

A workaround is to add the coding comment to the destination file in advance.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant