python - PyPi description markdown doesn't work -

-

I uploaded a package to use POP: 

  Register -r pypi dragon setup.py sdist upload -r pypi

I am trying to modify decsription, I wrote (Please do not edit the formatting of the following part of the code For example, I've made it: `` `Dragon '@' RTR (this is the purpose of displaying my problem): 

  ** nose-docstring-plugin ** This plugin lets you Half of their properties The test enables to modify the dosstring of tests on: section = 'miksaction', type = 'functional +', module = 'miamulude', id = 1) def test_function (self): "" "This is the original doccrusion pass However, the text appears to be,  without  marker formatting what I'm doing wrong?   < P> 
 
 PyPI does  not  support, README will not be rendered in HTML 
 If you want a rendered readme, stick with the reconstructed text; This is a good starting point.  
 You probably want to install it so that you can test your document locally; You want to see the  rst2html.py  script included on your README to see if errors occur, if any. There are too many errors in your specific sample: 
   $ bin / rst2html.py test.rst & gt; /tmp/test.html test.rst: 7: (error / 3) Unexpected indentation. Test.rst: 3: (Warning / 2) Inline literal start-string without end-string. Test.rst: 3: (Warning / 2) Inline interpreted text or phrase reference starting string without end-string. Test.rst: 11: (warning / 2) block coat ends without a blank line; Unexpected unindent Test.rst: 11: (Warning / 2) Inline literal start-string without end-string. Test.rst: 11: (Warning / 2) Inline interpreted text or phrase reference start string without end-string.

Your code block is using the Gecko's MarkTown extension, which is completely incorrect for the structured text again. You can use a reverse code block (perhaps, If the PPI version of doctors is new enough): 

  .. code-block :: python @attr (section = 'MySection', type = 'functional +', module = 'mymodule', ID = 1) DEF test_function (self): "" This is the original docostring ""

This is done locally by testing There is a need to set up as well.

If you are interested, then add support for Markdown.


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more