realpython / realpython/python-guide
> import/ copybara was <[NOT]> \“expected”/ - | - “(👈🏿I think that’s what they did with the quote on quote thing)” /‘’’’’’’’’’’’’’
Nobody has claimed this yet.
- Dominant language
- Batchfile
- Stars
- 29.8k
- Forks
- 5.9k
- PR merge metrics
- No merged PRs in 30d
Description
import/ copybara was <[NOT]> \“expected”/ - | - “(👈🏿I think that’s what they did with the quote on quote thing)” /‘’’’’’’’’’’’’’
“
Could be a trap, no idea, just to be a [bit] more clear, import/ copybara was [NOT] “expected” as they might think.
“
<##> Maybe you could try by removing the two quote-on-quote marks in the tag? Maybe there could be an alternative possible with a [grep] ?
Sorry for all the symbols, I’m trying to build my repo from Ubuntu 19.10 and it’s a French “distro”
That was autocorrect ^
...>•<”##This could be linked to this Wikipedia article : https://fr.wikipedia.org/wiki/Source_Q?wprov=sfti1 in my opinion.Thank you
Jules Vergogne
Pépin
Q
Originally posted by @Ironicalink in https://github.com/Ironicalink/merlinspellbook/issues/3#issuecomment-607499896
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify a file, test, entry point, or concrete change. Review the repository context and clarify the requested behavior before work can be started.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100