Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handle conflicting project names gracefully, fixes: #1357 #1837

Merged
merged 5 commits into from
Jun 10, 2015

Conversation

jenner
Copy link
Contributor

@jenner jenner commented Jun 10, 2015

  • Check for importable packages/modules with the same
    name as the package to be created
  • Added --force-conflicting-name option to enforce the
    use of a conflicting package
  • Added appropriate tests

jenner added 4 commits June 10, 2015 22:13
- Check for importable packages/modules with the same
  name as the package to be created
- Added --force-conflicting-name option to enforce the
  use of a conflicting package
- Added appropriate tests
- Use input() in python3 and raw_input in python 2.x
- Remoced unused local variables
- Made sure str.format() calls are py2.6 compatible
- Removed test_scaffolds/test_init.py#test_pre_site
  since the check is handled in pcreate script
if sys.version_info[0] == 3:
user_input = input # pragma: no cover
else:
user_input = raw_input # NOQA
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- Use pyramid.compat.input_ instead of manually checking
  for python version and chosing the appropriate
  input/raw_input function
- Renamed--force-conflicting-name option to --ignore-conflicting-name
- Display invalid scaffold names in a sorted manner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants