Update Pipfile.lock about bot HOT 6 CLOSED

Comment from Mark:

changed title from Update Pip{-e-}file.lock to Update Pipfile.lock

from bot.

Comment from Scragly:

Agreed. 1 and 2 were things I noticed when I first loaded the project up too, along with the fact that the discord.py package should be named discord-py in the Pipfile, not discord.

In a personal project's Pipfile, I have discord.py listed with:

discord-py = {git="https://github.com/Rapptz/discord.py.git", ref="rewrite", editable=true}

but as you stated, a commit ref will work perfectly fine:

discord-py = {git="https://github.com/Rapptz/discord.py.git", ref="860d6a9ace8248dfeec18b8b159e7b757d9f56bb", editable=true}

The editable flag should be ensured to be added, as without it, it sometimes doesn't update the package on ref change, same with the package's dependency updates.

from bot.

Comment from Mark:

Just noticed that the name is currently discord and not discord-py in the Pipfile too. By the way, I think the dash is preferred over the dot, for now at least, since there is a bug with pipenv for packages with a . (or a select few other symbols) in the name.

from bot.

Comment from Gareth Coles:

The package is named discord, though. It's also named that on pypi.

from bot.

Comment from Mark:

No it isn't:

• PyPI
• setup.py

from bot.

Comment from Gareth Coles:

Huh, weird. I thought it was.

from bot.