-
Notifications
You must be signed in to change notification settings - Fork 329
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
url: resource and query encoding should support unicode #530
Conversation
f7a8e17
to
0208fd3
Compare
@@ -44,7 +44,8 @@ | |||
|
|||
# Internal imports | |||
from . import __title__, __version__ | |||
from .compat import urlsplit, range, urlencode, basestring | |||
from .compat import (urlsplit, queryencode, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see issue in your files/code.
It depends what you target for. I see it from the standpoint what I would target for.
I would target for have everything in your lib unicode. I mean all coming and outgoing strings.
For that typically programmer needs to have two things enabled shown as two lines below.
# encoding: utf-8
from __future__ import unicode_literals
First line says that this file is UTF-8.
Second line makes every string to be unicode string in this file (not just base string with UTF-8 encoding in it).
What you have now is only first line out of two in this file.
So, your file has all base strings with UTF-8. NOT really unicode strings everywhere.
I'm not sure what you want.
You still can try to go with base strings and UTF-8, but that seems assumed to be more complicated way
with many side effects that needs to be handled.
Hope this can be useful.
All this message is from python 2.7 point of view of course. Not 3.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good idea @Yurmusp will test it out and see if there are any problems for 3.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what was meant. Who will test it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"will" means "we will" shorter way to saying it :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my understanding. Change I suggested shall have no impact on 3.x.
Because this change is actually to make everything more like 3.x
(every string to be unicode) but within 2.x python.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We won't be doing this for now this PR works as is.. We will take this activity as such an issue comes in future. We don't want to introduce subtle changes like this which can have unexpected consequences.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as it works, it's fine I think.
:)
OK. Sounds good.
…On Tue, Jun 6, 2017 at 1:11 PM, Harshavardhana ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In minio/api.py
<#530 (comment)>:
> @@ -44,7 +44,8 @@
# Internal imports
from . import __title__, __version__
-from .compat import urlsplit, range, urlencode, basestring
+from .compat import (urlsplit, queryencode,
"will" means "we will" shorter way to saying it :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#530 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AWEzQmbMs2WY3qzGnwd8ox4rRGosGdf3ks5sBbKKgaJpZM4NwyXQ>
.
|
Please, let me know when done. |
We have a process to review and test. As soon that's done it will be merged. |
Is it days, weeks, months?
can you tell what is a ball park usually?
…On Tue, Jun 6, 2017 at 2:40 PM, Dee Koder ***@***.***> wrote:
We have a process to review and test. As soon that's done it will be
merged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#530 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AWEzQoxDIvXa0iSnjxU_-z0YidhHVG6Cks5sBcdHgaJpZM4NwyXQ>
.
|
Usually 2-3 days.. @Yurmusp |
Sounds good. Thank you.
…On Tue, Jun 6, 2017 at 2:49 PM, Harshavardhana ***@***.***> wrote:
Is it days, weeks, months?
can you tell what is a ball park usually?
Usually 2-3 days.. @Yurmusp <https://github.com/yurmusp>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#530 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AWEzQtMX_pq1GH07ygit6tZPcYhNzj1uks5sBcmEgaJpZM4NwyXQ>
.
|
@Yurmusp its taking a bit longer because we are right now doing some fixes in minio/minio. Please stay tuned on this one. |
Yes. Waiting.
Please, do not delay too much if possible.
Thanks.
…On Sun, Jun 11, 2017 at 6:58 PM, Dee Koder ***@***.***> wrote:
@Yurmusp <https://github.com/yurmusp> its taking a bit longer because we
are right now doing some fixes in minio/minio. Please stay tuned on this
one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#530 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AWEzQikK2j3d7IjaNhxxTooPlqxFrUBnks5sDJspgaJpZM4NwyXQ>
.
|
Guys,
Any progress?
…On Mon, Jun 12, 2017 at 1:32 PM, Yuriy Musatenko ***@***.***> wrote:
Yes. Waiting.
Please, do not delay too much if possible.
Thanks.
On Sun, Jun 11, 2017 at 6:58 PM, Dee Koder ***@***.***>
wrote:
> @Yurmusp <https://github.com/yurmusp> its taking a bit longer because we
> are right now doing some fixes in minio/minio. Please stay tuned on this
> one.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#530 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AWEzQikK2j3d7IjaNhxxTooPlqxFrUBnks5sDJspgaJpZM4NwyXQ>
> .
>
|
0208fd3
to
c46bdc7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
5f06810
to
57daf09
Compare
python2.7 lacks proper unicode support, so we need a proper wrapper function for url encoding. With this the url and query encodings works for all unicode characters. Fixes minio#529
57daf09
to
c6926bd
Compare
When you guys expect it to be released? |
Thank you guys. Looks like this works. |
python2.7 lacks proper unicode support, so we need
a proper wrapper function for url encoding. With
this the url and query encodings works for all
unicode characters.
Fixes #529