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

Fix unicode error #136

Closed
wants to merge 12 commits into from
Closed

Conversation

julienmalard
Copy link

This fixes #221 by exchanging the regex package for re (the former having fixed the long-standing bug in re (see here for details). Not sure if this will work for poetry (i.e., whether adding regex as a dependency is acceptable)...but thought I would propose this change and wait for feedback to take it from there.
Thanks!

Resolves: python-poetry/poetry#221

  • Added tests for changed code.
  • Updated documentation for changed code.

Unfortunately couldn't figure out where to add the tests. Let me know and I will gladly do so!

This fixes python-poetry#221 by exchanging the regex package for re (the former having fixed the long-standing bug in re (see [here](lark-parser/lark#590) for details). Not sure if this will work for poetry (i.e., whether adding regex as a dependency is acceptable)...but thought I would propose this change and wait for feedback to take it from there.
Thanks!
@kasteph
Copy link
Member

kasteph commented Mar 26, 2021

Thank you for the PR! Can you rebase against main and resolve the conflicts?

sdispater and others added 8 commits March 26, 2021 12:54
* Update CI files for Python 3.6+ only

* Modernize codebase

* Reorganize imports to improve performance
The sync target previously regenerated the poetry.lock for vendored
packages, causing larger than necessary change set for patches. This
change introduces the update target to specifically handle lock file
updates, lock target to regenerate the lock file and repurpose the sync
target to only sync as expected.
Setting develop to `True` by default causes un-expected side-effects
and requires downstream consumers to rely on checks like
`package.develop and package.source_type == "directory""` to determine
if develop mode.

This also corresponds to current high-level behaviour of packages being
non-develop by default.
@julienmalard
Copy link
Author

Thanks @stephsamson ! I rebased, added failing tests, and pushed again (all local tests passing with latest commit). Please do let me know what else would be needed.

@julienmalard
Copy link
Author

P.S. I just reformatted. It currently seems to fail because regex is missing as a dependency; do you happen to know where I should specify it? (Would adding it to [tool.poetry.dependencies] work?)

@Secrus
Copy link
Member

Secrus commented Aug 22, 2022

Superseded by #276

@Secrus Secrus closed this Aug 22, 2022
@julienmalard julienmalard deleted the patch-1 branch August 22, 2022 08:40
@julienmalard julienmalard restored the patch-1 branch August 22, 2022 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

poetry develop failing on non-ASCII characters
6 participants