On Fri, Feb 24, 2017 at 6:59 AM, Paul Moore <p.f.moore@gmail.com> wrote:
On 24 February 2017 at 11:54, Lele Gaifax <lele@metapensiero.it> wrote:
> Paul Moore <p.f.moore@gmail.com> writes:
>
>> On 24 February 2017 at 11:37, Lele Gaifax <lele@metapensiero.it> wrote:
>>> Can anyone shed some light on the problem? By what logic buildout used a
>>> different name for that particular package?
>>
>> While I don't know anything about buildout, pyramid-tm is the
>> normalised version of pyramid_tm - see
>> https://www.python.org/dev/peps/pep-0503/#normalized-names
>
> Oh, I see, thank you. Does that mean that the right thing I should do is
> always using such normalized names in my requirements.txt/versions.cfg?

I *think* it shouldn't matter. The problem will likely be with older
tools not normalising. So using normalised names throughout might help
such tools.

Thanks Paul.  Yes, this is a buildout bug:

https://github.com/buildout/buildout/issues/317

This case shed the light on the bug for me. Thanks.

Jim

--