Remove user-provided project name from API

[vyasr]

Description

This PR removes the ability for users to set a project name. The name still exists, but it is always just "project". These changes were split off from #643. Currently this changeset only includes the minimal set of changes to ensure that tests pass, but a large number of tests will now trigger warnings. Once reviewers indicate their approval of the new API I can go through and clean up tests.

Specifically, the changes here ensure that in 2.0 a user who accidentally passes a project name as either a positional or keyword argument will only see a warning, not an error. This choice is intended to provide a softer off-ramp for project names since they have been an integral part of signac since its inception. The only cases that were previously valid that will now fail are if the user provides multiple positional arguments in order to set the root directory, e.g. init_project("project_name", "/root/directory"). I think that this is an acceptable level of breakage since the vast majority of users do not set the root explicitly.

I haven't removed the Project.id property here since the name still exists and users can still access it until the 2.0 migration actually removes it. I will remove the id property at that time.

Motivation and Context

Prep for 2.0. Part of #541.

Types of Changes

• Documentation update
• Bug fix
• New feature
• Breaking change¹

¹The change breaks (or has the potential to break) existing functionality.

Checklist:

• I am familiar with the Contributing Guidelines.
• I agree with the terms of the Contributor Agreement.
• My name is on the list of contributors.
• My code follows the code style guideline of this project.
• The changes introduced by this pull request are covered by existing or newly introduced tests.

If necessary:

• I have updated the API documentation as part of the package doc-strings.
• I have created a separate pull request to update the framework documentation on signac-docs and linked it here.
• I have updated the changelog and added all related issue and pull request numbers for future reference (if applicable). See example below.

[codecov]

Codecov Report

Merging #677 (6d79ac9) into next (2544101) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             next     #677      +/-   ##
==========================================
+ Coverage   85.82%   85.84%   +0.01%     
==========================================
  Files          51       51              
  Lines        5024     5038      +14     
  Branches     1104     1109       +5     
==========================================
+ Hits         4312     4325      +13     
- Misses        515      516       +1     
  Partials      197      197              

Impacted Files	Coverage Δ
signac/__main__.py	75.75% <100.00%> (-0.29%)	⬇️
signac/contrib/project.py	89.44% <100.00%> (+0.41%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2544101...6d79ac9. Read the comment docs.

[bdice]

Suggestions attached.

[bdice]

This looks good to me!

edit: I see Python 3.6 tests are failing. The underlying problem is that version.parse only has the attribute major for packaging >= 20.0. We pin Python 3.6 to packaging==15.0. This can be fixed by using version.parse(__version__).release[0] instead of version.parse(__version__).major.

https://packaging.pypa.io/en/latest/changelog.html#id14 (the linked issue is wrong, it should point to pypa/packaging#225)

[vyasr]

@bdice thanks for debugging that for me and making the change painless!

[bdice]

@vyasr I think the method I proposed above would be a bit less hacky with version parsing but I approve the fix either way.

[vyasr]

@csadorf feel free to merge this if you think it's ready.

[csadorf]

Thanks @vyasr !