Need help with naming scheme in debian/control for python library

[Aryan Karamtoth <aryankmmiv@outlook.com>]

Hi, I'm trying to package a python library into debian. I used dh_make to create the debian folder in the source code.

I have a small query regarding the naming convention I need to follow in the debian/control for python packages

Debian/control has a section called Source with the source package name as the first field and also has another section called package with the package name and another section called package docs

When I first used dh_make to make the Debian folder, used the folder name as the source package name in the form “package name” but the package that I’m trying to package needs to have the name as “python3-packagename” but the package field already has that kind of name

So my question is should I rename the source field to “python3-packagename” too or will it cause any conflicts?

To make it more clear, my debian/control currently looks something like this

source: python3-packagename

priority: main

.

.

.

.

package: python3-packagename

.

.

.

package: python3-package name-docs

.

.