tomtom-international / cookiecutter-python Goto Github PK

Dependabot couldn't parse the pyproject.toml found at /{{cookiecutter.project_name}}/pyproject.toml.

You can mention @dependabot in the comments below to contact the Dependabot team.

Description

It would be good to generate a Docker image that is compatible with whalebrew.

IMPORTANT PLEASE READ: NO RESPONSE WILL RESULT IN REPO ARCHIVAL AND FINALLY DELETION

Dear maintainer,

One important topic in our TomTom open source engineering community is to make our public organization on GitHub, as well as the repositories hosted on it, more welcoming to contributors. That process starts which making it easy for other to understand the purpose of a codebase is and how people can contribute.

In order to do so we want to learn which repo's are still actively maintained and important to keep available to the open source community and which are not. We have therefore decided to start a clean-up proces which will be done as follows:

1. Please respond to this issue within 30 days and provide us with the necessary information requested below.
2. If there is no reply to this issue after these 30 days, the repository will be archived
3. After your repo has been archived you have an additional 30 days to respond and provide information and discuss with us whether you want to revert, or keep archived status.
4. IMPORTANT After the above mentioned additional 30 days no response is given the repository will be removed from the TomTom-International organization or will be DELETED

Could you please be so kind to provide us with the following information

Contact details

Repo owner/primary contact: [please provide email address]

Repository details

Describe the purpose/objective of this codebase in 1-5 sentences:
[enter description here]

Please select how this repository contributes to the following (thick all that apply):

• Internal use: The code is used inside TomTom and there is a vested interest in long term maintenance
• Employer branding: Project gives an insight into the scale and problem-solving of TomTom tech.
• Hiring: contributors and users of the project could be attractive job candidates
• Learning: TomTom employees can collaborate with and learn from external experts on the topic
• Enhancement: the project could gain new functionality and refinement by external use and contribution
• Product: The project is needed to make our tech or products integrate with other products or tech stacks
• License Compliance
• Fork: Fork needed for for upstream contributions, long-term upstream collaboration or product / CI/CD pipeline dependency or other need. If this is the case you can move your fork to a new GitHub organization https://github.com/tomtom-forks. If you need access to this org reach out at the #ospo channel on slack with your TomTom Github user account.

Additional context information about the purpose of this codebase:
[enter addition info here]

Questions?

Please respond to this issue or drop a line to [email protected] mentioning this issue nr.
Or for TomTom'ers reach out on the #ospo slack channel.

Thanks so much for helping keep our public repositories up to date and welcoming to all contributors.

Description

Right now regardless whether a project is published on GH or BB we produce the same files. Some files are important when opensourcing a project whereas for internal usage only some are superfluous.

The idea is that when selecting BitBucket Server as VCS we can assume that the project won't be opensourced. In that case we should clean up all files related to OSS in the post hook.

If someone decides to opensource the projects the template can be again applied with GH as VCS and the important files will be generated again.

Description

Currently we support the generation of documentation but it is not yet integrated into Bitbucket pages and Github pages.

• Date you used Cookiecutter PyPackage: 10.01.20
• Cookiecutter version used, if any: 1.6.0
• Python version, if any: 3.6.8
• Operating System: macOS Mojave

Description

Generated pyproject.toml file is malformed when setting black formatter setting to n

/)
'''

What I Did

Generate a dummy project with default values (especially black formatter set to no) and the generated pyproject.toml file will be malformed:

Description

Right now all intermediate files are generated under the root directory of the project (eg. .egg directory, coverage files, virtualenv, etc.)

In order to easily get to a clean state it would be good to store all the generated output in one directory

Description

Create some documentation in form of a wiki/README to explain the various options the cookiecutter template prompts for

To avoid manual changes to AUTHORS.md (and forgetting contributors) we should make use of a script to fetch the information from git.

Example:
https://github.com/moby/moby/blob/master/hack/generate-authors.sh

Instead of calling Pylint, we should call Black (https://stackoverflow.com/a/21196195) with the check option set in order to verify if files are in the correct format.

The bot created this issue to inform you that pyup.io has been set up on this repo.
Once you have closed it, the bot will open pull requests for updates as soon as they are available.

Description

Add a target to the Makefile to generate a docker image similar what the pythonSetupPyPipeline does

Dependabot encountered the following error when parsing your .dependabot/config.yml:

The property '#/update_configs/1' did not contain a required property of 'package_manager'
The property '#/update_configs/1' did not contain a required property of 'directory'
The property '#/update_configs/1' did not contain a required property of 'update_schedule'

Please update the config file to conform with Dependabot's specification using our docs and online validator.

You can mention @dependabot in the comments below to contact the Dependabot team.

The bot encountered an error in your .pyup.yml config file:

  in "<unicode string>", line 20, column 5:
      - {{cookiecutter.project_name}}/re ... 
        ^
expected <block end>, but found '<scalar>'
  in "<unicode string>", line 20, column 34:
      - {{cookiecutter.project_name}}/requirements_dev.txt:
                                     ^

You can validate it with this online YAML parser or by taking a look at the Documentation.

Since the cookiecutter itself has not the ability to easily add comments during the process of generating a new project (currently it shows you only the cookiecutter variable name and possible values) it would be good to have a simple Github learning lab showing how to create easily projects.

This would then explain step by step all the available variables and show the user what exactly to do.

Description

As discussed in #36 (comment) it would be nice to not require the virtualenv and use the built in venv module. This has already been my operating mode on Linux, but should be tested elsewhere.