PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Thursday the 17th of December, 2015

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[00:15:55] <pmxbot> jaraco pushed 3 commits to setuptools (https://bitbucket.org/pypa/setuptools/) :
[00:15:55] <pmxbot> In resolve version, always cast to a string (avoiding Unicode on Python 2). Fixes #476.
[00:15:56] <pmxbot> Explicitly quote strings rather than relying on repr. Fixes #477.
[00:15:56] <pmxbot> Prefer locals to vars
[00:34:36] <pmxbot> jaraco pushed 3 commits to setuptools (https://bitbucket.org/pypa/setuptools/) :
[00:34:36] <pmxbot> Bumped to 19.1.1 in preparation for next release.
[00:34:36] <pmxbot> Added tag 19.1.1 for changeset 0a2a3d89416e
[00:34:36] <pmxbot> Bumped to 19.1.2 in preparation for next release.
[03:48:57] <StevenK> lifeless: Last failure in pip
[03:49:05] <StevenK> lifeless: If I can pick your brain for a few
[03:49:25] <lifeless> sure
[03:49:53] <StevenK> lifeless: test_get_index_urls_locations in unit/test_finder.py is the failure
[03:50:46] <StevenK> lifeless: Turns out pkg_resources.Requirement replaces _ with - for project_name. packaging.Requirement does no such thing.
[03:51:21] <lifeless> it also case folds
[03:51:50] <lifeless> we may need a PEP to define that, possibly an edit of 508
[03:51:59] <StevenK> (Pdb) p self.req.project_name
[03:51:59] <StevenK> 'Complex-Name'
[03:52:03] <lifeless> though it seems more like a PyPI thing
[03:52:26] <StevenK> I can deal with it in the method itself, by doing a replace if that's reasonable
[03:53:07] <lifeless> I'd crib the pkg resources glue yeah
[11:32:08] <xafer> dstufft: did you see https://github.com/pypa/packaging-problems/issues/81 ?
[11:32:35] <dstufft> I did, then promptly forgot about it
[11:32:47] <dstufft> I'll take care of it in a bit, taking my daughter to the bus soon
[11:40:55] <xafer> thanks :)
[18:24:32] <nlh> ping dstufft
[18:24:41] <dstufft> nlh: pong
[18:24:48] <nlh> hello! How is the new house?
[18:26:06] <dstufft> alright :D still unpacking but at least have a working computer and internet now
[18:26:24] <nlh> cool! I'm glad you do too!
[18:27:04] <nlh> I'm just writing up my thoughts on the design process - I wanted to include a section on internationalization and localization... but as this is more your area, i thought I'd ask you about it first
[18:27:27] <dstufft> sure
[18:28:06] <dstufft> right now it's using l20n.js which is a translation thing that actually understands HTML instead of trying to shoe horn gettext into it
[18:28:20] <dstufft> but beyond marking things for localization, I Haven't relaly used it much
[18:28:53] <nlh> ok... but the plan is to fully support it? As in, at some stage we'll be looking for translators?
[18:28:59] <nlh> post launch?
[18:29:07] <dstufft> yea
[18:29:12] <dstufft> that's the plan
[18:29:18] <nlh> cool. And does the current PyPI do any of this?
[18:29:21] <dstufft> Nope
[18:29:23] <dstufft> english only
[18:29:25] <nlh> (I couldn't find the code base)
[18:29:30] <dstufft> no localization either
[18:29:32] <nlh> well, that's a HUGE improvement :D
[18:29:39] <dstufft> current code base is at bitbucket.org/pypa/pypi
[18:29:42] <dstufft> but it's really bad
[18:30:17] <nlh> ok, great. Well, I'll write it up... and send you the document before I publish :D
[18:30:30] <dstufft> sounds good
[18:30:32] <nlh> hopefully I can get it finished in the next couple of days
[18:30:47] <nlh> and then, I AM going to put in a talk proposal for PyCon... because why not?
[18:30:47] <nlh> lol
[18:30:54] <dstufft> of particular interest (I think) to the design, is the fact that l20n.js supports "responsive localization"
[18:31:18] <dstufft> IOW, you can have different localization strings based on the size of the display
[18:32:06] <nlh> oh, that's cool. I'll read about it and make sure to include it
[18:32:34] <dstufft> so translators with languages that are longer can try to make shorter translations in situations where there isn 't room for a long chunk of text
[18:34:53] <nlh> right, that's awesome
[18:36:09] <dstufft> it does some other nice stuff (I think anyways) it doesn't use the english text (or whatever) as the "id" for the translation, so you can make adjusts to the english text (typo fixes, things that don't change the _meaning_ of the string) without forcing everyone to retranslate
[18:43:14] <lifeless> dstufft: o/
[18:43:23] <dstufft> heya