On 24 February 2017 at 11:54, Lele Gaifax <firstname.lastname@example.org> wrote:
> Paul Moore <email@example.com> writes:
>> On 24 February 2017 at 11:37, Lele Gaifax <firstname.lastname@example.org> 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
> 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